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.
Hello all. I'm running a DHCP server that listens on my wireless access point to provide internal network addresses to client computers. Then they are able to access my external interface through my shorewall. The problem is that DHCP does not want to start without a subnet declaration for the eth0 external interface, which is assigned via DHCP by my ISP. I have given it the current IP of the external interface in a subnet declaration just to shut it up and make it run, but the next time the IP changes, I'll have to update the DHCPD.conf, which I don't want to have to do all the time. Here are the contents of my current dhcpd.conf, including the interim subnet declaration
Thanks for the info, MQM. It seems the problem was that I had to start DHCP with the interface I wanted it to listen to as an argument. Otherwise it would try to pay attention to its hardcoded target eth0, even though it's not in dhcpd.conf.
Oh yes. You need to restrict dhcpd to the interface that handles your internal network. If you accidentally start it on your "internet connection" interface, then your ISP will get very upset, when you start handing out IPs instead of them. LOL