Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Not sure I understand fully.. Are you trying to 'get into' some sort of internal configuration menu in the modem, sort of like one would do with a router?
192.168.0.1 is normally the 'default gateway' but not in my experience an I.P. address for a piece of hardware. FOr excample, to get into my router, I always just used my web browser, and entered 192.168.0.254 (or whatever it is) into the navigation bar, and instantly the routers login page appeaed. Is this what you are trying to do?
Also, changing your ethernet adapters IP address using ifconfig is not changing the modem IP address, only the address of the NIC (network interface) so I suspect that whatever address you should be using to access the modem is hard-coded, and is something other than 192.168.0.1.
Maybe I've totally misunderstood the issue, but can you give us the full model name & number of the modem, and any further information about it?
I'm not sure what 'installing' the modem would entail, but my guess would be that it would merely need to be plugged in & turned on, maybe even RESET using the reset button & procedure documented in the manual. As for 'installation' it appears from the manual that any installation that you would do would apply more to Windows than Linux. It looks like you can basically plug it in and access it thru the browser as we discussed.
Now, it seems like your ethernet connection (NIC) is not configured properly. The manual indicated that the modem will give your computer an IP using the DHCP method, so you need to configure your ethernet adapter to use DHCP to aquire an IP address.
What Linux are you using (or what OS if not Linux?) and what kernel?
What type of onboard ethernet device do you have?
Have you enabled the kernel driver necessary to use your ethernet device?
Does your OS have a network configuration area? Does it work, and tell you that the ethernet device is 'enabled'?
Let's start there..
Last edited by GrapefruiTgirl; 09-17-2007 at 06:14 AM.
OK, well let's see here.. First, I'll tell you that I am not using a Debian distro, so I can't be specific on what files you will be dealing with, if any, or where on your system they will be located. However, chances are, they are in the /etc folder somewhere.
In the root console, type 'ifconfig' by itself, and tell me if it shows your ethernet adapter (probably eth0) and if it is up and running. If not try typing ifconfig eth0_up. Does it work?
So, for the Realtek adapter: It is (perfectly?) supported by the kernel. I have a Realtek 8211 adapter, and the driver I use is called r8169 or r8139, and is in the kernel. Now, whether it's built into YOUR current kernel, I don't know.
In the root console, type 'lsmod' and see if you see a similarly named driver listed there. If so, great. If not, type 'modprobe r8169' or 'modprobe r8139' and let us know how that goes. Any errors? If there's no feedback, then it worked. The module should be inserted now.
OK, as I mentioned, I'm not totally sure how to go about configuring your Debian system, so you will need to do some research on your own to learn how and where to set up your ethernet adapter for DHCP and enable it if necessary (if it isnt already enabled by this point). Check your system menu for 'Internet Adapters' or 'Internet Connections' and go from there. Also, check any documentation for your Linux to learn what files are involved and where they are located.
Keep me posted, I'll help where I can.
If you cannot locate the driver for your device, it may not me compiled into your kernel (or as a module) though if you're running a stock kernel, I would think it would be, but who knows.. If it isn't, you'll hafta recompile the kernel to enable the driver for the Realtek device. Let's get to that later, if necessary.
EDIT: I get the impression from your post that the eth0 device IS active, or atleast is seen by the system. If so, it's a matter of configuring it for DHCP, so that it can get an IP from the modem and communicate with it. Again, check your documentation for something like 'Configuring DHCP' or similar.
Last edited by GrapefruiTgirl; 09-17-2007 at 06:41 AM.
yes the eth0 is up and running
i typed modprobe r8169
and there was no feedback...
the ismod didn't work, doesn't find that command
and i think the dhcp adapter is enabled i did it my self in the
network administration tool menu (i'm doing a bit of direct translation here, my system is in french)
it says that the eth0 interface is active
it has a dhcp configuration...
OK, 'lsmod' is with an L, not an 'I', as in 'LSMOD'
Anyhow, as the eth0 is up and active, we don't need to look at lsmod anyhow, because obviously the adapter's driver is already installed.
So, since DHCP is configured, and eth0 is up, it would appear that something very simple is preventing the modem from communicating.
What I would try (and this may not help, but I don't have much more to offer) would be to reset the modem using the procedure in the manual, and then disable the eth0 and re-enable it, by doing one of two methods:
or , method 2, if your debian system uses rc init scripts and has a file such as /etc/rc.d/rc.inet1, would be to navigate to the folder /etc/rc.d and type:
and then try to log into the modem again using the browser.
If this doesn't help, I'm sorry but with my limited knowledge of the Debian methods of doing things, I would more than likely lead you astray than help, if I suggest more stuff to try.
If you think I *can* help further, please feel free to post again. Meanwhile, I hope another user pops in with a new idea for you, or points to something obvious that we/I missed.
Here's another thread on another forum, where a user appears to have had similar problems. They set up a gateway address and/or IP address for the eth0, as issued by the modem, and it fixed the problem.