NAT stopped working under Fedora 8

[tbroberg]

On my AMD64 Fedora 8 host system running VirtualBox 1.6.6, *all* of my 3 Fedora and 2 Windows VMs stopped working with NAT.

I suspect this happened when I did that "yum update -y" which presumably updated the kernel.

nslookup fails, ping to a known good address on the internet fails, ping to 10.0.2.3 fails.

Ping to 10.0.2.2 succeeds.

If I do tcpdump on the NAT'ed adapter and ping addresses, for example 10.0.2.3, I can see outbound traffic and ARP replies coming back, but no IP traffic coming back.

Oddly enough, all my complicated networking stuff still works great. I have bridges between the VMs and the host all over the place, and they all work fine.

Given than multiple VMs with disparate OS'es lost it at the same time, I have to think this is an issue on the host side, but I'm not sure where to start looking.

I've tried "/etc/init.d/vboxdrv setup," updating to 2.0.2 and updating guest additions, rebooting VMs, rebooting the host, google, the FAQ, and numerous vile threats involving such things as a pipe wrench and the motherboard.

Has anybody got any ideas more productive than fulfilling my threats?

Is there any way to examine the health of the VirtualBox NAT networking subsystem?

- Tim.[/list][/list]

[Sasquatch]

It appears that a firewall or some sort is blocking your NAT packets. A ping to 10.0.2.3 will always fail, as it's your DNS server that is usually outside the Host. 10.0.2.2 is the only link to an actuall reachable machine, your Host. I can use nslookup just fine from within a VM.

[tbroberg]

I swear I tried this yesterday at least twice, but I managed to get to google.com by filling in http://<ip addr>.

So, it looks like I have DNS issues, which is a pain, but considerably less puzzling.

Actually, I set the DNS back the way it was and the whole problem went away.

Some kind of caching issue?

Anyway it's working now.

Weird.

Thanks for the note, Sasquatch.

- Tim.