RE: [SuSE Linux] networking - DHCP
Gerry Doris wrote:
Start yeast, go into System Administration, Network Configuration, dhcp client.
Hi, just as I see this thread...Did anybody get dhcpd-client working under SuSE 6.1? I didn't. I saw the dhcpd-server receiving the DHCP request from the client, I saw the server sending the right answer and I saw the client running the script: /sbin/dhclient-script (referenced in /etc/dhclient.conf) with the right network parameters. But no device was configured and no route was set. I then tried to setup the network by the use of the kernel's bootp mechanism. This works and I still use this work arround. But DHCP would be even nicer. Thanks, Ruben -- Dr. Ruben Schattevoy <A HREF="http://www.biochem.mpg.de/~schattev"><A HREF="http://www.biochem.mpg.de/~schattev</A">http://www.biochem.mpg.de/~schattev</A</A>> Max-Planck-Institut of Biochemistry <A HREF="mailto:schattev@biochem.mpg.de">mailto:schattev@biochem.mpg.de</A> Am Klopferspitz 18a Voice +49(89)8578-2723 82152 Planegg/Munich, Germany Fax +49(89)8578-2479 -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Hello, On Fri, Jun 04, Ruben Schattevoy wrote:
Gerry Doris wrote:
Start yeast, go into System Administration, Network Configuration, dhcp client.
Hi,
just as I see this thread...Did anybody get dhcpd-client working under SuSE 6.1? I didn't. I saw the dhcpd-server receiving the
Yes, on all of my Test PCs without problems.
DHCP request from the client, I saw the server sending the right answer and I saw the client running the script:
/sbin/dhclient-script (referenced in /etc/dhclient.conf)
with the right network parameters. But no device was configured and no route was set. I then tried to setup the network by the use of the kernel's bootp mechanism. This works and I still use this work arround. But DHCP would be even nicer.
Make sure that the dummy device is disabled. run /sbin/init.d/dhclient start That's all I need to do. Thorsten -- Thorsten Kukuk <A HREF="http://www.suse.de/~kukuk/"><A HREF="http://www.suse.de/~kukuk/</A">http://www.suse.de/~kukuk/</A</A>> kukuk@suse.de SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg Linux is like a Vorlon. It is incredibly powerful, gives terse, cryptic answers and has a lot of things going on in the background. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Thorsten Kukuk wrote:
Make sure that the dummy device is disabled. run /sbin/init.d/dhclient start
That's all I need to do.
Well, it does not work for me! I have tested it again. The dummy device is turned off, BOOTP still works but the dhclient scripts just overwrites the proper network setting from the kernels BOOTP by it's initial values and never replaces them by the proper parameters. This is part of the /var/log/messages Jun 4 16:21:21 rzpc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Jun 4 16:21:21 rzpc dhclient: DHCPOFFER from 141.61.16.2 which proves that the dhclient has gotten an answer from out BOOTP/DHCP-Server. Any more ideas, what could be wrong on my side? Thanks, Ruben -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Ruben Schattevoy wrote:
Thorsten Kukuk wrote:
Make sure that the dummy device is disabled. run /sbin/init.d/dhclient start
That's all I need to do.
Probably because Thorsten's router to his ISP is a "configurationless" router, similar to the Cisco 675.
Well, it does not work for me! I have tested it again. The dummy device is turned off, BOOTP still works but the dhclient scripts just overwrites the proper network setting from the kernels BOOTP by it's initial values and never replaces them by the proper parameters.
This is part of the /var/log/messages
Jun 4 16:21:21 rzpc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Jun 4 16:21:21 rzpc dhclient: DHCPOFFER from 141.61.16.2
which proves that the dhclient has gotten an answer from out BOOTP/DHCP-Server.
Any more ideas, what could be wrong on my side?
Thanks,
Ruben
-- JLK Linux, because it's STABLE, the source code is included, the price is right. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (3)
-
jlkreps＠navix.net -
kukuk＠suse.de -
schattev＠biochem.mpg.de