Re: [beagleboard] Beaglebone A5 cannot resolve DHCP server

[Jason Kridner]

On Sun, Jun 10, 2012 at 2:22 AM, kislo <dima.ki...@gmail.com> wrote:
> I am trying to connect my Beaglebone A5 to the internet to be able to opkg
> Angstrom packages. As it stands, my ifconfig output when I have ssh'ed to
> 192.168.7.2 is:
>
> root@beaglebone:~# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr D4:94:A1:91:EB:00
>           inet addr:169.254.172.97  Bcast:169.254.255.255  Mask:255.255.0.0
>           inet6 addr: fe80::d694:a1ff:fe91:eb00/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:40 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:8728 (8.5 KiB)  TX bytes:12146 (11.8 KiB)
>           Interrupt:40

Do you know that you have a DHCP server properly configured on your
LAN to which you have connected your BeagleBone?

What is the output of 'udhcpc -i eth0' ?

>
> 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:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:404 (404.0 B)  TX bytes:404 (404.0 B)
>
> usb0      Link encap:Ethernet  HWaddr 5A:A9:F7:05:49:63
>           inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>           inet6 addr: fe80::58a9:f7ff:fe05:4963/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:104 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:14406 (14.0 KiB)  TX bytes:11415 (11.1 KiB)
>
> My local machine runs ubuntu but I recall the 169.254.x.x subnet with mask
> 255.255.0.0 is a Windows indicator of an APIPA failover when the DHCP server
> fails to allocate an IP address. Does anyone know if this is the same in
> Linux? Pinging google (by IP, not by name - see below for missing DNS)
> predictably gives a Destination Host Unreachable error.
>
> Connman ./get-services shows no DNS by the way - not sure if this will
> matter for opkg requests.
> root@beaglebone:/usr/lib/connman/test# ./get-services
> [ /net/connman/service/ethernet_d494a191eb00_cable ]
>     IPv6.Configuration = { Method=auto Privacy=disabled }
>     AutoConnect = false
>     Proxy.Configuration = { }
>     Name = Wired
>     Nameservers = [ ]
>     Provider = { }
>     Favorite = true
>     Domains.Configuration = [ ]
>     State = ready
>     Proxy = { Method=direct }
>     Nameservers.Configuration = [ ]
>     LoginRequired = 0
>     IPv6 = { }
>     Domains = [ ]
>     Ethernet = { Interface=eth0 MTU=1500 Method=auto
> Address=D4:94:A1:91:EB:00 }
>     Security = [ ]
>     IPv4.Configuration = { Method=dhcp }
>     Type = ethernet
>     Immutable = false
>     IPv4 = { Netmask=255.255.0.0 Method=dhcp Address=169.254.172.97 }
>
> So I followed this guide:
> http://www.gigamegablog.com/2012/02/06/beaglebone-linux-101-assigning-a-static-ip-address-with-connman/
> to assign a static IP with the set-ipv4-method script. However, the same
> issue persists after restarting everything, though with the new static
> address I gave in place of my original APIPA-like IP.
>
> Any help would be greatly appreciated.
>
> Dima
>
>
>
> -- To join: http://beagleboard.org/discuss
> To unsubscribe from this group, send email to:
> beagleboard...@googlegroups.com
> Frequently asked questions: http://beagleboard.org/faq

[kislo]

DHCP was not correctly configured, thanks for that.

Pretty embarrassing what the real issue turned out to be so I won't get into it. To salvage some usefulness for this thread let me add that the static IP configuration outlined in the link in my original post worked perfectly.

[Gregg Harrington]

Most often your internet connection will serve as a DHCP server or if you have a wireless router that too could be handing out DHCP. Setting it up on a server for a home env is over kill. 

If you don't have one and are so inclined, you can probably spend about 40 bucks on a pretty basic linksys router for your internet connection. I love mine, basic, but it works great!

On Saturday, June 16, 2012 1:17:35 PM UTC-7, Roberto wrote:

So I have the same exact issue!!!!  I typed the 'udhcpc -i eth0' command as Jason so kindly pointed to and I receive the following:

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

[  600.147060] INFO: task udevd:73 blocked for more than 120 seconds.

[  600.153531] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Sending discover...

Sending discover...

Sending discover...

This is a non-stop cycle... I have experience with Ubuntu web servers before but this is my first ARM/beaglebone.  I'm on angstrom right now (straight out of the box - no modifications made).  So my question is... How do I setup a DHCP server for a LAN???  I assume this is the answer you were alluding to in your last post.

I tried reading this post (http://www.howtoforge.com/dhcp_server_linux_debian_sarge), but I don't have Dabian Sarge... I think that's an OS..., but I have a mac OSX.  Any help would be greatly appreciated.  I'm a super newbie so please excuse my confusion.

Roberto