Found a strange error, costing me some time and nerves. Was able to finally solve it but thought posting it here would be a good idea, since there isn´t really information on this anywhere else on the net. So for the benefit of afterworld:
After enabling VLAN on my FreeBSD 13 hosts ix0 interface, my LAN interface is now on ix0.10, which I adjusted in the .vbox-File of my VirtualBox guest as well to ix0.10 (Guest is FBSD 13 also, but should be independent of the guest OS). As a consequence, the guest interface (em0 in this case) didn´t get connections any more, despite showing as active in the guest OS. Pakets just dropped, was not able to traceroute or anything.
After fiddling around with tagging the packets on the guest and replacing the guest adapter by AM Net III and virtio, I found an historic thread, indicating that the Virtualbox driver had problems with dots (".") in interface name some 10 years ago and the guy reporting it complained, that it was not fixed. Which seems to be true still today.
So I gave it a try and renamed my LAN interface to something without dots
and suddenly, everything worked as it should.
To persist, I added "name h2ksux" to my interface declaration in rc.conf:
And there you go...
Greetings from Hell
Betzi
After enabling VLAN on my FreeBSD 13 hosts ix0 interface, my LAN interface is now on ix0.10, which I adjusted in the .vbox-File of my VirtualBox guest as well to ix0.10 (Guest is FBSD 13 also, but should be independent of the guest OS). As a consequence, the guest interface (em0 in this case) didn´t get connections any more, despite showing as active in the guest OS. Pakets just dropped, was not able to traceroute or anything.
After fiddling around with tagging the packets on the guest and replacing the guest adapter by AM Net III and virtio, I found an historic thread, indicating that the Virtualbox driver had problems with dots (".") in interface name some 10 years ago and the guy reporting it complained, that it was not fixed. Which seems to be true still today.
So I gave it a try and renamed my LAN interface to something without dots
ifconfig ix0.10 name h2ksuxand suddenly, everything worked as it should.
To persist, I added "name h2ksux" to my interface declaration in rc.conf:
ifconfig_ix0_10="inet //--// name h2ksux" And there you go...
Greetings from Hell
Betzi