On VirtualBox_4.3.20_2 hosted on FreeBSD_11-Current_amd64, I have
{Debian-Jessie, OpenWRT, WindowsXP} running as guest.
All guests are using Host-Only networking on 192.168.56.0/28, with 192.168.56.1
(IP of vboxnet0) serving DHCP. Host firewall (PF) handles all routing correctly
and guests normally connect outside through subnet gateway (192.168.56.1).
A recent upgrade has broken Host-Only networking for Linux guests. WindowsXP
guests (static or DHCP assigned) connect to outside without problem as long as
Default_Gateway is defined in network config. Linux guests were able to connect
before but no longer. Further, all Linux guests have Static IP and
Default_Gateway defined but;
* "netstat -rn" shows correct gateway
0.0.0.0 / 192.168.56.1 / 0.0.0.0 / etho
192.168.56.0 /.0.0.0.0 / 255.255.255.240 / etho
* At guest startup, tcpdump shows: ARP, Request who-has 192.168.56.1 tell
192.168.56.10, length 46
But fails all ping and traceroute commands to vboxnet0 (192.168.56.1). tcpdump
shows nothing.
* When guest config is modified to request IP from DHCP, guests fail to receive
IP from VirtualBox DHCP. tcpdump shows:
IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
55:44:99:99:66:66 (oui Unknown), length 300
IP 192.168.56.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 548
IP 192.168.56.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 548
* The exception to the above, is if I run WindowsXP guest anytime then try
Linux guests. After WindowsXP guest starts, Linux guests are able to receive IP
from vboxnet DHCP, and (after more poking) able to ping the subnet gateway.
* When set to Bridged, networking on Linux guests works correctly.
I'd rather get some feedback here before posting a PR.
Please no "why r u using host-only" comments.
--
FreeBSD_amd64_11-Current_RadeonKMS
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[email protected]"
