G
Guest
Guest
Archived from groups: comp.dcom.lans.ethernet (More info?)
Hi,
My provider can give me more IP addresses if and only if I can play nice
with his 802.1Q tagged VLAN network setup, with each subclassed IP
address range on its own VLAN.
For testing, I have a Debian linux laptop with a VLAN enabled kernel and
the vlan package installed, with its /etc/network/interfaces file
configured more or less like this:
--
# /etc/network/interfaces
auto lo
iface lo inet loopback
# no gateway address for eth0 itself
auto eth0
iface eth0 inet static
address w.x.y.z
netmask 255.255.255.0
## not the real vlan id
auto eth0.1234
iface eth0.1234 inet static
address 207.177.74.18
netmask 255.255.255.0
gateway 207.177.74.1
## not the real vlan id
auto eth0.2345
iface eth0.2345 inet static
address 207.177.73.226
netmask 255.255.255.240
gateway 207.177.73.225
metric 1
# repeat the above stanza 3 more times in its essentials to create
# 5 VLANS total.
--
It gives some oddball error messages, but it basically just works, and
it frees me from writing scripts using /sbin/vconfig (well done, whoever
did the integration work; even virtual addresses on top of the vlan
interfaces work).
Once I hooked it up to the Internet feed with the new 802.1Q tagged IP
address ranges coming from my provider, I could ping each VLAN interface
gateway address. Also, I can browse the web from it, so long as I set
the default route metric on one of the VLAN interfaces lower than the
others or have only one vlan interface up.
So I know the laptop sees the tagged packets. Unfortunately, if I have
all the VLAN interfaces up, I can ping only the IP addresses tied to the
VLAN interface with the metric for the default route lower than all the
others (with only one VLAN interface up, it has the lowest metric for
the default route).
What must I do to make this pig fly?
My goal is to have this laptop connected to all the vlans, and to ping
any IP I set up on any of the VLAN interfaces. Once I do that, I figure
I can set up multiple servers connecting to the VLANS with arbitrary IP
addresses using a managed switch easily enough.
--
Christopher L. Everett
Chief Technology Officer www.medbanner.com
MedBanner, Inc. www.physemp.com
Hi,
My provider can give me more IP addresses if and only if I can play nice
with his 802.1Q tagged VLAN network setup, with each subclassed IP
address range on its own VLAN.
For testing, I have a Debian linux laptop with a VLAN enabled kernel and
the vlan package installed, with its /etc/network/interfaces file
configured more or less like this:
--
# /etc/network/interfaces
auto lo
iface lo inet loopback
# no gateway address for eth0 itself
auto eth0
iface eth0 inet static
address w.x.y.z
netmask 255.255.255.0
## not the real vlan id
auto eth0.1234
iface eth0.1234 inet static
address 207.177.74.18
netmask 255.255.255.0
gateway 207.177.74.1
## not the real vlan id
auto eth0.2345
iface eth0.2345 inet static
address 207.177.73.226
netmask 255.255.255.240
gateway 207.177.73.225
metric 1
# repeat the above stanza 3 more times in its essentials to create
# 5 VLANS total.
--
It gives some oddball error messages, but it basically just works, and
it frees me from writing scripts using /sbin/vconfig (well done, whoever
did the integration work; even virtual addresses on top of the vlan
interfaces work).
Once I hooked it up to the Internet feed with the new 802.1Q tagged IP
address ranges coming from my provider, I could ping each VLAN interface
gateway address. Also, I can browse the web from it, so long as I set
the default route metric on one of the VLAN interfaces lower than the
others or have only one vlan interface up.
So I know the laptop sees the tagged packets. Unfortunately, if I have
all the VLAN interfaces up, I can ping only the IP addresses tied to the
VLAN interface with the metric for the default route lower than all the
others (with only one VLAN interface up, it has the lowest metric for
the default route).
What must I do to make this pig fly?
My goal is to have this laptop connected to all the vlans, and to ping
any IP I set up on any of the VLAN interfaces. Once I do that, I figure
I can set up multiple servers connecting to the VLANS with arbitrary IP
addresses using a managed switch easily enough.
--
Christopher L. Everett
Chief Technology Officer www.medbanner.com
MedBanner, Inc. www.physemp.com