TCP Unreachable After Update

[the_bear]

I upgraded to 4.3.24 r98716. After upgrading, TCP stopped working, but ICMP continues to work. My guest is Ubuntu with Windows 8 host. I tried turning off the Windows firewall, but that didn't help. Bridge mode works, but I find NAT more convenient. I also get some rpc bind errors during VM boot, but I don't think that is related.

Code: Select all

ping 192.168.1.254 
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_req=1 ttl=63 time=0.889 ms

telnet 192.168.1.254 
Trying 192.168.1.254...
telnet: Unable to connect to remote host: Network is unreachable

ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:b2:74:46  
          inet addr:10.0.3.15  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feb2:7446/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:107 errors:0 dropped:0 overruns:0 frame:0
          TX packets:917 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8318 (8.3 KB)  TX bytes:76854 (76.8 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.0.3.2        0.0.0.0         UG    0      0        0 eth0
default         10.0.3.2        0.0.0.0         UG    100    0        0 eth0
10.0.3.0        *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0

[the_bear]

I found that Qualcomm had not signed the network driver on my host OS. There was a recent change to VirtualBox that rejects connecting to network drivers that are not signed. I updated the network driver of the host machine to a new signed one and now NAT is working again.

[socratis]

Nice finding! But more importantly, thank you for letting us know. This may help users that are facing the problem down the road. Kudos for the report of the problem being your first post and the solution your second!