8.0-REL lagg(4) + vlan(4) + em(4) problems
I've just upgraded a 7.1-REL server to 8.0-REL and have lost my ability to use vlan(4) on top of lagg(4) on top of em(4). (Not sure about other interface types, just encountered the problem tonight.) Using tcpdump, I see that I can receive 802.1q-tagged traffic (and on the correct VLAN interface), but the switch appears to receive frames from the server without 802.1q tags--the only bridge entry on the switch port is on the "default" untagged VLAN. Setting the switch port to untagged and configuring lagg0 with an IP address works fine (bidirectionally), and making em0 or em1 the vlandev for the VLAN interface also works fine. My ems, in case the problem is there and not in lagg: e...@pci0:5:0:0: class=0x02 card=0x135e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)' class = network subclass = ethernet e...@pci0:5:0:1: class=0x02 card=0x135e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'HP NC360T PCIe DP Gigabit Server Adapter (n1e5132)' class = network subclass = ethernet I didn't see anything about this on current@, stable@, or here over the last few months, only at the FreeBSD forums (http://forums.freebsd.org/showthread.php?t=7668). There's also open PR kern/132715, but I'm not experiencing panics, just incorrect behaviour. Is my issue known in any way? Any suggestions other than filing a PR (which I'll be happy to do)? thanks, Jeff ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 8.0-REL lagg(4) + vlan(4) + em(4) problems
I wrote: > I've just upgraded a 7.1-REL server to 8.0-REL and have lost my > ability to use vlan(4) on top of lagg(4) on top of em(4). I should have mentioned that I'm using lagg failover. I can reproduce my problem in single-user as follows: # ifconfig em0 up # ifconfig em1 up # ifconfig lagg0 create laggproto failover laggport em0 laggport em1 up # ifconfig vlan20 create vlan 20 vlandev lagg0 # ifconfig vlan20 / up Jeff ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
patch: ndisusb: show device description on attach
--- /sys/dev/if_ndis/if_ndis_usb.c 2009-11-25 21:49:03.0 + +++ if_ndis_usb.c 2009-12-12 12:17:27.0 + @@ -165,6 +165,7 @@ driver_object *drv; int devidx = 0; + device_set_usb_desc(self); db = uaa->driver_ivar; sc = (struct ndis_softc *)dummy; sc->ndis_dev = self; -- Paul B Mahol ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/141376: [ndis] [patch] broken scan by passing ies and ies_len pointer to net80211
On 12/11/09, lini...@freebsd.org wrote: > Old Synopsis: ndis: broken scan > New Synopsis: [ndis] [patch] broken scan by passing ies and ies_len pointer New Synopsis: [ndis] [patch] broken scan by _not_ passing ies and ies_len pointer > to net80211 > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Fri Dec 11 19:48:19 UTC 2009 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=141376 > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > -- Paul B Mahol ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 10gigE link with FreeBSD hosts ?
>Can't get 10 gigabit thru a PCI-X slot, it doesnt have the bandwidth, you need >PCI Express, in >fact you will find that lots of factors will come into play and might keep you >from achieving >optimal thruput. > >>For a two port adapter you will need an 8x PCIE slot, preferably Gen 2, and >>if all three systems >don't have that its gonna slow everyone down. > >Further, once you involve packet forwarding it gets even more demanding. > >Trying to do it 'on the cheap' and you might get 3 or 4 Gb, maybe even worse >depending. Thanks. I just spoke of pci-x because that was the form factor of the Sun adapter. Ok, so let's say I have pci-e 16 or 8x for all adapters, again with the same "just out of date" commodity pcs (intel core or c2d, etc.) and the same network layout: (a) <-- cable --> (b) <-- cable --> (c) you're saying I can start to approach actual 10 gb/s throughput ? I guess there is one layer of packet forwarding in place, since I am bridging on (b) ... but is that going to just be a small (10% ?) hit, or are we talking 50% ? Finally, are a few (5 or 6) simple ipfw rules (like, block tcp 130, or block xmas tree packets, etc.) going to kill me ? Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/141414: [vge] vge(4) problem on 8.0-RELEASE
Synopsis: [vge] vge(4) problem on 8.0-RELEASE Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Dec 13 02:04:19 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141414 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
