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.
I've seen something when working for a customer and I've never figured out if it was doable with Linux boxes... that's not really because I need it, but I'm interested in how this could/would work.
So, my customer has got a huge LAN made of Cisco boxes. He has many VLANs, each in a different subnet. They are connected through layer 3 switches (4 catalysts 6000 routing through OSPF as a matter of fact).
It's time to use sample config.... let's say that :
VLAN1 is 192.168.1.0/24, that's for the PC
VLAN2 is 192.168.2.0/24, that's for the servers
There's only one dhcp server : 192.168.2.1
When a PC requests for an IP, the layer 3 switch that receives the request forwards it to the dhcp server (because the dhcp server's IP is configured in the switch) and uses the IP of the interface that received the request as a source IP for the forwarded dhcp request.
The dhcp server receives the request, sees the source IP and thus knows in what subnet it must select the IP to send back. So he replies to the layer 3 switch which in turn forwards the dhcp response to the PC.
I know how to set this up on Cisco routers, that's a single command line :
ip helper-address 192.168.2.1
What I wonder is :
1/ How could we do this with a Linux router ?
2/ How could we configure a Linux dhcp server to work like this ? Do you think that configuring all subnets on the dhcpd.conf file would be enough (maybe... as a matter of fact, there's no specification in the Cisco configuraiton guides on what dhcp server must be used, so it may be a standard) ?