#181 closed defect (wontfix)
Inability to ping from guest
| Reported by: | markba | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.3.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
In a guest OS, it is not possible to ping to any external IP address (result of ping is a time out). Strange thing is though that network services like Samba and FTP are available and reachable once you know the IP address. Connecting through that address (Windows or Linux, mount) is indeed possible.
Tried all combinations (host/guest) with no success:
- Ubuntu/Ubuntu
- Ubuntu/Windows XP
- Windows XP/Windows XP
- Windows XP/Ubuntu
Guests are connected through NAT.
Utilities like traceroute also don't work. Addresses are resolved through DNS, so the DNS server is reachable, but the pinging it self only shows time outs.
Change History (3)
comment:1 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 16 years ago
Frank, this means that utilities like netselect-apt in debian won't work, as they rely on traceroute to validate the fastest mirror.
Is there any way to kludge together a default response (ie 10ms) for ICMP so that utilities that rely upon it don't fail?
comment:3 by , 16 years ago
Not with the current NAT implementation. If you rely on ICMP, use host interface networking. See the user manual on how to setup this.
This is not really a bug but more an issue or an unimplemented feature. Lack of ICMP support with NAT is described in the UserManual chapter 5.3.2. No fix is planned since ICMP is not important for NAT.