[Bug 259645] crash in_cksumdata (sys/amd64/amd64/in_cksum.c:113) via in4_cksum (sys/netpfil/pf/in4_cksum.c:117) after FreeBSD 13.0 p5 update

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645 --- Comment #25 from Arnaud de Prelle --- Created attachment 229952 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229952&action=edit apn dmesg.boot -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 259645] crash in_cksumdata (sys/amd64/amd64/in_cksum.c:113) via in4_cksum (sys/netpfil/pf/in4_cksum.c:117) after FreeBSD 13.0 p5 update

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645 --- Comment #24 from Arnaud de Prelle --- Created attachment 229951 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229951&action=edit apn pciconf -lv -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 259645] crash in_cksumdata (sys/amd64/amd64/in_cksum.c:113) via in4_cksum (sys/netpfil/pf/in4_cksum.c:117) after FreeBSD 13.0 p5 update

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645 --- Comment #23 from Arnaud de Prelle --- Created attachment 229950 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229950&action=edit apn PF Firewall configuration -- You are receiving this mail because: You are on the CC list

[Bug 259645] crash in_cksumdata (sys/amd64/amd64/in_cksum.c:113) via in4_cksum (sys/netpfil/pf/in4_cksum.c:117) after FreeBSD 13.0 p5 update

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645 --- Comment #22 from Arnaud de Prelle --- Hi, I patched yesterday at around 8AM CET from 13.0-p4 to 13.0-p5 and experienced two crashes in a a few minutes at around 11PM CET. I guess it's related to this bug and will apply the workaround.

[Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260 --- Comment #1 from Marek Zarychta --- Last time tested on 13.0-STABLE stable/13-n248421-3b936a8c889 where the issue persists. It is also worth mentioning that turning off vlanmtu vlanhwtag vlanhwfilter vlanhwtso vlanhwcsum on parents doesn

[Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260 Marek Zarychta changed: What|Removed |Added CC||n...@freebsd.org Keywor

[Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221122 Mason Loring Bliss changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You a

[Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221122 --- Comment #19 from Mason Loring Bliss --- I saw this issue on FreeBSD 13.0-RELEASE, and following kbowling's recommendation, also tried the most recent 13-STABLE images. This latter is where I've gathered data. Same issue: Add an epair h

[Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221122 Mason Loring Bliss changed: What|Removed |Added Resolution|Not A Bug |--- CC|

Re: Weirdness with same-host IPv6 packets

2021-12-06 Thread Dustin Marquess
So tracing the traffic using tcpdump, the UDP packet itself is being sent, it's just not making it to the process for some reason: 19:10:23.502313 IP6 (flowlabel 0xc0e2c, hlim 64, next-header UDP (17) payload length: 16) 2001:470:bc52:4::101.56339 > 2001:470:bc52:4::101.: [bad udp cksum 0xc3b2

Re: if_vlan allow to set incorrect mtu

2021-12-06 Thread Marek Zarychta
W dniu 8.11.2021 o 08:13, Zhenlei Huang pisze: On Nov 7, 2021, at 3:51 PM, Rozhuk Ivan wrote: Hi! Why if_vlan allow to set same MTU size or bigger as on parrent nic? Setup: - workstation with MTU 9000 and IPv4 on h/w nic - server with MTU 9000 on h/w nic and IPv4 on vlan nic with MTU 900

[Bug 240818] igb(4) vlanhwfilter feature generate link UP/DOWN for each new vlan created

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818 --- Comment #26 from Marek Zarychta --- Probably fixed in https://cgit.freebsd.org/src/commit/?id=9c6432dc4bb936f0842d766d8b3b19dfcde15da2 See bug 230996. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable

2021-12-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230996 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu.

Re: Porting OpenBSD MPLS to FreeBSD

2021-12-06 Thread Lev Serebryakov
On 19.11.2021 23:16, Lutz Donnerhacke wrote: * Is porting OpenBSD MPLS to FreeBSD feasible, or are we better off doing a from-scratch implementation based on netgraph? I'd prefer a netgraph approach, if possible. It helps to concentrate on the important things. Isn't netgraph is very PPS-

Re: why multi-hop icmp redirects to 0.0.0.0 on 13.0 ?

2021-12-06 Thread Rodney W. Grimes
> On Sun, 5 Dec 2021, Lutz Donnerhacke wrote: > > > On Sun, Dec 05, 2021 at 08:20:08PM +0200, John Hay wrote: > >> Something I have observed is that if you use FreeBSD 13 as a router with 2 > >> subnets on the same interface, it will generate redirects when hosts send > >> packets to the other sub

Re: Porting OpenBSD MPLS to FreeBSD

2021-12-06 Thread Rodney W. Grimes
[ Charset UTF-8 unsupported, converting... ] > Hi Alexander, > > On 2021-12-04 10:42, Alexander V. Chernikov wrote: > >> * Is porting OpenBSD MPLS to FreeBSD feasible, or are we better off > >> doing a from-scratch implementation based on netgraph? > > It depends. MPLS implementaiton can be split