Date: Sun, 28 Nov 2004 17:02:37 +0000 (GMT) From: Robert Watson <rwatson@freebsd.org> To: Kevin Day <toasty@dragondata.com> Cc: freebsd-net@freebsd.org Subject: Re: em(4) VLAN + PROMISC still doesn't work with latest CVS version Message-ID: <Pine.NEB.3.96L.1041128161659.94120E-100000@fledge.watson.org> In-Reply-To: <35FC873E-40BF-11D9-8850-000A95A8A1F2@dragondata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 Nov 2004, Kevin Day wrote: > I recently upgraded to 5.3 on a system, and manually upgraded > src/sys/dev/em/* to the latest RELENG_5 versions. (1.44.2.4 of if_em.c) I'm able to reproduce problems using the below configuration is 6.x also, and am investigating. Thanks for the report, hope to get back to you shortly with something concrete. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > While the VLAN side of things works better than the stock 5.3 version, > there still is this problem: > > > ifconfig vlan1 create > ifconfig vlan1 vlan 1 vlandev em1 link0 > ifconfig vlan2 create > ifconfig vlan2 vlan 2 vlandev em1 link0 > ifconfig vlan3 create > ifconfig vlan3 vlan 3 vlandev em1 link0 > > ifconfig vlan1 inet 192.aaa.bbb.129 netmask 255.255.255.0 > ifconfig vlan2 inet 64.ccc.ddd.61 netmask 255.255.255.192 > ifconfig vlan3 inet 64.eee.fff.61 netmask 255.255.255.192 > > ifconfig em1 up > ifconfig em1 promisc > > If I do this, vlan1 and vlan3 work fine. Vlan2 can receive packets, but > anything sent out vlan2 doesn't seem to be heard by any foreign hosts. > Setting "ifconfig em1 -promisc" makes all vlans work properly. > > This is better than the stock 5.3 version of em(4) where none of the > vlans worked, but something still isn't right. > > Is this a known problem still or am I just doing something wrong? > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041128161659.94120E-100000>