VirtualBox

Opened 13 years ago

Last modified 12 years ago

#9371 closed defect

NAT Interface fails — at Version 15

Reported by: david Owned by:
Component: network/NAT Version: VirtualBox 4.1.0
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by Frank Mehnert)

I have searched bug tracker and found a few with similar symptoms, but resolved bug id's. For my situation, something must have changed after 3.16(the latest functioning version). Before I submit a new Bug I figured I would post here

Environment:

  • VirtualBox 4.1.0 r73009 win.x86
  • Host OS Windows 7 Release: 6.1.7600
  • Guest OS Linux 2.6.24

Problem:

  • All traffic from the guest OS(10.0.3.101) to the VirtualBox NAT interface (10.0.3.2) fails after a duration of time.
  • Initially all traffic functions correctly, after approximately 15-20 min the guest OS is unable to contact the VirtualBox NAT interface. No ping to VirtualBox or anything else on the NAT interface of the guest. The guest is configured for two adapters. adapter 1 is a Host only network that continues to function normally when adapter 2 fails.

Attempted Resolutions:

  • I am able to restore traffic while the guest is running by changing the interface type to something other than NAT, and then reverting back to a NAT interface. This only leads to recreating the NAT failure again.
  • Restarting the guest also recreates the failure.
  • I tried changing the adapter driver types with no success.
  • Down grading to VirtualBox 3.1.6 r59338 is the only solution that provides continuous NAT connectivity.

Change History (18)

by david, 13 years ago

Attachment: ZTM2-2011-08-02-13-56-31.log​ added

VBox log

comment:1 by david, 13 years ago

Tried using guest adapter 1 as NAT interface, still recreates the failure.

in reply to:  1 ; comment:2 by vasily Levchenko, 13 years ago

Replying to dnahas:

Tried using guest adapter 1 as NAT interface, still recreates the failure.

In order to reproduce the issue locally, could you please give me a hint how I can provoke the problem::

  1. what guest you had installed?
  2. what is routing table on your guest?
  3. what kind of networking activity are you doing? e.g. wget ​http://10.0.3.2/something_big, can be used to illustrate the problem.
  4. Is it reproducible if network adapter is e1000, or it happens with pcnet only?

comment:3 by david, 13 years ago

  1. Guest OS Linux 2.6.24

2.The default route 10.0.2.2 and the only other entries in the routing table are the local subnets, 10.0.2.0/24 and 10.10.10.0/24 with no gateway.
a.eth0 10.0.2.102/24 – NAT interface
b.eth1 10.10.10.102/24 – Host only adapter

3.I have not found a single specific activity causes the failure. Once the failure occurs all connectivity is lost, and the NAT interface on the guest cannot ping the virtualbox NAT gateway(10.0.2.2)

The guest is a Linux based virtual appliance used for traffic management and monitoring.

  1. I have tried all of the adapter type options available in virtual box with no success. VirtualBox 3.1.6 r59338 is the newest version that functions for more than 15-20 min.

in reply to:  2 comment:4 by david, 13 years ago

Replying to Hachiman: posted below

in reply to:  3 comment:5 by vasily Levchenko, 13 years ago

Replying to dnahas:

  1. Guest OS Linux 2.6.24

Where I can download the installation image?

2.The default route 10.0.2.2 and the only other entries in the routing table are the local subnets, 10.0.2.0/24 and 10.10.10.0/24 with no gateway.
a.eth0 10.0.2.102/24 – NAT interface
b.eth1 10.10.10.102/24 – Host only adapter

Could you please add route and ifconfig output to defect?

3.I have not found a single specific activity causes the failure. Once the failure occurs all connectivity is lost, and the NAT interface on the guest cannot ping the virtualbox NAT gateway(10.0.2.2)

The guest is a Linux based virtual appliance used for traffic management and monitoring.

  1. I have tried all of the adapter type options available in virtual box with no success. VirtualBox 3.1.6 r59338 is the newest version that functions for more than 15-20 min.

Could you please collect network traffic dump from your vm interfaces till outage moment (please see Network_tips for details)?

comment:6 by david, 13 years ago 

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
10.10.10.0      *               255.255.255.0   U     0      0        0 eth1
default         10.0.2.2        0.0.0.0         UG    100    0        0 eth0


