VLANS and DHCP

[King, Michael]

Maybe you know this maybe you don't.

Where-ever your setting up these VLAN's (and I'm assuming they are a
router).

Most (If not all) routers have the concept of IP helper statements.  IP
helpers just relay the information to the designated DHCP server.

If you define the subnet in the DHCP server, it can figure it out and
"It just works"

What are you using to define your VLAN's?

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
Behalf Of Steve Wenger
Sent: Friday, August 18, 2006 12:18 AM
To: dhcp-users at isc.org
Subject: Re: VLANS and DHCP

I will be running it on Fedora Core 5,  I am going to have approx 100
total vlans to start, and I know it can be done I am just not sure how
to get it done.

Steve Wenger
Nconnect Internet and High Speed Wireless.
Got a need for speed?  We have a solution for you!


-----Original Message-----
From: Michael Loftis <mloftis at wgops.com>
To: dhcp-users at isc.org
Date: Thu, 17 Aug 2006 20:27:59 -0600
Subject: Re: VLANS and DHCP

> 
> --On August 17, 2006 9:09:53 PM -0500 Steve Wenger 
> <steve at nconnectwireless.com> wrote:
> 
> > I am currently running a wireless network with over 2ooo clients
> attached
> > to  50 different access points,  I will be reconfiguring the network
> and
> > setting  up different VLANS for each tower location.  I want to use
> one
> > centralized  DHCP server so I need to configure a DHCP server that
> can
> > assign clients  addresses from multiple address blocks both public
> and
> > private based upon  the VLAN that the client is part of.  Can anyone

> > point me to some  documentation on how to accomplish this.
> > Steve Wenger
> > Nconnect Internet and High Speed Wireless.
> > Got a need for speed?  We have a solution for you!
> 
> What platform?  Linux and FreeBSD both support an 802.1q/VLAN 
> encapsulation driver.  I've used both to run DHCP and they work very 
> well.  They both expose an interface to DHCPd, so there's nothing 
> 'special' as far as DHCPd is concerned.  In Linux there's an option 
> you have to sometimes set that makes sure the Layer2 Ethernet headers 
> are correct in order to make certain the DHCPd works.  In any case 
> it's not the DHCPd that does the VLAN interface, it's the host OS.
>