Bug 930

Summary: poky-image-lsb-sdk-beagleboard does not get IP over dhcp
Product: [Build System, Metadata & Runtime] BitBake Reporter: Robert Berger <pokylinux>
Component: bitbakeAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, jessica.zhang, poky.bs.watcher, poky.watcher, sgw
Version: 0.9   
Target Milestone: 1.1   
Hardware: Beagleboard   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Robert Berger 2011-03-24 07:48:38 UTC
Using rpm instead of ipk I'm able to build
poky-image-lsb-sdk-beagleboard even with the lastest and greatest from
git (commit aeaa356a5ee77b4596c479451a9db289381a4d16 Sat Mar 19 01:30:12
2011 +0000)

The problem I have now is, that on my beagle-xm networking does not seem
to get an IP address from my dhcp server.

root@beagleboard:~# ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5375 (5.2 KiB)  TX bytes:5375 (5.2 KiB)

usb0      Link encap:Ethernet  HWaddr 06:ba:3b:e0:1f:b2
          BROADCAST MULTICAST  MTU:1492  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


Manually it seems to work:
root@beagleboard:~# ifconfig usb0 192.168.42.67
root@beagleboard:~# ifcusb0: link up, 100Mbps, full-duplex, lpa 0xC5E1

root@beagleboard:~# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:55 errors:0 dropped:0 overruns:0 frame:0
          TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6140 (5.9 KiB)  TX bytes:6140 (5.9 KiB)

usb0      Link encap:Ethernet  HWaddr 06:ba:3b:e0:1f:b2
          inet addr:192.168.42.67  Bcast:192.168.42.255  Mask:255.255.255.0
          inet6 addr: fe80::4ba:3bff:fee0:1fb2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1492  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:5472 (5.3 KiB)

A sato image built from exactly the same sources had dhcp working out of
the box.

/etc/network/interfaces are identical (see below).
... and if you ask my uneducated guess I would say this should not work,
since usb0 is static ?!?!

... but, surprisingly enough it does on sato ...

... and if I make the following change in lsb-sdk it still does not :

iface usb0 inet dhcp

it also does not work if I hardcode the network conf for usb0 in
/etc/network/interfaces

--------------

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wireless interfaces
iface wlan0 inet dhcp
	wireless_mode managed
	wireless_essid any
	wpa-driver wext
	wpa-conf /etc/wpa_supplicant.conf

iface atml0 inet dhcp

# Wired or wireless interfaces
iface eth0 inet dhcp
iface eth1 inet dhcp

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
	address 192.168.7.2
	netmask 255.255.255.0
	network 192.168.7.0
	gateway 192.168.7.1

# Bluetooth networking
iface bnep0 inet dhcp


RP suggests conman might help on sato.
Comment 1 Paul Eggleton 2011-03-28 07:33:31 UTC
AFAIK connman does not pay attention to /etc/network/interfaces; hence it does not matter what is set in there when connman is used. Where connman is not in use /etc/network/interfaces takes precedence.

I'm thinking this is a duplicate of bug #875 (if that bug was expanded to refer to the default ethernet interface rather than specifically eth0).
Comment 2 Paul Eggleton 2011-04-29 11:16:06 UTC
Patch submitted for this one:

https://lists.yoctoproject.org/pipermail/poky/2011-April/005483.html