Ticket #12225 (closed defect: fixed)
NAT cable_connected ignored when router goes down => Fixed in SVN
|Reported by:||socratis||Owned by:|
|Version:||VirtualBox 4.3.0||Keywords:||NAT, cable connected|
|Host type:||Mac OS X|
My setup is as follows:
Guest (any) w/ 4 net adapters (Host, Internal, Bridged, NAT) --> Host OSX 10.6.8 (10.0.0.101) --> TimeCapsule (10.0.0.1, 192.168.2.2) --> ISP_Device (192.168.2.1)
- Host: (Cable connected) 192.168.100.x
- Internal: (Cable connected) 192.168.50.x
- Bridged: (Cable DISconnected)
- NAT: (Cable DISconnected) (set to get 10.x.x.x address once connected, usually 10.0.5.15)
Here's the deal; after upgrading to 4.3.x, if my ISP_Device goes down (power, ADSL connection) and comes up again, NAT connects to the internet! The preferences still say "Cable not connected" but I do have an IP address and can ping/connect at will to anything on the Internet. Checking/unchecking the "Cable connected" checkbox does disconnect NAT.
This could very well be a major security hole, that is why I put the priority to Critical.
- Summary changed from NAT cable_connected ignored when router goes down to NAT cable_connected ignored when router goes down => Fixed in SVN