Date: Mon, 04 Apr 2022 18:50:59 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 255830] dummynet(4) queues/pipes do not work inside of a VNET jail Message-ID: <bug-255830-29815-Np6MHDzIlV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255830-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-255830-29815@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255830 --- Comment #8 from Joshua Kinard <kumba@gentoo.org> --- (In reply to Kristof Provost from comment #7) FWIW, I've revisited this in 13.1-RC1 on my router and was able to successf= ully put my router configuration into a jail by allowing the jail to have direct access to the WAN and LAN ports (the jail host has six GbE ports total, so = it runs management services on a third port). I was also able to get the separate wireless subnet into the same jail after putting wlan0 into the jail and tweaking hostapd's rc.d script to allow run= ning in a jail. So far, the only issue noticed, which appears to be benign, are these messa= ges in dmesg when the jail is shutdown or restarted: [nhop_ctl] inet.0 nhop_free: failed to unlink nh#3/inet/em0/resolve [nhop_ctl] inet.0 nhop_free: failed to unlink nh#2/inet/em0/<ISP IP address> [nhop_ctl] inet.0 nhop_free: failed to unlink nh#5/inet/em1/resolve [nhop_ctl] inet6.0 nhop_free: failed to unlink nh#5/inet6/em1/resolve If those messages are not an issue, I'd say this bug can be closed. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255830-29815-Np6MHDzIlV>