Date: Tue, 07 Dec 2004 16:22:16 +0200 From: Iasen Kostov <tbyte@OTEL.net> To: Iasen Kostov <tbyte@OTEL.net> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: em(4) VLAN + PROMISC still doesn't work with latest CVS version Message-ID: <41B5BC98.2080408@OTEL.net> In-Reply-To: <41AB0B98.6020600@OTEL.net> References: <Pine.NEB.3.96L.1041128161659.94120E-100000@fledge.watson.org> <41AB0B98.6020600@OTEL.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Iasen Kostov wrote: > Robert Watson wrote: > >> 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? >>> >>> >>> >>> >>> >> > Saddly I can just confirm that :( > > regards > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > Is there an update on this case or I should find a way to disable all hw "things" in the driver ?:) (because things are getting hot here :). regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41B5BC98.2080408>