#15391 new defect

TTL Expired in Base Machine if 2 VM's runnig

Reported by:	mad4x4	Owned by:
Component:	network	Version:	VirtualBox 5.0.18
Keywords:	TTL LOOP	Cc:
Guest type:	Windows	Host type:	Windows

Description (last modified by Valery Ushakov)

Been using Virtual box for Years, but I have notice a problem lately ( last week). Using VirtualBox 5.0.18 r106667

Each of my VM's have 2 Interfaces , one set as bridged (IPV4 Static) , one set as NAT (DCHP) . The NAT interface is set as Cable Disconnected to Keep VM from internet unless I specifically need it.

Now down to my problem, my network on my base machine seems to have TTL Expire errors when I ping 8.8.8.8 from base machine while I have 2 VM's running as soon as I pause them or switch them off/suspend them the TTL EXPIRE error disappears. I have tried with and without the network interfaces in the VM enabled. This can be seen by the time the XP Splash screen shows on Second machine rather than once XP is fully running.

Ping to 8.8.8.8 from Base machine as second VM is started

Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 8.8.8.8: bytes=32 time=33ms TTL=58
Reply from 8.8.8.8: bytes=32 time=30ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.

Routing Tables from Base Machine

===========================================================================
Interface List
 28...1a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter
 16...2a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 31...0a 00 27 00 00 1f ......VirtualBox Host-Only Ethernet Adapter
 12...d4 be d9 84 d1 0b ......Realtek PCIe GBE Family Controller
  8...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 21...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
 13...b8 76 3f 20 74 c1 ......Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz)
 23...00 ff 99 5b a6 25 ......TAP-Win32 Adapter V9
 43...00 ff ea 7f 81 0e ......TeamViewer VPN Adapter
  3...b8 76 3f 20 74 c2 ......Bluetooth PAN HelpText
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.176     20
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.172     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     172.16.228.0    255.255.255.0         On-link    172.16.228.176    276
     172.16.228.0    255.255.255.0         On-link    172.16.228.172    281
   172.16.228.172  255.255.255.255         On-link    172.16.228.172    281
   172.16.228.176  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.172    281
     192.168.10.0    255.255.255.0         On-link      192.168.10.1    276
     192.168.10.1  255.255.255.255         On-link      192.168.10.1    276
   192.168.10.255  255.255.255.255         On-link      192.168.10.1    276
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    266
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    266
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    266
    192.168.184.0    255.255.255.0         On-link     192.168.184.1    276
    192.168.184.1  255.255.255.255         On-link     192.168.184.1    276
  192.168.184.255  255.255.255.255         On-link     192.168.184.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.56.1    266
        224.0.0.0        240.0.0.0         On-link    172.16.228.176    276
        224.0.0.0        240.0.0.0         On-link    172.16.228.172    281
        224.0.0.0        240.0.0.0         On-link      192.168.10.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.184.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.56.1    266
  255.255.255.255  255.255.255.255         On-link    172.16.228.176    276
  255.255.255.255  255.255.255.255         On-link    172.16.228.172    281
  255.255.255.255  255.255.255.255         On-link      192.168.10.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.184.1    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 31    266 fe80::/64                On-link
 13    281 fe80::/64                On-link
  8    276 fe80::/64                On-link
 21    276 fe80::/64                On-link
 13    281 fe80::558:9d49:604d:8884/128
                                    On-link
 31    266 fe80::5565:d785:2df6:9cb6/128
                                    On-link
  8    276 fe80::88b5:5871:7b28:d87/128
                                    On-link
 21    276 fe80::c9b3:ca08:7e8b:6e66/128
                                    On-link
  1    306 ff00::/8                 On-link
 31    266 ff00::/8                 On-link
 13    281 ff00::/8                 On-link
  8    276 ff00::/8                 On-link
 21    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

VM Log ATTACHED

Attachments (2)

VM Log.txt (65.1 KB ) - added by mad4x4 9 years ago.: vm LOG
Linx1-2016-05-05-10-48-39.log (107.5 KB ) - added by mad4x4 9 years ago.: Linux on V 5.20 - LOG

Download all attachments as: .zip

Change History (6)

by mad4x4, 9 years ago

Attachment:	VM Log.txt added

vm LOG

by mad4x4, 9 years ago

Attachment:	Linx1-2016-05-05-10-48-39.log added

Linux on V 5.20 - LOG

comment:1 by mad4x4, 9 years ago

More pronounced with Version 5.20..... Can get it to fail with 1 VM machine. Set up a new VM with Damn Small Linux and set up 2 networks 1= NAT 2=Bridged to LAN.... Started machine and had a ping 8.8.8.8 window on base machine as soon as started the TTL Fail appeared on base machine - see second LOG

Last edited 9 years ago by mad4x4 (previous) (diff)

comment:2 by Valery Ushakov, 9 years ago

Description:	modified (diff)
Summary:	TTL Expiry in Base Machine iF 2 VM's runnig → TTL Expired in Base Machine if 2 VM's runnig

comment:3 by Valery Ushakov, 9 years ago

Please, can you do a packet capture of this on the host?

comment:4 by Valery Ushakov, 9 years ago

Description:	modified (diff)

Note: See TracTickets for help on using tickets.

Download in other formats: