Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just set up a small DHCP server on my local area network, and I was attempting to give different IP addresses out depending on the type of connection -- wired clients would get IPs from one pool, wireless from another. Not being able to find either the answer or the right search terms to find suggestions, I turn to you.
Since wireless traffic must pass through the wireless router on my network, is there a way for me to map any traffic passing through device X (known mac address) into a different pool than devices hardwired to my switch? I'd rather not filter every potential wireless card manufacturer's mac address prefix, as many of the manufacturers also make wired cards.
The reason behind this is that I will be using iptables to filter a lot of traffic from wireless devices who have received DHCP addresses, where as my known hosts sit safely on a different range.
If I am understanding this correctly, the server is hardwired to a consumer-type router/AP, which is allowing both wired and wireless devices to connect to the network?
So then, all DHCP requests would be received on a single Ethernet interface on the server?
Currently the wireless AP connects to a switch, into which the server is plugged. In other words, yes, all requests will be coming through the same interface.
Well, I am no expert on DHCPD, but from my understanding that is going to be a problem. If you had requests coming from two interfaces you could give them separate scopes; but with everything coming from one interface it seems like you would have to fall back on MAC filters which are certainly not ideal, as you said.
Would it be possible in your current setup to physically connect the AP to a second network card in the server?
Unfortunately by the constraints of the server I cannot fit any more network cards into the box, and this isn't so crucial as to necessitate another NIC being installed. I didn't know if I could shape traffic, for lack of a better phrase, based on the router through which it first entered.
I admit I haven't taken a look at deep packet inspection to see how the routers add information to the packets, if at all.
Thanks, but the current network configuration is that it would be easier to leave the AP plugged into the switch. If it can't be done I'll just have to go the manufacturer route.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.