Determining request

[Tim Gavin]

I'd use vlans on your switch, if it's managed.  The server and DHCP
will recognise vlans like separate interfaces.

it also helps you shape your traffic if you need such a thing at a
future date, and contain outbreaks if you have them.



On Tue, Jan 5, 2010 at 12:09, Matt Causey <matt.causey at gmail.com> wrote:
> On Tue, Jan 5, 2010 at 12:00 PM, Ashley M. Kirchner <ashley at pcraft.com> wrote:
>>
>>   Is there a way to detect whether a request came in from a wired network
>> versus a wireless network?  Our setup is as follows:
>>
>>   Main DHCP server that dishes out IPs based on MAC addresses.  This is
>> wired into our main switch.  From that switch I also have a wireless access
>> point.  A wireless device will send a request out which goes through the
>> access point to the DHCP server and back.  The wireless class is set to
>> allow unknown-clients.
>>
>>   If a wired device sends a request, and it has *not* been defined already
>> through it's MAC, DHCP will automatically drop it in the wireless group and
>> pool.  I don't want that.  For our wired network, I don't want anything to
>> be able to get an IP unless it's already defined.  For the wireless one,
>> they should all go in the wireless pool and get an IP from there.
>>
>>   So, is there some way to determine if a request came in from a wired
>> device versus a wireless one?
>>
> Depending on the capabilities of your LAN/WLAN gear....and how the
> DHCP traffic flows, you might be able to use some option 83 foo to
> accomplish that.
>
> --
> Matt
>
>>   A
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>