qemu No Internet Access In Guest VM

tivolo

tivolo

Hi all,

I have been trying to find a solution to my networking problem since hours, but i am running out of ideas and hope that someone here can help.

To create a VM, i followed the steps in the handbook. The guest system is running, but i am not happy yet with the networking.
After i assigned an ip address to the bridge, i was able to ping the host from the guest, SSH her and vice versa. If i try this for a node on the internet like ping 9.9.9.9, it is unreachable. Firewall is disabled.

My netstat looks not like as if it would restrict any ip packets from leaving the host to the internet (vpn-gr-72).

Destination Gateway Flags Netif Expire
0.0.0.0/1 link#5 US vpn-gr-72
default 192.168.1.1 UGS wlan0
10.2.0.2 link#1 UH lo0
unn-11-111-11-111. 192.168.1.1 UGHS wlan0
localhost link#1 UH lo0
128.0.0.0/1 link#5 US vpn-gr-72
169.254.0.0/16 link#7 U bridge0
169.254.154.15 link#1 UHS lo0
192.168.1.0/24 link#2 U wlan0
192.168.1.250 link#1 UHS lo0

In the attachment i put the scripts i used to initialize the network and start the guest vm.

Thanks for any advices!
 

Attachments

Hi there.
tivolo said:
My netstat looks not like as if it would restrict any ip packets from leaving the host to the internet (vpn-gr-72).
Rich (BB code): 
169.254.0.0/16 link#7 U bridge0
Click to expand...
Isn't the 169.254. address block reserved for "link-local" addresses, "valid only for communications on a local link, i.e., within a subnetwork", from which network packets with a link-local source or destination address must not be forwarded beyond the local link?

Link-local address - Wikipedia

en.wikipedia.org en.wikipedia.org
Link-local addresses are not guaranteed to be unique beyond their network segment. Therefore, routers do not forward packets with link-local source or destination addresses.
Click to expand...

RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses, 2.7. Link-Local Packets Are Not Forwarded
Code: 
...
   An IPv4 packet whose source and/or destination address is in the
   169.254/16 prefix MUST NOT be sent to any router for forwarding, and
   any network device receiving such a packet MUST NOT forward it,
   regardless of the TTL in the IPv4 header.
...
 
You must log in or register to reply here.
Back
Top