Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
My current setup consists of 3 machines (2 Linux, 1 Windows XP), all connected through a Linksys router. The linksys router has DHCP enabled and all 3 computers can pickup ip addresses from the linksys router.
what i am trying to do is allow one linux machine to pickup an ip address from the other linux machine rather then the linksys router. here is what i have done so far:
1. added the MAC address of the linux machine that is going to pickup an ip address to the filter list of my linksys router (so as to not send an ip from the linksys)
2. dhcpd.conf script looks as follows:
# Configuration file for ISC dhcpd v3.0
ddns-update-style none; # required for ISC v3.0
I had a similar situation and I just ended up disabling the router's dhcp server. I normally check the router's status page to see whether the info has changed. If it did, I changed the dhcp server's info to match. The only difference in my situation is that the clients always got IP info from the linux dhcp server even though both dhcp servers were running. The clients would only get the router's dhcp info only if the linux dhcp was turned off.
Originally posted by sidmark-2850 I had a similar situation and I just ended up disabling the router's dhcp server. I normally check the router's status page to see whether the info has changed. If it did, I changed the dhcp server's info to match. The only difference in my situation is that the clients always got IP info from the linux dhcp server even though both dhcp servers were running. The clients would only get the router's dhcp info only if the linux dhcp was turned off.
Your problem would be nice in my scenario =)
I do belive thats that the "non authoritative" line is for in the dhcpd.conf, it does resolve the issue of the linux dhcp server taking over the entire network.
if a client is looking for a DHCP server, it will use the server which responded the fastest on his request. So in the case of 330pilot, the router was faster than the linux pc (most of the time anyway). in the case of sidmark-2850 the linux pc was faster than the router.
As far as I know there is no way of telling a client which DHCP server to use. It will always pick the one which answered the fastest to his request.
330Pilot, I have a linksys router and am in the exact situation. I do not have the "non authoritative" statement in my dhcpd.conf file. Double checking, I have both dhcp servers on right now and I always get the IP from the linux box unless it is turned off. That is the only time I get the address from the router. The dhcp server is plugged directly to the router's ports and I have a hub plugged to the router's uplink port. I sometimes have problems with a machine plugged to the hub as it won't get an address from either dhcp server. I ended up configuring it statically, which really sucks. That machine has a really long cable though. I am not sure about the length, but it communicates just fine with the other machines on the network. The other machines plugged to the hub have shorter cables and there is no issue with obtaining addressed. Play around with the authoritative statements and see whether that makes a difference.