Opened 16 years ago
Closed 14 years ago
#4567 closed defect (fixed)
Internal network stops working after suspend
| Reported by: | Robin Green | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 3.0.2 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Mac OS X |
Description
This is with OSE 3.0.2 with two Linux guests on an internal network. After suspending the host, the guests also suspend as expected, and automatically resume, and when I try to use the internal network, it doesn't work. Cannot connect to the other machine and pings fail. Bringing down and up the interface on both machines does not change anything.
Each guest has 2 network cards; all 4 are the same type. On one of the guests, the internal networking is attached to the first network card; on the other, it's attached to the second. The other network cards are NAT. The NAT network cards are both configured to do DNS masquerading.
Attachments (2)
Change History (12)
by , 16 years ago
comment:1 by , 16 years ago
It turns out it doesn't require a suspend - it seems to be caused by the network being left almost idle for a period of time (although there may be some operating system packets transmitted, so I don't know if it's completely idle).
comment:3 by , 16 years ago
I see the same problem with suspend/resume on 3.0.6. Host: WinXP; guest: Fedora Core 10 with e1000 NIC.
comment:4 by , 16 years ago
I am no longer experiencing this bug - I think due to upgrading my guests.
comment:6 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if this problem persists, 3.0.10 is about to be released.
comment:7 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
i using 3.2.8 OSE and fail again
comment:8 by , 14 years ago
| Component: | network → network/hostif |
|---|
comment:9 by , 14 years ago
Can anybody confirm that the problem is present in 4.0.4 and provide VBox.log?
Log file for first machine