Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Not getting a DHCP response from AT&T
See original GitHub issueI’m trying to get this setup finally but it’s just not working for me. It never gets a DHCP address.
EdgeOS: 1.10.9 ONT: eth1 RG: eth2
ubnt@ubnt:/var/log$ sudo python /config/scripts/eap_proxy.py eth1 eth2 --restart-dhcp --ignore-when-wan-up --ignore-logoff --ping-gateway --set-mac --debug
[2019-08-30 12:07:00,901]: starting proxy_loop
[2019-08-30 12:07:17,785]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 15, Request (1) id 5, len 15 [11]
[2019-08-30 12:07:17,788]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 15, Request (1) id 5, len 15 [11] > eth2
[2019-08-30 12:07:17,792]: eth2: sent 64 bytes
[2019-08-30 12:07:17,816]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 22, Response (2) id 5, len 22 [18]
[2019-08-30 12:07:17,821]: eth1.0: setting mac to d4:b2:7a:b0:dd:74
[2019-08-30 12:07:19,413]: eth1.0: no IP address
[2019-08-30 12:07:19,417]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 22, Response (2) id 5, len 22 [18] > eth1
[2019-08-30 12:07:19,421]: eth1: sent 60 bytes
[2019-08-30 12:07:19,425]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 4, Failure (4) id 5, len 4 [0]
[2019-08-30 12:07:19,430]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 4, Failure (4) id 5, len 4 [0] > eth2
[2019-08-30 12:07:19,434]: eth2: sent 64 bytes
[2019-08-30 12:07:19,438]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 15, Request (1) id 6, len 15 [11]
[2019-08-30 12:07:19,442]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 15, Request (1) id 6, len 15 [11] > eth2
[2019-08-30 12:07:19,446]: eth2: sent 64 bytes
[2019-08-30 12:07:19,841]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 22, Response (2) id 6, len 22 [18]
[2019-08-30 12:07:19,847]: eth1.0: no IP address
[2019-08-30 12:07:19,852]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 22, Response (2) id 6, len 22 [18] > eth1
[2019-08-30 12:07:19,856]: eth1: sent 60 bytes
[2019-08-30 12:07:19,870]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 7, len 6 [2]
[2019-08-30 12:07:19,874]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 7, len 6 [2] > eth2
[2019-08-30 12:07:19,879]: eth2: sent 64 bytes
[2019-08-30 12:07:21,112]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 206, Response (2) id 7, len 206 [202]
[2019-08-30 12:07:21,118]: eth1.0: no IP address
[2019-08-30 12:07:21,121]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 206, Response (2) id 7, len 206 [202] > eth1
[2019-08-30 12:07:21,126]: eth1: sent 224 bytes
[2019-08-30 12:07:21,227]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 8, len 1020 [1016]
[2019-08-30 12:07:21,230]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 8, len 1020 [1016] > eth2
[2019-08-30 12:07:21,234]: eth2: sent 1038 bytes
[2019-08-30 12:07:22,147]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 8, len 6 [2]
[2019-08-30 12:07:22,152]: eth1.0: no IP address
[2019-08-30 12:07:22,155]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 8, len 6 [2] > eth1
[2019-08-30 12:07:22,159]: eth1: sent 60 bytes
[2019-08-30 12:07:22,173]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 9, len 1020 [1016]
[2019-08-30 12:07:22,177]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 9, len 1020 [1016] > eth2
[2019-08-30 12:07:22,181]: eth2: sent 1038 bytes
[2019-08-30 12:07:23,171]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 9, len 6 [2]
[2019-08-30 12:07:23,177]: eth1.0: no IP address
[2019-08-30 12:07:23,179]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 9, len 6 [2] > eth1
[2019-08-30 12:07:23,184]: eth1: sent 60 bytes
[2019-08-30 12:07:23,198]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 10, len 1020 [1016]
[2019-08-30 12:07:23,202]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 1020, Request (1) id 10, len 1020 [1016] > eth2
[2019-08-30 12:07:23,206]: eth2: sent 1038 bytes
[2019-08-30 12:07:24,199]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 10, len 6 [2]
[2019-08-30 12:07:24,205]: eth1.0: no IP address
[2019-08-30 12:07:24,208]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 10, len 6 [2] > eth1
[2019-08-30 12:07:24,212]: eth1: sent 60 bytes
[2019-08-30 12:07:24,226]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 707, Request (1) id 11, len 707 [703]
[2019-08-30 12:07:24,230]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 707, Request (1) id 11, len 707 [703] > eth2
[2019-08-30 12:07:24,233]: eth2: sent 725 bytes
[2019-08-30 12:07:25,528]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 1408, Response (2) id 11, len 1408 [1404]
[2019-08-30 12:07:25,533]: eth1.0: no IP address
[2019-08-30 12:07:25,536]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 1408, Response (2) id 11, len 1408 [1404] > eth1
[2019-08-30 12:07:25,540]: eth1: sent 1426 bytes
[2019-08-30 12:07:25,558]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 12, len 6 [2]
[2019-08-30 12:07:25,561]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 12, len 6 [2] > eth2
[2019-08-30 12:07:25,565]: eth2: sent 64 bytes
[2019-08-30 12:07:26,553]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 1404, Response (2) id 12, len 1404 [1400]
[2019-08-30 12:07:26,558]: eth1.0: no IP address
[2019-08-30 12:07:26,561]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 1404, Response (2) id 12, len 1404 [1400] > eth1
[2019-08-30 12:07:26,564]: eth1: sent 1422 bytes
[2019-08-30 12:07:26,582]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 13, len 6 [2]
[2019-08-30 12:07:26,585]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 6, Request (1) id 13, len 6 [2] > eth2
[2019-08-30 12:07:26,589]: eth2: sent 64 bytes
[2019-08-30 12:07:27,589]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 893, Response (2) id 13, len 893 [889]
[2019-08-30 12:07:27,594]: eth1.0: no IP address
[2019-08-30 12:07:27,597]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 893, Response (2) id 13, len 893 [889] > eth1
[2019-08-30 12:07:27,600]: eth1: sent 911 bytes
[2019-08-30 12:07:27,632]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 69, Request (1) id 14, len 69 [65]
[2019-08-30 12:07:27,635]: eth1: 00:90:d0:63:ff:01 > d4:b2:7a:b0:dd:74, EAP packet (0) v1, len 69, Request (1) id 14, len 69 [65] > eth2
[2019-08-30 12:07:27,639]: eth2: sent 87 bytes
[2019-08-30 12:07:28,615]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 14, len 6 [2]
[2019-08-30 12:07:28,620]: eth1.0: no IP address
[2019-08-30 12:07:28,623]: eth2: d4:b2:7a:b0:dd:74 > 01:80:c2:00:00:03, EAP packet (0) v2, len 6, Response (2) id 14, len 6 [2] > eth1
[2019-08-30 12:07:28,627]: eth1: sent 60 bytes
[2019-08-30 12:07:28,651]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 4, Success (3) id 14, len 4 [0]
[2019-08-30 12:07:28,655]: eth1.0: no IP address
[2019-08-30 12:07:28,657]: eth1.0: restarting dhclient
Option new_ip requires an argument
Option old_ip requires an argument
[2019-08-30 12:07:29,334]: eth1: 00:90:d0:63:ff:01 > 01:80:c2:00:00:03, EAP packet (0) v1, len 4, Success (3) id 14, len 4 [0] > eth2
[2019-08-30 12:07:29,338]: eth2: sent 64 bytes
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (4 by maintainers)
Top Results From Across the Web
My router DHCP will not assign IP address | AT&T Community ...
Go to Home Network > Subnets & DHCP. Under "DHCP Server" there is a "DHCP Server Enable" section, with a drop down to...
Read more >DHCP - "reset list" to solve connection issues?
DHCP - "reset list" to solve connection issues? After 3 years of no issues with my ATT router, the last week or so...
Read more >unknown DHCP requests coming from router
I've finally taken the plunge and turned off the DHCP service in the router and activated a local DHCP Server on my linux...
Read more >BGW320-500 DHCP issues - AT&T Community Forums
I miss the time having my Asus router with Harris modem. This AT&T 320-500 reboot several times a day randomly. It is not...
Read more >DPH-154 fails to get DHCP IP from router
I bought the DPH-154 yesterday and got it home, plugged it in and started the configuration, but the status webpage never got past...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Can confirm, the proxy isn’t working with ER X firmware 2.x+.
I have the same issue (no ip error message, mac correctly set), but only on my ER X fw 2.08 - if I switch back to 1.10 it all works.