OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Critical
  • Priority Very Low
  • Reported Version openwrt-18.06
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Björn Strömberg - 03.11.2019
Last edited by Petr Štetiar - 14.11.2019

FS#2576 - Archer C7 v2 - after flashing 18.06.4 wan dhcp works until reboot or reload interface

Supply the following if possible:
- Device problem occurs on

 Model	TP-Link Archer C7 v2 (EU)

- Software versions of OpenWrt/LEDE release, packages, etc.

 Firmware Version	OpenWrt 18.06.4 r7808-ef686b7292 / LuCI openwrt-18.06 branch (git-19.170.32094-4d6d8bc)
 vanilla - nothing added or removed. there are some updates but they do not change anything in this issue.

- Steps to reproduce

  • flash 18.06.4 with default configuration
  • on firstboot wan dhcp got its IP and everything is all fine.
  • restart router and dhcp does not get IP. or restart wan interface and dhcp does not get a IP.
  • syslog gets blasted with client id error due to string instead of hex-string (’root’) i change it to ‘AE’ and error goes away.
  • no matter what you try after fixing the client id error,

no log output saying anything is wrong ether, not in syslog, nor in dmesg.

    is there anyway to get more info without actually running a wireshark capture on wan?

- some notes:
in syslog there is a error related to the dhcp client id (defaults to ‘root’ string) that it wants a hex string, so i changed this to ‘AE’ just a hex pair the syslog error goes away but i still do not get a IP. how long should a client id be? can it be empty?

i’ve run firstboot && reboot now to test things so many times today and this happens everytime. i think i’ve reset back to first boot like 10 times today.. same issue every time, so its not a one time bug it happens every time. (and not happen on 18.06.2 have not tried 18.06.3)

now its back to work week so can continue looking at this next week.

Closed by  Petr Štetiar
14.11.2019 18:31
Reason for closing:  Different project
Additional comments about closing:  

LuCI issue.

Jo-Philipp Wich commented on 03.11.2019 21:12

Its a browser autocomplete bug. For whatever reasons, browsers treat the "clientid" input as username field and autofill "root" in there, when you then save your wan interface settings, the malformed string is written to the config.

Björn Strömberg commented on 04.11.2019 06:38

so if i remove the uci 'network.wan.clientid' key from config, a restart/reload should work? right now i checked on my vanilla firstboot without messing with the wan interface.

it only contains


so it sounds likely the clientid config might be the culprit. so issue is really in Luci if this is true.

Björn Strömberg commented on 12.11.2019 11:30

reboots work as they should when client id is not set, so this issue can be closed.

its a issue with Luci.


Available keyboard shortcuts


Task Details

Task Editing