[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #17 from iz-rp...@hs-karlsruhe.de --- With INVARIANTS enabled the same i386 kernel from comment #16 does not panic. So it looks like it is the same cause as mentioned in the bug report in comment #15. Ralf -- You are receiving

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #18 from Hans Petter Selasky --- Created attachment 184049 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184049&action=edit Fix for panic Hi, Can you try the attached patch? -- You are receiving this mail because:

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #19 from Hans Petter Selasky --- https://reviews.freebsd.org/D11475 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #20 from iz-rp...@hs-karlsruhe.de --- r319722 with the patch mentioned in comment #18 does not panic any more. I double checked that INVARIANTS is disabled in my kernel configuration, so your patch fixes the panic. Thank you. Ra

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #21 from oleg.nau...@gmail.com --- It possible that patch is incomplete; please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220452 -- You are receiving this mail because: You are the assignee for the bug.

Re: [Bug 220351] Path MTU discovery works only after resetting an internal interface MTU (mpd5, ng_nat, ipfw)

02.07.2017 23:57, Herbert J. Skuhra wrote: > mpd: [B1] IFACE: Connecting tcpmssfix > > But when I disable IPv6 on my network everything is working... even > without tcpmssfix enabled. > > Instead of enabling ipv6cp in mpd5 I've also tested with an IPv6 tunnel > from HE... same issue. :-( I do n

Re: [Bug 220351] Path MTU discovery works only after resetting an internal interface MTU (mpd5, ng_nat, ipfw)

03.07.2017 3:31, Herbert J. Skuhra wrote: >> Instead of enabling ipv6cp in mpd5 I've also tested with an IPv6 tunnel >> from HE... same issue. :-( > > Hmm, adding "mtu#1440" to /etc/rtadvd.conf apperently fixes these > issues. Makes sense? Perhaps, as temporary workaround. You could fill new IPv

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #22 from commit-h...@freebsd.org --- A commit references this bug: Author: hselasky Date: Tue Jul 4 18:23:18 UTC 2017 New revision: 320652 URL: https://svnweb.freebsd.org/changeset/base/320652 Log: After r319722 two fields w

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 Hans Petter Selasky changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 220358] panic in tcp_lro_flush_all

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 Mark Millard changed: What|Removed |Added CC||mar...@dsl-only.net --- Comment #24

[Bug 220449] NetFlow v9 exports are without MAC addresses (ng_netflow)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220449 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org -- You are

Re: AW: axge0 and AX88179

Yes, I am having exactly the same problem that Shteryana described. I also got messages about wrong ip length when I started dhclient for ue0. If I plug my device into a usb 2.0 port and enable flow control, I get networking speeds that are around 250 Mbit/sec. If flow control is disabled and the d