NAT cable_connected ignored when router goes down => Fixed in SVN

[Socratis]

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.

[Socratis]

Bug still there with 4.3.2...

[Frank Mehnert]

Thank you for the report. The fix for this bug will be available in the next maintenance release. ​Here is a test build containing this fix.

[Socratis]

Confirmed as fixed with build 4.3.3-90530.

[Frank Mehnert]

Thanks for the feedback!

[Frank Mehnert]

Fix is contained in 4.3.4.