Menu
▾
▴
Re: [Devil-Linux-discuss] [BULK] Re: Slightly OT: DHCPD and 802.1q trunk
|
From: Frank W. <Fra...@ct...> - 2008-03-06 10:09:02
|
Hi again,
let me explain the problem I experience:
I have two ranges on my dhcp server, that should be distributed to clients on
the two vlans:
shared-network LAN {
subnet 192.168.123.0 netmask 255.255.255.0 {
range 192.168.123.50 192.168.123.100;
default-lease-time 60000;
max-lease-time 72000;
option broadcast-address 192.168.123.255;
option domain-name "ebac";
option routers 192.168.123.1;
}
subnet 10.0.0.0 netmask 255.255.0.0 {
range 10.0.0.100 10.0.0.200;
default-lease-time 60000;
max-lease-time 72000;
option broadcast-address 10.0.255.255;
option domain-name "lan";
option routers 10.0.0.1;
}
}
Both ranges are on two VLANs on the same physical NIC:
vlan100 Link encap:Ethernet HWaddr 00:10:F3:12:52:7D
inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.255.0.0
vlan103 Link encap:Ethernet HWaddr 00:10:F3:12:52:7D
inet addr:192.168.123.1 Bcast:192.168.123.255 Mask:255.255.255.0
Unfortunately, hosts in both VLANs get addresses from the same pool....
Thanks for your input!
Frank
On Thursday 06 March 2008 10:46:53 John Jore wrote:
> Frank,
> VLANs can be considered "virtual network cards" with separate IP subnets. A
> client would only be on one or the other VLAN, never on both at the same
> time. dhcpd should not have any issues with this nor would you need to
> reconfigure you clients. I run DL with VLANs myself.
>
> Or I might have completely misunderstood your email....
>
>
> Regards,
> John Jore
>
> ________________________________________
> From: dev...@li...
> [dev...@li...] On Behalf Of Frank Weis
> [Fra...@ct...] Sent: 06 March 2008 08:22
> To: dev...@li...
> Subject: [Devil-Linux-discuss] Slightly OT: DHCPD and 802.1q trunk
>
> Hi all,
>
> I wonder if it is possible to have a trunked port, let's say vlan10 and
> vlan20 on the same NIC, and have dhcpd distribute different address pools
> to clients in the vlans? The vlan-tag is certainly stripped off the packet
> before it is passed to dhcpd, so dhcpd has no way of knowing which vlan the
> request came from.
>
> I know there is some possibility to configure the clients to include some
> label in the request, and differenciate them using that on the server, but
> that would mean reconfigureing all the clients....
>
>
> Thanks for any ideas,
>
> Frank
> --
> _______________________________________________
> Centre de Technologie de l'Education
> 29 avenue John F. Kennedy
> L-1855 Luxembourg-Kirchberg
> email: Fra...@ct...
> tél.: +352 247-85973
> fax: +352 333797
> _______________________________________________
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
--
_______________________________________________
Centre de Technologie de l'Education
29 avenue John F. Kennedy
L-1855 Luxembourg-Kirchberg
email: Fra...@ct...
tél.: +352 247-85973
fax: +352 333797
_______________________________________________
|
