https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264865
mario felicioni changed:
What|Removed |Added
CC||marietto2...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263046
--- Comment #1 from Kurt Jaeger ---
I found drivers here:
https://www.broadcom.com/products/ethernet-connectivity/network-adapters/p425g
testbuilding on 13.1 right now.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263046
--- Comment #2 from Kurt Jaeger ---
After I disabled -Werror, it builds, but:
link_elf_obj: symbol if_multiaddr_count undefined
Building out from the CURRENT tree does not find that function 8-(
--
You are receiving this mail because:
Y
Hi!
For more details, see:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263046
Problem: Getting a BCM57504 card to work on FreeBSD
Current state of affairs:
There's a driver from Broadcom:
https://www.broadcom.com/products/ethernet-connectivity/network-adapters/p425g
as version 222.0.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #73 from Christos Chatzaras ---
I see that iron.udjin loader.conf has wireguard enabled.
I use wireguard too.
Is this possible related to wireguard?
--
You are receiving this mail because:
You are the assignee for the bug.
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #74 from Richard Scheffenegger ---
The offending TCP sessions we've seen so far all seem to be regular https
sessions. For (yet unknown) reasons, rarely the FIN bit seems to get accounted
more than once - up to 6 times, from one
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #75 from iron.ud...@gmail.com ---
(In reply to Christos Chatzaras from comment #73)
I don't think that it's somehow related to wireguard because I had similar
panics on the server which is doesn't have wireguard installed/used.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #76 from Michael Tuexen ---
(In reply to iron.udjin from comment #75)
Thanks for the data pointer. I guess, whatever modifications a tunnel or link
layer does unintentionally would look like packet corruption to TCP and should
b
