Opened 14 years ago
Closed 8 years ago
#6284 closed defect (obsolete)
Openvpn disruption when active VM with bridged network
Reported by: | Giovanni Toraldo (gionn) | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 3.1.4 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Mac OS X |
Description (last modified by )
I have a Mac OSX 10.6.2 as host, and I use a Debian Lenny as guest for development purposes with ethernet bridging.
I often use vpn connections on Mac host, with tunnelblick (http://code.google.com/p/tunnelblick/). For the first time today, I noticed some strange behavior with a new vpn configuration, resulting in very poor nfs performances, going stall completely after few minutes.
Another (nice) problem I get, is with ssh through the same vpn:
scorp@antani-mac:~$ ssh -l libersoft 192.168.1.1 Last login: Wed Feb 24 18:02:36 2010 from vpn.libersoft.bncf.lan libersoft@nfs-server:~$ exit scorp@antani-mac:~$ ssh -l 123456789 192.168.1.1 123456789@192.168.1.1's password:
scorp@antani-mac:~$ ssh -l root 192.168.1.1 Read from socket failed: Operation timed out scorp@antani-mac:~$ ssh -l 1234567 192.168.1.1 Read from socket failed: Operation timed out
With an username > 8 chars, ssh connects almost instantly, with an username <= 8 chars, the session seems to start, but some answer from remote server get lost or my packages never get transmitted (note the retransmissions on the tcpdump for login <= 8 chars).
My dmesg shows (a lot of):
in_delayed_cksum_offset: ip_len 49408 (193) doesn't match actual length 207 in_delayed_cksum_offset: ip_len 49408 (193) doesn't match actual length 207 in_delayed_cksum_offset: ip_len 49408 (193) doesn't match actual length 207
If I shutdown (or even pause) every guest VM using bridged networking, the problem disappears.
The only reason I can find in this particular vpn config, is that it use udp packets (In the past I always used tcp-based ones).
Attachments (3)
Change History (8)
by , 14 years ago
Attachment: | antani-web-2010-02-24-20-53-20.log added |
---|
by , 14 years ago
Attachment: | tcpdump-longlogin.txt added |
---|
Tcpdump of the ssh session that works (username > 8)
by , 14 years ago
Attachment: | tcpdump-shortlogin.txt added |
---|
Tcpdump of the ssh session that *doesn't* works (username <= 8)
comment:1 by , 14 years ago
To jump on the bandwagon, I ran into this problem today while running VirtualBox 3.2 on an OS X 10.6.3 system.
comment:3 by , 13 years ago
I am affected by this as well. VirtualBox 4.0.10, mac os 10.6.8. Guest: Arch Linux
comment:4 by , 12 years ago
Also seeing this issue. Just updated to 4.0.14 this morning, but saw it on 4.0.10 as well. It started occurring a few days ago, using a Linux guest on a Snow Leopard host. The only relevant configuration change I have made recently (that I recall) is that I recently switched the ethernet adapter for my virtual machine from bridging to en1 (Apple Airport) to en0 (1000BaseT).
If I change my virtual machine to NAT, the problem doesn't seem to occur.
comment:5 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
VBox log