Date: Fri, 23 Feb 2001 15:22:57 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Mike Tancsa <mike@sentex.net> Cc: stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 802.1q vlans and STABLE Message-ID: <20010223152257.K36182@gsmx07.alcatel.com.au> In-Reply-To: <4.2.2.20010222215259.03d78d60@marble.sentex.net>; from mike@sentex.net on Thu, Feb 22, 2001 at 10:13:20PM -0500 References: <4.2.2.20010222215259.03d78d60@marble.sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-Feb-22 22:13:20 -0500, Mike Tancsa <mike@sentex.net> 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 Address Ipkts Ierrs Opkts Oerrs Coll dc0* 1500 <Link#1> 08:00:2b:c3:6b:b9 0 0 0 0 0 fxp0 1500 <Link#2> 00:d0:b7:20:8f:ee 252636245 0 252026018 0 0 fxp0 1500 none none 252636245 0 252026018 0 0 fxp1* 1500 <Link#3> 00:d0:b7:20:bd:ab 0 0 0 0 0 xl0* 1500 <Link#4> 00:c0:4f:ba:32:2b 0 0 0 0 0 vlan0 1500 <Link#5> 00:d0:b7:20:8f:ee 51854151 0 24998001 0 0 vlan0 1500 net91/24 aalp02-a0 51854151 0 24998001 0 0 vlan1 1500 <Link#6> 00:d0:b7:20:8f:ee 0 0 2 0 0 vlan1 1500 net155 aalp02-a1 0 0 2 0 0 vlan2 1500 <Link#7> 00:d0:b7:20:8f:ee 90580612 0 128663939 0 0 vlan2 1500 net156 aalp02-l0 90580612 0 128663939 0 0 vlan3 1500 <Link#8> 00:d0:b7:20:8f:ee 9104283 0 9104999 0 0 vlan3 1500 net157 aalp02-l1 9104283 0 9104999 0 0 vlan4 1500 <Link#9> 00:d0:b7:20:8f:ee 93593008 0 81969794 0 0 vlan4 1500 net158 aalp02-r0 93593008 0 81969794 0 0 vlan5 1500 <Link#10> 00:d0:b7:20:8f:ee 7504326 0 7289701 0 0 vlan5 1500 net159 aalp02-r1 7504326 0 7289701 0 0 lo0 16384 <Link#11> 8 0 8 0 0 lo0 16384 127 localhost 8 0 8 0 0 ds0* 65532 <Link#12> 0 0 0 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 majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010223152257.K36182>