Re: [SLE] eth0 once again...this time it's better
On Thursday 18 July 2002 15.59, Alan Wissenberg wrote:
Hi, Anders!!
On Thursday 18 July 2002 15:49, Anders Johansson wrote:
On Thursday 18 July 2002 14.47, Nick Selby wrote:
Can anyone offer any suggestions?
Did you try my suggestion?
dhcpcd -d eth0
I had tried it before, no effect. Now that eth0 is being recognized once again, I forgot to re-run that. I just did; and got this:
dhcppc1:~ # dhcpcd -d eth0 #dhcpcd: MAC address = 00:30:84:2d:35:d8 dhcpcd: your IP address = 192.168.1.34 dhcppc1:~ # #
Great, yes?
Yes, perfect. After this the network works without problems, right? So all you need is to make this permanent. If YaST won't do it, do it manually. Create a file in /etc/sysconfig/network called ifcfg-eth0 with the contents BOOTPROTO="dhcp" STARTMODE="onboot" Then, unless I'm much mistaken, it should work on startup.
Also check that the kernel driver module for the card has loaded properly.
Eh. Er. How? Here's ifconfig, for the first time since we started this that I have seen eth0:
If it hadn't loaded properly, dhcpcd wouldn't have run as successfully as it did, so that's not an issue now.
dhcppc1:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:30:84:2D:35:D8 inet addr:192.168.1.34 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::230:84ff:fe2d:35d8/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3360 errors:0 dropped:0 overruns:0 frame:0 TX packets:3261 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1498490 (1.4 Mb) TX bytes:445327 (434.8 Kb) Interrupt:5 Base address:0xa000
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:86 errors:0 dropped:0 overruns:0 frame:0 TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5888 (5.7 Kb) TX bytes:5888 (5.7 Kb)
dhcppc1:~ #
Here#s route -n Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Looks perfect. Check that /etc/resolv.conf also has an entry for the name server. As far as I can see that's all you need for successful networking. //Anders
On Thursday 18 July 2002 16:09, Anders Johansson wrote:
On Thursday 18 July 2002 15.59, Alan Wissenberg wrote:
Hi, Anders!!
On Thursday 18 July 2002 15:49, Anders Johansson wrote:
On Thursday 18 July 2002 14.47, Nick Selby wrote:
Can anyone offer any suggestions?
Did you try my suggestion?
dhcpcd -d eth0
I had tried it before, no effect. Now that eth0 is being recognized once again, I forgot to re-run that. I just did; and got this:
dhcppc1:~ # dhcpcd -d eth0 #dhcpcd: MAC address = 00:30:84:2d:35:d8 dhcpcd: your IP address = 192.168.1.34 dhcppc1:~ # #
Great, yes?
Yes, perfect. After this the network works without problems, right?
So all you need is to make this permanent. If YaST won't do it, do it manually. Create a file in /etc/sysconfig/network called ifcfg-eth0 with the contents
BOOTPROTO="dhcp" STARTMODE="onboot"
Whhoops. Went in there and there wlready was that file and in it those lines you mentioned,. However there was also the line: UNIQUE="8otl.i7weOaDg+M6" What be this? I haven''t yet tried a reboot for fear of losing this connection!!!!! Nick
Then, unless I'm much mistaken, it should work on startup.
Also check that the kernel driver module for the card has loaded properly.
Eh. Er. How? Here's ifconfig, for the first time since we started this that I have seen eth0:
If it hadn't loaded properly, dhcpcd wouldn't have run as successfully as it did, so that's not an issue now.
dhcppc1:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:30:84:2D:35:D8 inet addr:192.168.1.34 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::230:84ff:fe2d:35d8/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3360 errors:0 dropped:0 overruns:0 frame:0 TX packets:3261 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1498490 (1.4 Mb) TX bytes:445327 (434.8 Kb) Interrupt:5 Base address:0xa000
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:86 errors:0 dropped:0 overruns:0 frame:0 TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5888 (5.7 Kb) TX bytes:5888 (5.7 Kb)
dhcppc1:~ #
Here#s route -n Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Looks perfect. Check that /etc/resolv.conf also has an entry for the name server. As far as I can see that's all you need for successful networking.
//Anders
On Thursday 18 July 2002 16.18, Nick Selby wrote:
Whhoops. Went in there and there wlready was that file and in it those lines you mentioned,. However there was also the line:
UNIQUE="8otl.i7weOaDg+M6"
What be this?
That is a YaST identifier.
I haven''t yet tried a reboot for fear of losing this connection!!!!!
After a reboot if it's not started automatically, the dhcpcd command you ran this time should work again as well. But it's curious that it won't work on bootup. 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. //Anders
participants (2)
-
Anders Johansson -
Nick Selby