qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Coldfire 5282 Support


From: William Mahoney
Subject: Re: [Qemu-discuss] Coldfire 5282 Support
Date: Tue, 3 Oct 2017 13:48:38 +0000

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
mcf_fec: do_tx
mcf_fec: tx_bd 47d370a0 flags 9c00 len 42 data 47d42000
mcf_fec: Sending packet
mcf_fec: tx_bd 47d370a8 flags 0000 len 0 data 00000000
mcf_fec: IRQ 0 = 1
mcf_fec: IRQ 1 = 1
mcf_fec: IRQ 0 = 0
mcf_fec: IRQ 1 = 0
mcf_fec: do_tx
mcf_fec: tx_bd 47d370a8 flags 9c00 len 42 data 47d42800
mcf_fec: Sending packet
mcf_fec: tx_bd 47d370b0 flags 0000 len 0 data 00000000
mcf_fec: IRQ 0 = 1
mcf_fec: IRQ 1 = 1
mcf_fec: IRQ 0 = 0
mcf_fec: IRQ 1 = 0
mcf_fec: do_tx
mcf_fec: tx_bd 47d370b0 flags 9c00 len 42 data 47d43000
mcf_fec: Sending packet
mcf_fec: tx_bd 47d370b8 flags 0000 len 0 data 00000000
mcf_fec: IRQ 0 = 1
mcf_fec: IRQ 1 = 1
mcf_fec: IRQ 0 = 0
mcf_fec: IRQ 1 = 0
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.




> On Oct 3, 2017, at 8:40 AM, Thomas Huth <address@hidden> wrote:
> 
> On 03.10.2017 15:21, William Mahoney wrote:
>> Hi Thomas;
>> 
>> I was telling this to Peter as well offline. The initial problem just FYI 
>> was that the routing on the m68k side was nonexistent, so it wasn’t even 
>> sending anything to the net drivers at all. I turned on the debugging in the 
>> net driver and there was no traffic. It looks like there is a gateway set up 
>> in the uClinux but it’s lying.  
>> 
>> Now the hang-up in on my Unbuntu host side. When I do this: 
>> 
>>    ./bin/qemu-system-m68k \
>>      -cpu m5208 \
>>      -M mcf5208evb \
>>      -kernel ./coldfire-test-0.1/vmlinux-2.6.21-uc0 \
>>      -nographic \
>>      -net nic -net user,id=net0 \
>>      -object filter-dump,id=f1,netdev=net0,file=temp_net.pcap
>> 
>> The pcap shows what’s going on. QEMU does an ARP to the host and my host is 
>> … very very quiet. As they say in war movies, "it’s almost TOO quiet!" So I 
>> need to track down why here’s no resolving, then I think I’ll be good.
> 
> If I run that command, the 68k side successfully gets an IP address via
> DHCP. What do you see when you run "ifconfig" at the 68k shell?
> 
> Thomas


reply via email to

[Prev in Thread] Current Thread [Next in Thread]