When you DHCRELAY, it sends the interface's IP Address to the DHCP Server,
the DHCP Server then attempts to match that to a known subnet and assign
IP addresses from that subnet.
So if you have Segment A, Segment B, RouterA and Router B
Segment A - Router A - Segment B - RouterB
| | |
192.168.0.1 192.168.2.1 192.168.2.2
A DHCP Request from Segment A gets forwarded by Router A to Router B, it's
tagged with the router's address of 192.168.0.1. The DHCP server receives
this packet and attempts to assign it an address from the 192.168.0.X
scope (if it's defined).
In a normal situation where Router B knows about Segment A this would work
perfectly (since it has a route back to segment A). However, in my case,
RouterB is actually an AP Firewall that I (can't/don't now how) to set a
static route.
Dhcrelay doesn't just blindly forward the DHCP Requests.
I was slightly confused by the inability of parpbridge to forward dhcp
requests, but all's well that ends well.
--Pat
On Wed, 18 Dec 2002, Vladimir I. wrote:
>
> Hmm, I don't understand. Why would DHCP start to assign IPs from a
> different subnet?
>
> [EMAIL PROTECTED] wrote:
> > You can, but it affects which IP's are assigned by the DHCP server to the
> > remote segment by which "Router" Passed the information on, in this case
> > the "bogus IP Address" thereby creating another IP subnet, which isn't
> > what i want to do.
> >
> > Anyways, the AP hardware did the bridging as I expected it to passed the
> > DHCP requests over to the wireless segment and the WISP box.
>
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
