Date: Sun, 15 Sep 2002 17:22:26 +0200 From: sthaug@nethelp.no To: stesin@breaker.tormoz.net Cc: mike@sentex.net, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Bug? VLANs, fxp, Catalyst and link0 story Message-ID: <74847.1032103346@verdi.nethelp.no> In-Reply-To: Your message of "Sun, 15 Sep 2002 18:05:29 %2B0300 (EEST)" References: <20020915175929.T1070-100000@chour.hostmaster.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Why do you need the link0 portion ? > > For "carrier" interface? Sorry I don't know. :( It doesn't work without > it. For vlanXX interfaces, manpage states that link0 enables hardware > (firmware) processing of 802.1q tags in Intel ethernet chips. It is > supposed to work, doesn't it? Here's an example of what works for me: pseudo-device vlan 10 #VLAN support ifconfig_fxp1="up" ifconfig_vlan0="inet 194.19.1.42 netmask 255.255.255.252 vlan 24 vlandev fxp1" ifconfig_vlan1="inet 10.65.0.254 netmask 0xffffff00 vlan 57 vlandev fxp1" On the Cisco 3548 switch: interface FastEthernet0/48 switchport trunk encapsulation dot1q switchport mode trunk Note that the native VLAN on this trunk is VLAN 1, and I'm specifically *not* using this VLAN for anything. (802.1q native VLAN is an incredibly bad idea, IMHO. But that's another discussion entirely.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74847.1032103346>