OpenWrt/LEDE Project

  • Status New
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version openwrt-18.06
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Balazs Vinarz - 11.07.2019
Last edited by Petr Štetiar - 14.07.2019

FS#2381 - Hostname variable is missing for the same machine on different interfaces

Hello,

an older Asus eeePC was just connected to the router using cable. Seconds later the wireless connection became alive as well.
On the DHCP leases I can see the 1 sec older entry for the wired connection, but shows no hostname.
The wireless connection’s lease will expire 1 second later and has the hostname variable.
Is this function broken by design?

Regards

Balazs Vinarz commented on 11.07.2019 15:46

screenshot attachment

Admin
Jo-Philipp Wich commented on 11.07.2019 15:55

Is the hostname present for both IPs in /var/dhcp.leases ?

Balazs Vinarz commented on 12.07.2019 08:46

No

Admin
Jo-Philipp Wich commented on 12.07.2019 08:52

Then it seems to be either an issue with the DHCP client of this machine and/or with DNSmasq's handling of leases.

Project Manager
Petr Štetiar commented on 14.07.2019 19:37

Please try to reproduce it with the latest snapshot images, for details please follow https://openwrt.org/docs/guide-quick-start/developmentinstallation

Balazs Vinarz commented on 16.07.2019 07:44

Hello Petr,

did you change anything on the code? Will the commit available on the 19.07 release as well? This my main router, I don't really want to spend my time with snapshots on it, but I'm planning to upgrade to the latest stable build if it's out.
DHCP server seems to get the hostname from "both" the clients:

Tue Jul 16 09:39:43 2019 daemon.info dnsmasq-dhcp[10524]: DHCPREQUEST(br-lan) 192.168.1.178 00:xx:xx:xx:xx:xx
Tue Jul 16 09:39:43 2019 daemon.info dnsmasq-dhcp[10524]: DHCPACK(br-lan) 192.168.1.178 00:xx:xx:xx:xx:xx archEEE900
.
Tue Jul 16 09:40:08 2019 daemon.info hostapd: wlan0: STA 00:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Tue Jul 16 09:40:08 2019 daemon.info hostapd: wlan0: STA 00:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 5)
Tue Jul 16 09:40:08 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 00:xx:xx:xx:xx:xx
Tue Jul 16 09:40:08 2019 daemon.info hostapd: wlan0: STA 00:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Tue Jul 16 09:40:08 2019 daemon.info dnsmasq-dhcp[10524]: DHCPREQUEST(br-lan) 192.168.1.161 00:xx:xx:xx:xx:xx
Tue Jul 16 09:40:08 2019 daemon.info dnsmasq-dhcp[10524]: DHCPACK(br-lan) 192.168.1.161 00:xx:xx:xx:xx:xx archEEE900

Regards

Project Manager
Petr Štetiar commented on 16.07.2019 08:05
did you change anything on the code?

Nope, but there were a lot of changes in the dnsmasq package, which are available in the latest snapshot images:

* dnsmasq: move feature detection inside a shell func
* dnsmasq: skip options that are not compiled in
* package/dnsmasq: add max_ttl/min_cache_ttl/max_cache_ttl
* dnsmasq: prefer localuse over resolvfile guesswork
* dnsmasq: allow using dnsmasq as the sole resolver
* dnsmasq: ensure test and rc order as older than final releases
* dnsmasq: add rapid commit config option
* dnsmasq: latest pre-2.81 patches
* dnsmasq: allow building without tftp server support
* dnsmasq: backport latest pre2.81 patches
* dnsmasq: Fix dhcp-boot, dhcp-reply-delay and pxe-prompt regressions
* dnsmasq: fix ipv6 ipset bug
* dnsmasq: follow upstream dnsmasq pre-v2.81 v2
* Revert "dnsmasq: follow upstream dnsmasq pre-v2.81"
* dnsmasq: follow upstream dnsmasq pre-v2.81
* dnsmasq: drop dnssec timestamp file patch
* dnsmasq: tighten config file permissions
* dnsmasq: bump to v2.80
* dnsmasq: fix dnsmasq failure to start when ujail'd
* dnsmasq: bump to v2.80rc1
* dnsmasq: fix compile issue
* dnsmasq: add dhcp-ignore-names support - CERT VU#598349
* dnsmasq: bump to v2.80test8
* dnsmasq: bump to v2.80test7
* dnsmasq: Change behavior when RD bit unset in queries.
* dnsmasq: Handle memory allocation failure in make_non_terminals()
* dnsmasq: bump to dnsmasq 2.80test6
* dnsmasq: allow dnsmasq variants to be included in image
* dnsmasq: bump to dnsmasq v2.80test5
* dnsmasq: remove creation of /etc/ethers
* dnsmasq: bump to dnsmasq v2.80test3
* dnsmasq: don't use network functions at boottime (FS#1542)
* dnsmasq: bump to latest patches on 2.80rc2
* dnsmasq: fix dnsmasq startup issue
* dnsmasq: fix confdir option processing (FS#1572)
* Revert "dnsmasq: use "hostsdir" instead of "addn-hosts""
* dnsmasq: use "hostsdir" instead of "addn-hosts"

so it might be fixed already. If it's not fixed in the latest snapshots, then it's going to be broken in the 19.07 release as well. So if you can confirm, that the problem still exists in the snapshots, there might be some small chance (but still worth the effort), that someone would pick this up, fix it in master and backport this fix to 19.07 branch.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing