Re: [Qemu-discuss] Coldfire 5282 Support

[Thomas Huth]

On 03.10.2017 15:48, William Mahoney wrote:
> I also get everything from DHCP and I am correctly set as the .15 address, 
> etc. 
> 
> eth0      Link encap:Ethernet  HWaddr 52:54:00:12:34:56  
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:4 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:1314 (1.2 KiB)  TX bytes:1296 (1.2 KiB)
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> But:
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         10.0.2.2        255.255.255.255 UGH   0      0        0 eth0
> 10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
> 
> So I have to manually add a route to even get packets handed to the driver. 
> Then they go over to the host for ARP:
> 
> # route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         10.0.2.2        255.255.255.255 UGH   0      0        0 eth0
> 10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
> # route add -net 192.168.5.0 netmask 255.255.255.0 dev eth0
> # route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         10.0.2.2        255.255.255.255 UGH   0      0        0 eth0
> 192.168.5.0     *               255.255.255.0   U     0      0        0 eth0
> 10.0.2.0        *               255.255.255.0   U     0      0        0 eth0
> # nc 192.168.5.142 -p 6000
[...]
> nc: cannot connect to remote host (192.168.5.142): No route to host
> # 
> 
> On the PCAP it is: … Well shoot, Wireshark won’t let me cut/paste. But the 
> ARP is correct but the host is not answering it.

Not sure, but it might be normal that the host is not answering here.
The "user" networking is using NAT, so the host OS might think that it
is talking to itself here and thus ARP is not needed. You might want to
try "tap" networking instead. Or maybe try to connect to another host
from within the guest first (for example "nc www.google.com 80" ... and
then type "GET / HTTP/1.0").

Just another idea: Maybe there is a firewall running on the host that is
preventing the access?

 Thomas