I am working with VLANs and a BayStack 450-T without stability problems,
except when you configure NETGRAPH at the same time. The kernel crashes
during boot-up.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Tancsa
Sent: Friday, February 23, 2001 04:13
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: 802.1q vlans and STABLE


Hi,
are vlans and the fxp driver ready for prime time ? I have a situation
where I would like to deploy a simple network which looks like


[network vlan #1]-----[cat5500]-----[network vlan #2]
                          |
                          |
                          |
                    [freebsd fxp0]

The two remote networks would be trunked back to me using 802.1q encaps off
a cat 5500 switch.  I am using the patch at
http://www.euitt.upm.es/~pjlobo/fbsdvlan.html

to account for larger frame sizes. Whats not clear to me is that when
configuring fxp0, do I just assign it IPs via the vlan interface, or should
I also give fxp0 a normal IP.  Will it break things if fxp0 has an IP
associated with it ?

Also, does aliasing of vlan interfaces work as expected ?

if network #1 was 10.20.30.1/24 and 10.30.40.1/24 on vlan #123

and

network #2 was 172.16.1.1/24 and 192.168.1.1/24 on vlan #456

do I just do

ifconfig fxp0 up
ifconfig vlan0 inet 10.20.30.1 netmask 255.255.255.0 vlan 123 vlandev fxp0
mtu 1500
ifconfig vlan0 inet 10.30.40.1 netmask 255.255.255.0 alias


ifconfig vlan1 ....


Is there a limit as to the # of vlan interfaces ?  Also, do I have any
performance hits if I have too many vlans ?  If I recall correctly, in
LINUX, there used to be a performance hit if you had too many interfaces.


--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Network Administration,                           [EMAIL PROTECTED]
Sentex Communications                             www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to