No IPv4 adresses offered on LAN of GL-AR150 if no LAN cable is plugged during boot
Username: Tobias Leupold
Origin: https://bugs.openwrt.org/index.php?do=details&task_id=2145
This is 100 % reproducible with a fresh and unchanged installation of OpenWRT 18.06.2 on a GL-Inet GL-AR150, and it gave me quite some headache until I found out what’s happening here:
If a LAN cable is plugged during the device’s boot process and one does a DHCP request when it’s ready, the router offers an IPv4 address (as expected) and one can access it on 192.168.1.1. This is also the case for a DHCP request via WLAN, as soon as one does enable it.
If however the device is powered up without a LAN cable being plugged, no IPv4 address will be offered, neither for a LAN nor for a WLAN connection. One can connect to the router via the IPv6 address to be found in /etc/resov.conf (on the client) though, but not via IPv4. This is also the case if a LAN cable is plugged after booting.
Looking at /var/etc/dnsmasq.conf.cfg01411c, it does contain the line
dhcp-range=set:lan,192.168.1.100,192.168.1.249,255.255.255.0,12h
if a LAN cable has been plugged during bootup, and no such entry if none has been plugged.
This makes the device completely unusable for what I intend to use it ... as this happens with a completely unaltered, fresh installation, I suppose this is no misconfiguration but a bug?