Date: Tue, 29 Sep 2020 21:50:10 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 249399] The last jail created using VNET has ARP problem Message-ID: <bug-249399-29815-M2D2IeG759@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-249399-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-249399-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=3D249399 fred.ha11@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |Open Resolution|FIXED |--- --- Comment #3 from fred.ha11@yahoo.com --- Re-opening this bug report as it has NOT been fixed in BETA3. I closed this ticket earlier as VNET work properly again on one of my test servers, unfortunately VNET still malfunctions on the second.=20 OK, now we have a bug that will not always manifest itself, although the bu= gs behavior is consistent between reboots and always fails on the same server.= The jail/vnet setup of both servers is similar but the number of running jails varies. I would like to work with someone to fix this problem, but do not know what debug information to provide. Symptoms: ------------------------- (From the HOST) Initially when a list of jails are created all can be pinge= d. However, after the default ARP timeout, the LAST jail attached to the bridge fails to respond. (From another jail attached to the same VNET) All jails including the last = one created are pingable. Everything appears normal. --=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-249399-29815-M2D2IeG759>