Hello, everyone. Just as a quick suggestion, have you tried the other DHCP client (the ICS one I believe) instead of the default one ? There are two different ones on the SuSE8 discs, so it might be worth trying the other one if you haven't already. Bye for now, Stuart. -----Original Message----- From: Cleary_Mike@emc.com [mailto:Cleary_Mike@emc.com] Sent: Friday, July 26, 2002 17:45 To: suse-linux-e@suse.com Subject: RE: [SLE] DHCP weirdness w/suse 8 box and USRobotics router I don't have an answer, because I am experiencing pretty much the same thing. And I have spent a lot of time recently searching mail lists, etc. and it seems that this is a very common problem w/ SuSE 8.0. It is not hardware related I'm sure. The problem occurs on different types of equipment for different people (i.e. different NICs, different routers, etc). In most cases, windows machines using the same equipment work just fine. I'm wondering if there is a problem w/ the dhcpcd being used in SuSE 8.0. In all fairness, sometimes it works. Just the other night after a reinstall, during boot dhcp got an IP address. But then I had to reinstall again last night (other problems :) and no matter what I did, dhcp could not get an IP address. "rcnetwork restart" showed dhcp failing on both of my linux boxes. I'm going to try a tcpdump on eth0 tonight and see what I get (not that I'll understand it though....:) Eager for a solution....... Mike ------------------------------- Cleary_Mike@emc.com ------------------------------- A wink is as good as a nod to a blind horse. -----Original Message----- From: Nick Selby [mailto:php@nickselby.com] Sent: Friday, July 26, 2002 5:48 PM To: suse-linux-e@suse.com Subject: [SLE] DHCP weirdness w/suse 8 box and USRobotics router Hi all, Yesterday I took my Suse notebook to someone else's house, set the ethernet settings on no host or domain name, checked "Change hostname by DHCP", put in no default gateway, plugged into their router and accessed the internet. I tried to keep those same settings, this time plugging into my home network with three devices plugged into a hub and then from there to a US Robotics Model 8000 broadband router, and I have a problem getting my suse machine to get an IP address from the router. The router has issued one, but the Suse machine seems to not notice it. Here's the specifics: I have a setup like this: Win2K Box ---> Hub \ Suse8 Box ---> Hub >--Router -> DSL Modem -> Internet Print Server --> Hub / The windows machine sees the router fine and vice versa with DHCP; router assigned it an IP no problem. The Print server sees the router fine and vice versa with DHCP; router assigned it an IP no problem. The SuSe 8 machine, when configured with "Let DHCP do everything" (host name and all, or with host name and domain included), cannot get assigned an IP by the router, even though the router lists the Suse on its DHCP clients list and has, as far as it can see, assigned it an IP address. SuSE box won't see this, and tells me "Network is unreachable." ifconfig shows no listing for eth0 So I take a shot at this: I assign my machine a static IP address at the top end of the IP pool of the DHCP server on the router. Kapow - I'm in and online. ifconfig shows: linux:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:D0:59:31:57:27 inet addr:192.168.123.199 Bcast:192.168.123.255 Mask:255.255.255.0 inet6 addr: fe80::2d0:59ff:fe31:5727/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:669 errors:0 dropped:0 overruns:0 frame:0 TX packets:637 errors:0 dropped:0 overruns:0 carrier:0 collisions:4 txqueuelen:100 RX bytes:218209 (213.0 Kb) TX bytes:72963 (71.2 Kb) Interrupt:11 Base address:0x1c00 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:1920 errors:0 dropped:0 overruns:0 frame:0 TX packets:1920 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:759548 (741.7 Kb) TX bytes:759548 (741.7 Kb) Nice. I ping the router and the windows box, everything works. The windows machine can ping the linux machine. A good day so far... However, the DHCP client list on the router STILL shows my computer named linux at 192.168.123.115 - which is not there! The windows machine cannot find the computer named linux (though the domain is set properly in Samba and set to share the appropriate user directory, as you'll see below). When i have W2K search for 192.168.123.199, it finds the linux machine, and I can even set up a mapped network drive. HOWEVER, while my modem dials out still, I'm not able to use its connection because my machine seems to be looking to the router to get out to the world. I was only able to send this by resetting the network settings to "Get everything by DHCP" and restarting the network. When I do that, ifconfig gives me this: linux:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:D0:59:31:57:27 inet6 addr: fe80::2d0:59ff:fe31:5727/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1390 errors:0 dropped:0 overruns:0 frame:0 TX packets:1166 errors:38 dropped:0 overruns:0 carrier:76 collisions:28 txqueuelen:100 RX bytes:355304 (346.9 Kb) TX bytes:248736 (242.9 Kb) Interrupt:11 Base address:0x1c00 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:2070 errors:0 dropped:0 overruns:0 frame:0 TX packets:2070 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:784418 (766.0 Kb) TX bytes:784418 (766.0 Kb) ppp0 Link encap:Point-to-Point Protocol inet addr:213.7.10.172 P-t-P:62.104.218.41 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:76 errors:0 dropped:0 overruns:0 frame:0 TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:20229 (19.7 Kb) TX bytes:4990 (4.8 Kb) And by the way, the router does show HWaddr 00:D0:59:31:57:27 as belonging to "Linux", so I know it's seeing the machine and at least interrogating it enough to get that info. According to the router, the linux machine should be happily barking along on 192.168.123.115 Anyone have any suggestions on how to fix all this? Many thanks in advance, nick -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com