Re: kern/140712: [fxp] fxp driver starts with rxcsum on
Synopsis: [fxp] fxp driver starts with rxcsum on State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Fri Nov 20 22:03:13 UTC 2009 State-Changed-Why: I belive the fix was committed to HEAD(r197586) and MFCed to stable/8 and stable7 but it didn't make it into 8.0-RELEASE. To workaound the issue you can disable Rx checksum offload of fxp0. #ifconfig fxp0 -rxcsum Or download patch from the following URL. http://svn.freebsd.org/viewvc/base/head/sys/dev/fxp/if_fxp.c?r1=197586&r2=197575&view=patch Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Fri Nov 20 22:03:13 UTC 2009 Responsible-Changed-Why: Track. http://www.freebsd.org/cgi/query-pr.cgi?pr=140712 ___ 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/140728: [em] [patch] Fast irq registration in em driver
Old Synopsis: Fast irq registration in em driver New Synopsis: [em] [patch] Fast irq registration in em driver Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Nov 20 23:09:35 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140728 ___ 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: bce(4) BCM5907 CTX write errors on 7.2 driver
> > For the record we also have not been able to reproduce the issue on > > the R710 only the R610. > > I got hold of an R610 system and I now understand why the > issue was difficult to replicate on R710. The R610 ships > without Enterprise iDRAC while the R710 ship with the add-in > Enterprise iDRAC module. When the module is present the > system is managed through the additional RJ45 port but when > the module is absent iDRAC traffic will flow through the > on-board 5709 adpaters. > The error will only occur when management firmware is loaded > on the 5709 AND when NC-SI management functionality is enabled. > > You should be able to confirm this by adding or removing the > Enterprise iDRAC module on your systems. Now that I have a > failure again I have some ideas to test which might help. > Stay tuned. Does the attached patch make a difference for you? FYI, I'll be out next week on vacation. Dave if_bce.diff Description: if_bce.diff ___ 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"
ipfw not blocking inter jail ip traffic
iH, Have 2 jails and I don't want them to be able to reach other. gulag:#ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 08:00:27:03:18:ea inet 172.20.6.50 netmask 0xff00 broadcast 172.20.6.255 inet 172.20.6.209 netmask 0xff00 broadcast 172.20.6.255 inet 172.20.6.211 netmask 0xff00 broadcast 172.20.6.255 gulag:#ipfw list 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 1 deny ip from 172.20.6.209 to 172.20.6.211 10001 deny ip from 172.20.6.211 to 172.20.6.209 4 deny ip from 172.20.6.209 to any 65000 allow ip from any to any 65535 deny ip from any to any The two jails [.209 and .211] can still ping each other. Even with rule 4, the .209 jail can ping/ssh to the .211 jail, but of course cannot ping the gateway... If I remove rule '100' from the list, jails are no longer able to ping each other - Although the IPs are on em0, why is the rule with lo0 letting them pass? Does lo0 mean ALL ips assigned to server? or does it mean loopback interface: gulag:#ifconfig lo0 lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 ]Peter[ ___ 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"
