the same to the user via vlan 10.
Regards
DS
From: Joshua Morgan joshua.mor...@gmail.com
To: Markus H hauschild.mar...@gmail.com
Cc: cisco-nsp@puck.nether.net cisco-nsp@puck.nether.net
Sent: Sunday, March 10, 2013 4:51 AM
Subject: Re: [c-nsp] DHCP Forwarding
I've just read the Option 82 topic which brings to memory an unsolved
prolbem I had:
The current state of a network for a rather small event:
At the core a Cisco 3550, a few 2950s and non-Cisco WLAN APs (the APs
just map a few SSIDs onto the corresponding VLANs with either no
encryption (guest)
So is there anything I am missing? Is there any good documentation on
what information forwarded DHCP requests have by default or what things
I can add (besides the quite useless port number where the request came
in)?
Look at
On Sunday, 10 March 2013, Markus H wrote:
What I would like it to be:
The 3550 forwards DHCP requests to the DHCP VM. The VM decides (based
on which VLAN the client is in) from which pool to give out an address
and needs only one interface/ip. Further benefit: the VM server needs
to deal
What you're trying to achieve (mapping a client's request to a source VLAN
so that the DHCP server knows which pool/scope to serve from) is done out
of the box - the DHCP relay (configured using the ip helper-address
interface configuration command) will insert its IP address of the
interface that
