NatNetwork drops connectivity

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
ChrisLaw
Posts: 4
Joined: 21. Sep 2016, 18:24

NatNetwork drops connectivity

Post by ChrisLaw »

Hello,
I'm after some help with an odd problem I'm seeing on OSX and my natnetworks.

I'm currently using VirtualBox Version 5.0.18 r106667. The host OS is 10.10.5 (14F1909). I have 7 VM's defined, with a variety of OS's on them - but all linux, 64-bit across the board.
Networking, I have a mix of setups - but the issue I'm seeing is with natnetworks. I have 2 defined - one called DefaultNat and the other called StoreNat.

Attached to the DefaultNat I have a single VM, running ubuntu 14.04 - that setup appears fine.

Attached to the StoreNat I have 2 VM's - one RHEL 7.1 client, one RHEL7.1 server. I don't have guest additions in either of them. I portforward port 22 from both of them to ports on my Mac so that I can ssh into them. This setup worked well until just over a month ago. Since then the StoreNat natnetwork seems to just stop working after about 15 minutes or so. Any existing ssh connections are ok, but I am unable to create any new connections, nor can I connect outbound from the clients. There's no errors in the nat log, or the natnet log. I have got a workaround whereby I issue

Code: Select all

VBoxManage natnetwork stop --netname StoreNat && VBoxManage natnetwork start --netname StoreNat
whenever I need to use them. This buys me about 15 minutes each time!

I did find a ticket that talked about putting debug options on for the Natnet -

Code: Select all

export VBOXNET_StoreNat_RELEASE_LOG="+nat_service.e.l.l2.l3.f -nat_service.restrict"; export VBOXNET_StoreNat_RELEASE_LOG_FLAGS="thread timeprog";  VirtualBox & 
which does indeed give more verbosity, but I couldn't find help on what the flags meant, or what other flags were available.

I'm pretty much asking if anyone has seen this before, or what I can do to debug it more - I'm not an OSX man, I'm a linux user but it's what I get from work. I tried the strace equivalent truss but couldn't see anything useful from that either. I've not attached VM logs as I don't believe it to be a VM issue (and they don't get updated for hours at a time, when the problem occurs frequently).
Here's the natnet log that also doesn't show anything :-)

Code: Select all

VirtualBox NAT Network 5.0.18 r106667 darwin.amd64 (Apr 18 2016 16:00:39) release log
00:00:00.010723 Log opened 2016-09-21T15:58:26.955103000Z
00:00:00.010724 Build Type: release
00:00:00.010739 OS Product: Darwin
00:00:00.010747 OS Release: 14.5.0
00:00:00.010754 OS Version: Darwin Kernel Version 14.5.0: Thu Jun 16 19:58:21 PDT 2016; root:xnu-2782.50.4~1/RELEASE_X86_64
00:00:00.010887 DMI Product Name: MacBookPro11,4
00:00:00.010965 DMI Product Version: 1.0
00:00:00.010977 Host RAM: 16384MB total, 1955MB available
00:00:00.010982 Executable: /Applications/VirtualBox.app/Contents/MacOS/VBoxNetNAT
00:00:00.010983 Process ID: 17042
00:00:00.010984 Package type: DARWIN_64BITS_GENERIC
00:00:00.018875 SUP: Opened VMMR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0) at 0xffffff81ed3a5020.
00:00:00.022411 netif NT0: mac 52:54:00:12:35:00
00:00:00.022424 netif NT0: inet 10.0.2.1 netmask 255.255.255.0
00:00:00.022590 Loading IPv4 port-forwarding rule "ClientSSH": TCP :2251 -> 10.0.2.51:22
00:00:00.022619 Loading IPv4 port-forwarding rule "StoreSSH": TCP :2210 -> 10.0.2.10:22
00:00:00.022635 Loading IPv4 port-forwarding rule "clientsshagain": TCP :2215 -> 10.0.2.15:22
00:00:00.022649 Loading IPv4 port-forwarding rule "dhcpssh": TCP :2207 -> 10.0.2.7:22
00:00:00.022658 Loading IPv4 port-forwarding rule "server2ssh": TCP :2204 -> 10.0.2.4:22
Thanks in advance for any help,
Chris
Post Reply