Thats the thing, the native vlan is a different vlan. Native is also
untagged, all the other allowed vlans are tagged. If I create a single
interface tagged on a non-native allowed vlan it works. However creating
multiple tagged aliases is unclear, and I have not made it work yet.

On 7/18/07, Jack Neely <[EMAIL PROTECTED]> wrote:

On Tue, Jul 17, 2007 at 02:33:02PM -0400, [EMAIL PROTECTED] wrote:
>  X-Posted to the regular redhat list.
>
>  So I have a small issue. I have a machine with two interfaces, one on
vlan X
>  and one on vlan Y. I need 4 aliases on vlan X so I have eth0, trying to
>  create the four aliases using the standard vlan configuration does not
work.
>  Creating config files names eth0: 1.X does nothing, the files get
ignored.
>  Using the same config file with a different interface name works (
eth0.X), I
>  have also tried doing eth0.X:1 and that does nothing either.
>
>  So in short is there a way to either tag all of the traffic on a NIC
(ie
>  eth0) or to have multiple aliases on the same vlan ?

The vlan tagging wont work unless the switch you are connected to is
configured to trunk those vlans to your server.  If you've got two NICs
attached to two different vlans its most likely setup so that you just
see the two different networks and don't need to bother with any vlan
magic.  So creating eth0:1, eth0:2 should work fine for getting aliases
on vlan X.

Jack Neely

--
Jack Neely <[EMAIL PROTECTED]>
NCSU Campus Linux Services Lead
Information Technology Division, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to