Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 18915

Re: USB Ethernet works! But no IP address via DHCP

$
0
0

Hey Dan,

 

Apologies for resurrecting an answered thread but the behaviour you were seeing originally is exactly what I'm currently seeing with a Yocto 1.6.1 SPI image:

 

If I bring up eth0 on DHCP, eth0 appears to get a lease…

 

root@quark:~# ifup eth0

[  142.497936] eth0: device MAC address 02:00:00:00:00:00

udhcpc (v1.22.1) started

Sending discover...

[  144.500269] libphy: stmmac-1:01 - Link is Up - 100/Full

Sending discover...

Sending select for 192.168.1.15...

Lease of 192.168.1.15 obtained, lease time 86400

 

However, IP address doesn’t show (although there appears to be TX/RX packets):

 

root@quark:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 02:00:00:00:00:00

          UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1

          RX packets:93 errors:0 dropped:0 overruns:0 frame:0

          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:6724 (6.5 KiB)  TX bytes:1710 (1.6 KiB)

          Interrupt:11 Base address:0x8000

 

And I’m unable to ping:

 

root@quark:~# ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1): 56 data bytes

ping: sendto: Network is unreachable

 

If I then assign a static IP address everything works as expected:

 

root@quark:~# ifconfig eth0 192.168.1.15

root@quark:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 02:00:00:00:00:00

          inet addr:192.168.1.15  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1

          RX packets:113 errors:0 dropped:0 overruns:0 frame:0

          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:7924 (7.7 KiB)  TX bytes:1710 (1.6 KiB)

          Interrupt:11 Base address:0x8000

 

root@quark:~# ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: seq=0 ttl=64 time=3.822 ms

64 bytes from 192.168.1.1: seq=1 ttl=64 time=2.092 ms

 

Connman is not included as part of this SPI image - could something else be preventing the address being bound to eth0?  No other modules other than stmmac loaded.

 

Any suggestions welcome!


Viewing all articles
Browse latest Browse all 18915

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>