eth0 once again...this time it's better
Hi, On Tueasday I had a problem with my sue 8 machine. It is configured thusly: suse box --> router --> dsl modem -->internet The problem was that suse wasn't recognizing eth0, a nvidea card that works (as evidenced by the fact that you are getting this). I think that part of the problem was that smpppd was trying to start. I stopped that - I didn't need it. I then went into yast and deleted the existing eth0 configuration, then reinput the info and restarted the network. Success! However, when I restarted the machine, eth0 failed again on startup. Can anyone offer any suggestions? Thanks, Nick
On Thursday 18 July 2002 05:47, Nick Selby wrote:
However, when I restarted the machine, eth0 failed again on startup.
When you say failed, do you mean it wasn't able to get an address via DHCP? Or do you mean something else? AFAIK, if you connect to the internet using PPPoE (if you have a user name and password for your DSL service, then it is likely that you are using this method), you need to have the PPP service started before you network card will get its address. This might cause the DHCP service to fail on startup. Again, if this is not what's happening, let me know. -- Burhan
On Thursday 18 July 2002 15:03, you wrote:
On Thursday 18 July 2002 05:47, Nick Selby wrote:
However, when I restarted the machine, eth0 failed again on startup.
When you say failed, do you mean it wasn't able to get an address via DHCP? Or do you mean something else?
No, I mean that in the log it said starting,... lo.....................done eth0..................failed
AFAIK, if you connect to the internet using PPPoE (if you have a user name and password for your DSL service, then it is likely that you are using this method), you need to have the PPP service started before you network card will get its address. This might cause the DHCP service to fail on startup.
The username and password are stored on the router. The linux box is set up for dhcp, and gets IP and name server from the router.
Again, if this is not what's happening, let me know.
I'm open to any and all suggestions!
On Thursday 18 July 2002 15:09, Nick Selby wrote:
On Thursday 18 July 2002 15:03, you wrote:
On Thursday 18 July 2002 05:47, Nick Selby wrote:
However, when I restarted the machine, eth0 failed again on startup.
When you say failed, do you mean it wasn't able to get an address via DHCP? Or do you mean something else?
No, I mean that in the log it said starting,...
lo.....................done eth0..................failed
to be more precise, this is the actual message Setting up network interfaces: lo done eth0 (DHCP) failed
On Thursday 18 July 2002 06:15, Nick Selby wrote:
Setting up network interfaces: lo done eth0 (DHCP) failed
Yeap, just as I thought. This is the same message that I get when I bootup. A few things you should check : (under YaST2 -- which I personally hate, but....) : Under Network/Basic --> DSL Configuration : Make sure you check what mode you have it running under. More than likely it will be PPP over Ethernet. Check the firewall (unless you've got your own firewall setup) If you want DSL to come on everytime a user (application) accesses the internet, check the dial-on-demand. You will need the IP addresses of your local DNS servers for this to work. Check with your ISP. Under Network/Basic --> Network Card Configuration : If that eth0 (DHCP) failed is really bothering you, give your eth0 card a static IP address. Do this ONLY IF YOU ARE USING PPPoE. If your ISP has given you a static IP, then of course you would want that number in there. You can use any IP address that is in the private net class (my favorite is 127.0.0.1). Netmask is 255.255.255.0 You can leave the hostname and route settings alone. Under Network/Advanced --> Hostname and DNS : Check the box that says "change hostname with DHCP". Also, you add the DNS numbers (from step 1) under the Name Server List. Let me know if this helps, -- Burhan
On Thursday 18 July 2002 15:25, Burhan Khalid wrote:
On Thursday 18 July 2002 06:15, Nick Selby wrote:
Setting up network interfaces: lo done eth0 (DHCP) failed
Yeap, just as I thought. This is the same message that I get when I bootup. A few things you should check :
(under YaST2 -- which I personally hate, but....) :
Under Network/Basic --> DSL Configuration : Make sure you check what mode you have it running under. More than likely it will be PPP over Ethernet. Check the firewall (unless you've got your own firewall setup) If you want DSL to come on everytime a user (application) accesses the internet, check the dial-on-demand. You will need the IP addresses of your local DNS servers for this to work. Check with your ISP.
Wait. I'm really glad to hear this but I am concerned that you don't understand one element (or more likely I don't understand it, but here goes): The DSL connection is not directly connected to the machine, but rather to the router. The router is providing IP forwarding and masq services. I was under the impression - in fact the machine did not work - until I removed all DSL configuration information from the suse machine. Is this right?
Under Network/Basic --> Network Card Configuration : If that eth0 (DHCP) failed is really bothering you, give your eth0 card a static IP address. Do this ONLY IF YOU ARE USING PPPoE. If your ISP has given you a static IP, then of course you would want that number in there. You can use any IP address that is in the private net class (my favorite is 127.0.0.1). Netmask is 255.255.255.0
Yeah...but but but but but the DHCP is assigning an IP address, yes? or am I wrong here?
You can leave the hostname and route settings alone.
Under Network/Advanced --> Hostname and DNS :
Check the box that says "change hostname with DHCP". Also, you add the DNS numbers (from step 1) under the Name Server List.
That's been done.
Let me know if this helps,
We're getting there!
On Thursday 18 July 2002 16:28, Anders Johansson wrote:
After a reboot if it's not started automatically, the dhcpcd command you ran this time should work again as well.
No, it did not. AAARRRGGGHHHH. I write from WinXP. And this command did not work: linux:~ # dhcpcd -d eth0 linux:~ # ping 192.168.1.1 connect: Network is unreachable linux:~ # In fact, I was unable to restore the connection even by deleting the configuration of eth0 and then reinstalling it as I did last time. If I click in Available Hardware, I see that the machine sees it. However after reboot note the output of ifconfig: linux:~ # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:168 errors:0 dropped:0 overruns:0 frame:0 TX packets:168 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12976 (12.6 Kb) TX bytes:12976 (12.6 Kb) linux:~ #
But it's curious that it won't work on bootup.
Curious? Yeah, I'm pretty curuious myself.
I'm a little at a loss as to why, and without the hardware in front of me to experiment I can't really find out the reason for it.
So am I stuck here? What can I do?? Thanks in advance, nick
//Anders
------- End of forwarded message -------
On Thursday 18 July 2002 17.17, php@nickselby.com wrote:
So am I stuck here? What can I do??
Hm. You said you had an nvidia ethernet controller? If you do "/sbin/lsmod | grep nvnet" Do you get a hit? If you don't, try "modprobe nvnet" followed by the dhcpcd command. If that works, put a line "alias eth0 nvnet" in /etc/modules.conf and run depmod -a Just a thought //Anders
Nick: I am having a very similar problem. In the Network Card Configuration table, the entry under the Active column is "--" instead of Yes or Active. If I make a change to the network configuration, I receive an error that says Device eth0 not running. However, my PC is communicating with the internet through this same card! I use a static address (192.168.1.4) for this PC. The strange part is that I can not make telnet connections, or receive ping responses, to other PCs on my LAN in the house. Anyone have any ideas on this one? Charlie
participants (5)
-
Anders Johansson -
Burhan Khalid -
charlie carroll -
Nick Selby -
php＠nickselby.com