Created attachment 218028 [details]
12.2-BETA has a new issue with VNET that 12.1-RELEASE didn't have.
Initially when a list of jails are created all can be pinged. However, after the default ARP timeout, the last jail attached to the bridge fails to respond. If the ARP for the last jail is statically set (arp -s) it will again respond to pings. The problem only effects the last jail attached to the bridge regardless of the number of jails or which one is last.
My /etc/jails.conf is attached
*** Bug 249400 has been marked as a duplicate of this bug. ***
12.2-BETA3 does not have the problem.
Closing the bug report as FIXED.
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.
OK, now we have a bug that will not always manifest itself, although the bugs 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.
(From the HOST) Initially when a list of jails are created all can be pinged. 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.
Re-assign to net@ as the chances are much higher that network people can figure out ARP and things than jail people.
With 12.2-RELEASE I can not longer consistently duplicate the problem. While there are still VNET / ARP problems, I not longer believe that this bug report will be helpful in diagnosing the problem.