On 2026-04-10 20:51, Mike Larkin wrote:
On Wed, Apr 01, 2026 at 04:08:14PM -0600, Luke Call wrote:
I created a debian VM and vmctl starts it successfully (thanks to
earlier threads on that topic!). At first, the network worked fine.
Then I don't know what I did, but after restarting the VM,
the network would not work (can't ping anything from inside it,
nmap can't see the VM at all). Even recreating
the VM image and starting that--no network. I noticed an error
on the host, in /var/log/messages from around the time I started
the failing VM:
/bsd: arp: attempt to add entry for 100.64.1.3 on tap0 by [ipv6
address] on tap1
...repeated many times. But I don't know my way around arp or tap
interfaces.
Rebooting fixed it. But for next time, is there a better way for me to
address this?
Thanks much,
Luke Call
trace down where the packets get lost:
1. tcpdump -i vio0 inside the vm
2. tcpdump -i tapX on the host
3. tcpdump -i trunk/bridge/veb on the host (if using that)
4. tcpdump -i egress interface on the host
... etc ...
It is the PF. Try with `pfctl -f /etc/pf.conf` and it will work again.
When you restart the VM the tapX device get deleted/destroyed and all pf
rules (related to it) are gone too.
