suddenly cannot ping router on bridged network

[rainbow3]

All was working well connecting from linux guest via windows 10 host on bridged network. Then PC crashed.

Now I can connect fine with NAT connection. However when I switch to bridged connection I ping the router and get no response and and I cannot load a web page.

It says connected. ifconfig shows correct IP address. route shows the correct router address. arp -a shows the router and all other machines on the local network. I can ping all those machines and get a response.

However when I ping the router no response.

Have tried rebooting the router and host; and reinstalled latest virtualbox.

[rainbow3]

Found a solution.

I pinged from the router to the guest machine. Then it worked fine.

If anyone can explain this please do.

[rainbow3]

but now it has stopped again and that trick did not work.

[rainbow3]

I had my router set to allocate 192.168.0.16 to the vbox machine based on the mac address. If I turn this off so it just allocates the next available IP on the lan then it works fine in bridged mode.

So now I have a workaround but it is painful because I am running a server that I want to access from the internet. So each time I start the machine I have to find the IP address and configure the router to direct incoming traffic to it.

I don't understand what is going wrong here. Surely when the router/DHCP server issues a new IP address it should not make any difference whether it is random or static? Yet apparently it does.

[socratis]

How about assigning a static IP to your guest and forget all about changing your router configuration?