[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #22 from Gregory Neil Shapiro --- Bug 278422 filed for dxr crash -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #21 from Gregory Neil Shapiro --- (In reply to Zhenlei Huang from comment #19) That is another good solution that I can appy generically to all tunnels that might end up giving a BGP route to the tunnel endpoint. Thanks! --

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #20 from Gregory Neil Shapiro --- Funny thing happened when I put the config in place to work around the loop The sytem crashed with a panic in the dxr routing algorithm Marek recommended in comment 2. I'll file a new bug for

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #19 from Zhenlei Huang --- @Gregory bird2 learned more precise route for remote end of the vxlan tunnel from the vxlan interface. When that route was installed into kernel FIB then it ended up recursive encapsulation. Unfortunat

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #18 from Gregory Neil Shapiro --- Verified: #23 ip_output (m=m@entry=0xf80007e3e000, opt=opt@entry=0x0, ro=, flags=flags@entry=0, imo=0x0, inp=inp@entry=0x0) at ./../../netinet/ip_output.c:699 699 switch

Re: ixl(4) bhyve(8) SR-IOV with Transparent VLAN associated w/ VF's

2024-04-17 Thread Lexi Winter
Paul Procacci: > I'm assigning VF's to bhyve with pci passthru. [...] > Given this, I figured the best option would be to set the VLAN on the VF on > the host prior to handing it off to the bhyve instance effectively enabling > transparent vlans. [...] > Has anyone done this? Does anyone have any

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 Zhenlei Huang changed: What|Removed |Added CC||z...@freebsd.org --- Comment #17 f

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 Mark Johnston changed: What|Removed |Added Status|New |Open --- Comment #16 from Mark Joh

ixl(4) bhyve(8) SR-IOV with Transparent VLAN associated w/ VF's

2024-04-17 Thread Paul Procacci
Hey all, Strange one here. Not much on the internet that I could find. I'm assigning VF's to bhyve with pci passthru. Doing this allows the bhyve instance maintainer to set their own vlan and I'd like that not to be the case for various reasons. One being I don't need/want their traffic to pote

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 Gregory Neil Shapiro changed: What|Removed |Added Attachment #250014|0 |1 is obsolete|

[Bug 278394] Reproducible kernel panic related to IPv4 routes populated by bird2 (BGP)

2024-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278394 --- Comment #14 from Mark Johnston --- (In reply to Gregory Neil Shapiro from comment #10) So, if you're building a kernel from releng/14.0, GENERIC doesn't have debugging options enabled. DEBUG+=-g merely instructs the compiler to include

[iflib] Allow concurrent execution of admin tasks from different interfaces

2024-04-17 Thread Krzysztof Galazka
Hi, In current iflib implementation there is a single task queue group used for all admin tasks, defined with: iflib.c:560 TASKQGROUP_DEFINE(if_config_tqg, 1, 1); This does not allow for concurrent processing of tasks. In systems with a large number of interfaces this may cause one long running