This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Atheros 8031 Cannot get DHCP Lease

Other Parts Discussed in Thread: AM3358

Hi all,

We have an AM3358 board with u-boot version 2013.10  and linux kernel version 3.12.10 and atheros 8031 on eth0. On some of our routers, our board is able to get an IP address successully, but on some router (e.g. Orange Livebox Pro V3), the board is unable to get a DHCP lease. When we set the board's IP to static, we it appears the network is working since we can access the device on the network. How do I start troubleshooting this?

Regards,

Marlon

  • After running tcpdump, it seems we are not getting DHCP offers:

    # udhcpc -i eth0 -b && tcpdump -v -i eth0
    udhcpc (v1.20.2) started
    Sending discover...
    Sending discover...
    Sending discover...
    No lease, forking to background
    [ 473.930892] device eth0 entered promiscuous mode
    tcpdump: WARNING: eth0: no IPv4 address assigned
    tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
    04:38:59.403093 IP (tos 0xb8, ttl 64, id 47737, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:04.412771 IP (tos 0xb8, ttl 64, id 47738, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:09.422474 IP (tos 0xb8, ttl 64, id 47739, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:09.552453 IP (tos 0x0, ttl 4, id 0, offset 0, flags [DF], proto UDP (17), length 330)
    192.168.1.1.1900 > 239.255.255.250.1900: UDP, length 302
    04:39:09.553214 IP (tos 0x0, ttl 4, id 0, offset 0, flags [DF], proto UDP (17), length 321)
    192.168.1.1.1900 > 239.255.255.250.1900: UDP, length 293
    04:39:09.553949 IP (tos 0x0, ttl 4, id 0, offset 0, flags [DF], proto UDP (17), length 373)
    192.168.1.1.1900 > 239.255.255.250.1900: UDP, length 345
    04:39:09.554683 IP (tos 0x0, ttl 4, id 0, offset 0, flags [DF], proto UDP (17), length 385)
    192.168.1.1.1900 > 239.255.255.250.1900: UDP, length 357
    04:39:09.555415 IP (tos 0x0, ttl 4, id 0, offset 0, flags [DF], proto UDP (17), length 387)
    192.168.1.1.1900 > 239.255.255.250.1900: UDP, length 359
    04:39:14.432160 IP (tos 0xb8, ttl 64, id 47740, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:16.987011 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0xdd0e3c4a, secs 29, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:19.441910 IP (tos 0xb8, ttl 64, id 47741, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:19.991414 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0xdd0e3c4a, secs 32, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:22.995707 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0xdd0e3c4a, secs 35, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:24.451551 IP (tos 0xb8, ttl 64, id 47742, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:29.461329 IP (tos 0xb8, ttl 64, id 47743, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:34.470924 IP (tos 0xb8, ttl 64, id 47744, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:39.480673 IP (tos 0xb8, ttl 64, id 47745, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:44.480396 IP (tos 0xb8, ttl 64, id 47746, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:46.072232 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0x7149a936, secs 59, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:49.076533 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0x7149a936, secs 62, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:49.490087 IP (tos 0xb8, ttl 64, id 47747, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    04:39:52.080805 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d0:ff:50:54:06:b1 (oui Unknown), length 280, xid 0x7149a936, secs 65, Flags [none]
    Client-Ethernet-Address d0:ff:50:54:06:b1 (oui Unknown)
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Client-ID Option 61, length 7: ether d0:ff:50:54:06:b1
    MSZ Option 57, length 2: 576
    Parameter-Request Option 55, length 7:
    Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
    Domain-Name, BR, NTP
    Vendor-Class Option 60, length 12: "udhcp 1.20.2"
    04:39:54.499828 IP (tos 0xb8, ttl 64, id 47748, offset 0, flags [DF], proto UDP (17), length 86)
    192.168.1.1.9246 > 192.168.1.255.9246: UDP, length 58
    ^C
    23 packets captured
    23 packets received by filter
    0 packets dropped[ 532.259459] device eth0 left promiscuous mode
    by kernel
  • A quick suggestion is that I don't see any phy messages being displayed as the link comes up. The link must be up since you are receiving messages on the ethernet port. Are the phy addresses correct? If the cpsw driver does not think the phy is up then the packets may not be sent.
  • Hi Schuyler,

    We've connected a laptop to the router with a packet sniffer (wireshark) and we were able to see the packets from the laptop, which must mean that the packets have been sent. Am I right? So it seems that the router is not replying?

    Regards,
    Marlon