Opened 9 years ago
Last modified 9 years ago
#14389 closed defect
NAT taking 100% (single thread) CPU — at Version 3
| Reported by: | mightyiam | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 5.0.0 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description (last modified by )
Following up from this thread.
let's see how much of the questions there, I can answer.
Attached are the port forward rules as a screenshot.
ip r on the host should give the routing, right?
default via 192.168.0.1 dev eth0 proto static metric 100 10.10.10.0/24 dev vboxnet1 proto kernel scope link metric 100 192.168.0.0/24 dev eth0 proto kernel scope link metric 100
and ip r on the guest should give the routing on the guest:
default via 10.0.2.2 dev eth0 metric 100 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 10.10.10.0/24 dev eth1 proto kernel scope link src 10.10.10.10
Does this answer your questions?
Change History (4)
by , 9 years ago
| Attachment: | Screenshot_2015-08-04_22-17-12.png added |
|---|
comment:1 by , 9 years ago
| Component: | other → network/NAT |
|---|
comment:2 by , 9 years ago
Please, can you provide guest-side packet captures for both NAT and host-only interfaces, taken when the VM exhibits the problem.
comment:3 by , 9 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.


NAT port forwarding