> On 28. Oct 2020, at 18:10, D'Arcy Cain wrote:
>
> On 10/28/20 10:27 AM, Michael Gmelin wrote:
>> Can you (afford to) reboot the machine reliably? If so, schedule a reboot
>> using "shutdown -r +10" and then bring down the the interface to see if it
>> makes a difference.
>
> Nope. No dif
On 10/28/20 10:27 AM, Michael Gmelin wrote:
Can you (afford to) reboot the machine reliably? If so, schedule a reboot using
"shutdown -r +10" and then bring down the the interface to see if it makes a
difference.
Nope. No difference.
--
D'Arcy J.M. Cain | Democracy is three wolves
> On 28. Oct 2020, at 12:32, D'Arcy Cain wrote:
>
> On 10/27/20 2:58 PM, Michael Gmelin wrote:
>
> I hope you don't mind but I reverted this conversation back to the list in
> case it gives someone else any ideas.
>
>> Hi,
>> I tried to reproduce the problem on my home network, but things j
On 10/27/20 2:58 PM, Michael Gmelin wrote:
I hope you don't mind but I reverted this conversation back to the list in
case it gives someone else any ideas.
Hi,
I tried to reproduce the problem on my home network, but things just
work as expected.
I could run VMs with IPs off the local netwo
I have been trying to solve this problem for a week now. I have been
emailing the virtualization list (Re: When is a switch not a switch?)
because it had to do with vm-bhyve but now I am wondering if it is something
else. Maybe some of the network experts here can help.
Basically I have the
