Re: 802.1q vlans and STABLE

2001-02-23 Thread Julian Elischer

Peter Blok wrote:
 
 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.
 

huh?  can you give me more on this?

-- 
  __--_|\  Julian Elischer
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000-2001
--- X_.---._/  
v

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



RE: 802.1q vlans and STABLE

2001-02-22 Thread Peter Blok

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



Re: 802.1q vlans and STABLE

2001-02-22 Thread Peter Jeremy

On 2001-Feb-22 22:13:20 -0500, Mike Tancsa [EMAIL PROTECTED] wrote:
are vlans and the fxp driver ready for prime time ?

I've been running a system with 6 VLANs on an fxp for about 6 months
now without problems.  The system has currently been up nearly 3 weeks
(following a blackout) and had been up for 2 1/2 months before that.
netstat -I gives:

aalp02# netstat -i
Name  Mtu   Network   AddressIpkts IerrsOpkts Oerrs  Coll
dc0*  1500  Link#108:00:2b:c3:6b:b90 00 0 0
fxp0  1500  Link#200:d0:b7:20:8f:ee 252636245 0 252026018 0 0
fxp0  1500  none  none252636245 0 252026018 0 0
fxp1* 1500  Link#300:d0:b7:20:bd:ab0 00 0 0
xl0*  1500  Link#400:c0:4f:ba:32:2b0 00 0 0
vlan0 1500  Link#500:d0:b7:20:8f:ee 51854151 0 24998001 0 0
vlan0 1500  net91/24  aalp02-a0   51854151 0 24998001 0 0
vlan1 1500  Link#600:d0:b7:20:8f:ee0 02 0 0
vlan1 1500  net155aalp02-a1  0 02 0 0
vlan2 1500  Link#700:d0:b7:20:8f:ee 90580612 0 128663939 0 0
vlan2 1500  net156aalp02-l0   90580612 0 128663939 0 0
vlan3 1500  Link#800:d0:b7:20:8f:ee  9104283 0  9104999 0 0
vlan3 1500  net157aalp02-l19104283 0  9104999 0 0
vlan4 1500  Link#900:d0:b7:20:8f:ee 93593008 0 81969794 0 0
vlan4 1500  net158aalp02-r0   93593008 0 81969794 0 0
vlan5 1500  Link#10   00:d0:b7:20:8f:ee  7504326 0  7289701 0 0
vlan5 1500  net159aalp02-r17504326 0  7289701 0 0
lo0   16384 Link#118 08 0 0
lo0   16384 127   localhost  8 08 0 0
ds0*  65532 Link#120 00 0 0
aalp02#

http://www.euitt.upm.es/~pjlobo/fbsdvlan.html

That's where I got my code last August.  I haven't looked to see what
has changed since then.  I know I have patches for:
- set the "Long Receive OK" bit in the i82559 (fxp) [rather than
  rummage through "error packets"]
- support VLANs on the TI ThunderLan (tl driver)
- support VLANs on the SMC 9432TX (tx driver)
- VLAN support in driver modules for the above drivers
- fix VLAN handling in arp(8)
- support VLANs in tcpdump(8) [this may be in the generic tree by now]

configuring fxp0, do I just assign it IPs via the vlan interface, or should 
I also give fxp0 a normal IP.

The fxp0 interface doesn't need an IP address, but you will need to
explicitly `up' it with a line in /etc/rc.conf like:
ifconfig_fxp0="up media 100baseTX mediaopt full-duplex"

  Will it break things if fxp0 has an IP associated with it ?
No, but at least the Alcatel (Xylan) switch I'm using won't
send `normal' ethernet packets once the port has been designated
as a VLAN trunk.

Also, does aliasing of vlan interfaces work as expected ?

I don't know any reason why it wouldn't, but haven't tried.  I
_am_ using proxy ARP on one of the VLAN interfaces.

Is there a limit as to the # of vlan interfaces ?

There used to be some hard limits on total interfaces (16 or 32,
I can't remember which) - I'm not sure when the fix was MFC'd.
I don't believe there is any hard limit on the number of VLANs,
but I've never tried more than 6.

  Also, do I have any 
performance hits if I have too many vlans ?

On incoming 802.1Q packets, there's a linear search through a list of
known VLAN numbers to determine the destination vlan device.  Unless
you're planning on lots of VLAN's, this probably isn't an issue.

Peter

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