eth0      Link encap:Ethernet  HWaddr 08:00:27:9c:9a:dd
          inet addr:10.0.2.102  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe9c:9add/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20578 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21899 errors:476 dropped:0 overruns:0 carrier:12
          collisions:0 txqueuelen:1000
          RX bytes:4000612 (3.8 MB)  TX bytes:2535106 (2.4 MB)
          Interrupt:10 Base address:0xd020

eth1      Link encap:Ethernet  HWaddr 08:00:27:a4:ef:05
          inet addr:10.10.10.102  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fea4:ef05/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27200 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40175 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9375526 (8.9 MB)  TX bytes:8685903 (8.2 MB)
          Interrupt:9 Base address:0xd060

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:66163 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66163 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:19082352 (18.1 MB)  TX bytes:19082352 (18.1 MB)

comment:7 by david, 13 years ago

DestinationGatewayGenmaskFlagsMetricRefUseIface
10.0.2.0*255.255.255.0U000eth0
10.10.10.0*255.255.255.0U000eth1
default10.0.2.20.0.0.0UG10000eth0

by david, 13 years ago

Attachment: file.part01.exe​ added

Network traffic pcac dump part 1

by david, 13 years ago

Attachment: file.part02.rar​ added

Network traffic pcac dump part 2

comment:8 by david, 13 years ago

When the failure occurs, the network trace from vbox stops. A TCP dump on the guest shows some requests, and eventually arp requests for the 10.0.2.2 address The install would require developer access/sign up from the vendor. Would you like a copy of my VM?

14:58:05.361615 IP 10.0.2.102 > 10.0.2.2: ICMP echo request, id 32330, seq 4759, length 64 14:58:05.361654 IP 10.0.2.102 > 74.125.227.19: ICMP echo request, id 32330, seq 4760, length 64 14:58:05.361692 IP 10.0.2.102 > 74.125.227.18: ICMP echo request, id 32330, seq 4761, length 64

comment:9 by vasily Levchenko, 13 years ago

Could you please don't use self-extracted archives and attach or send me by mail raw archive [vasily _dot_ levchenko _at_ oracle _dot_ com]? Regarding the vm, I like to look at dumps first and will continue conversation about vm later then.

comment:10 by david, 13 years ago

pcap sent to requested email address.

in reply to:  10 comment:11 by vasily Levchenko, 13 years ago

Replying to dnahas:

pcap sent to requested email address.

Unfortunately it isn't still clear what is the reason of outage. Recently we have fixed bug affecting NAT networking under some conditions. Could you please try ​this build?

If it doesn't fix issue for you please don't uninstall it, we will continue investigate your case with this revision (I'll send you bits with enabled logging). Please note: that ICMP(ping) isn't reliable on Windows host, because on Windows we don't use socket like in Unix case for ICMP, instead we use ICMP API which isn't reliable itself. Other case of course is if the issue repeatable only with involving of ICMP, we should investigate exactly this case then.

So with this build please check the changes in the behavior, if it still unacceptable please let me know and I will share bits with enabled logging.

comment:12 by david, 13 years ago

Understanding the windows host ICMP reliability, why does the problem not exist with VirtualBox 3.1.6

Installed supplied update and problem still exists, would like to enable logging.

in reply to:  12 comment:13 by vasily Levchenko, 13 years ago

Replying to dnahas:

Installed supplied update and problem still exists, would like to enable logging.

Please do the following:

  1. download ​VBoxDD.dll.
  2. Replace original VBoxDD.dll with downloaded one.
  3. Switch on the tracing for the guest side like you've it before.
  4. Switch on tracing on host side (probably you'll need wireshark installation).
  5. Launch VBox in following manner: 
    # set VBOX_LOG=drv_nat.e.f.l2
# set VBOX_LOG_DEST=file=c:/nat.log
# set VBOX_LOG_FLAGS="thread time"
# VirtualBox --startvm <vm-name>

when you'll get the log and pcap files please send me them via email.

comment:14 by david, 13 years ago

log and pcap files sent via email

comment:15 by Frank Mehnert, 13 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
Contact – Privacy policy – Terms of Use