Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
openwrt-bot opened this issue Nov 3, 2019 · 3 comments
Closed

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

openwrt-bot opened this issue Nov 3, 2019 · 3 comments
Labels
flyspray

Comments

@openwrt-bot
Copy link

bjorns86:

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)

    packages:
    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.
@openwrt-bot
Copy link
Author

jow-:

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.

@openwrt-bot
Copy link
Author

bjorns86:

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
network.wan=interface
network.wan.ifname='eth0.2'
network.wan.proto='dhcp'

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

@openwrt-bot
Copy link
Author

bjorns86:

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

its a issue with Luci.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flyspray
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openwrt-bot