WAN disconnects after connection

Installing and Using OpenWrt Network and Wireless Configuration
1

I have a openwrt device based on an mt7628 running openwrt v21.02.0. The device is configured to run in station mode and I have no issues connecting to my home wifi with it's current configuration. However, I am trying to connect it to a new wifi network and am struggling to get it to stay connected. Here all all the relative logs:

Sat Mar  5 00:40:48 2022 daemon.notice netifd: Interface 'wan' is enabled
Sat Mar  5 00:40:49 2022 daemon.notice wpa_supplicant[1154]: wlan0: SME: Trying to authenticate with <addr> (SSID=<my-ssid> freq=2462 MHz)
Sat Mar  5 00:40:49 2022 kern.info kernel: [   39.648502] wlan0: authenticate with <addr>
Sat Mar  5 00:40:49 2022 kern.info kernel: [   39.667265] wlan0: send auth to <addr> (try 1/3)
Sat Mar  5 00:40:49 2022 kern.info kernel: [   39.679744] wlan0: authenticated
Sat Mar  5 00:40:49 2022 daemon.notice wpa_supplicant[1154]: wlan0: Trying to associate with <addr> (SSID=<my-ssid> freq=2462 MHz)
Sat Mar  5 00:40:49 2022 kern.info kernel: [   39.690393] wlan0: associate with <addr> (try 1/3)
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.703340] wlan0: RX AssocResp from <addr> (capab=0x1431 status=0 aid=1)
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.718990] wlan0: associated
Sat Mar  5 00:40:50 2022 daemon.notice hostapd: handle_probe_req: send failed
Sat Mar  5 00:40:50 2022 daemon.notice netifd: Network device 'wlan0' link is up
Sat Mar  5 00:40:50 2022 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Mar  5 00:40:50 2022 daemon.notice netifd: Interface 'wan' is setting up now
Sat Mar  5 00:40:50 2022 daemon.notice wpa_supplicant[1154]: wlan0: Associated with <addr>
Sat Mar  5 00:40:50 2022 daemon.notice wpa_supplicant[1154]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sat Mar  5 00:40:50 2022 daemon.notice wpa_supplicant[1154]: wlan0: WPA: Key negotiation completed with <addr> [PTK=CCMP GTK=CCMP]
Sat Mar  5 00:40:50 2022 daemon.notice wpa_supplicant[1154]: wlan0: CTRL-EVENT-CONNECTED - Connection to <addr> completed [id=0 id_str=]
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.746588] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sat Mar  5 00:40:50 2022 kern.debug kernel: [   39.760966] wlan0: Limiting TX power to 5 dBm as advertised by <addr>
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.774636] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.787904] br-lan: port 2(wlan0-1) entered blocking state
Sat Mar  5 00:40:50 2022 kern.info kernel: [   39.798823] br-lan: port 2(wlan0-1) entered forwarding state
Sat Mar  5 00:40:50 2022 daemon.notice netifd: Network device 'wlan0-1' link is up
Sat Mar  5 00:40:50 2022 daemon.notice netifd: wan (2232): udhcpc: started, v1.33.1
Sat Mar  5 00:40:50 2022 daemon.notice netifd: wan (2232): udhcpc: sending discover
Sat Mar  5 00:40:53 2022 daemon.notice netifd: wan (2232): udhcpc: sending discover
Sat Mar  5 00:40:53 2022 daemon.notice netifd: wan (2232): udhcpc: sending select for 10.254.8.239
Sat Mar  5 00:40:53 2022 daemon.notice netifd: wan (2232): udhcpc: lease of 10.254.8.239 obtained, lease time 691200
Sat Mar  5 00:40:53 2022 daemon.notice netifd: Interface 'wan' is now up
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain test
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain onion
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain localhost
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain local
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain invalid
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain bind
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using only locally-known addresses for domain lan
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using nameserver 75.75.75.75#53
Sat Mar  5 00:40:53 2022 daemon.info dnsmasq[1936]: using nameserver 75.75.76.76#53
Sat Mar  5 00:40:53 2022 user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'lan' is now down
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.377225] br-lan: port 2(wlan0-1) entered disabled state
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.388278] br-lan: port 1(eth0) entered disabled state
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.457129] device eth0 left promiscuous mode
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.465985] br-lan: port 1(eth0) entered disabled state
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.513866] device wlan0-1 left promiscuous mode
Sat Mar  5 00:42:27 2022 kern.info kernel: [  137.523250] br-lan: port 2(wlan0-1) entered disabled state
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'lan' is disabled
Sat Mar  5 00:42:27 2022 daemon.err odhcpd[1270]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Network device 'eth0' link is down
Sat Mar  5 00:42:27 2022 daemon.err odhcpd[1270]: setsockopt(SO_BINDTODEVICE): No such device
Sat Mar  5 00:42:27 2022 daemon.notice netifd: bridge 'br-lan' link is down
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'loopback' is now down
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'loopback' is disabled
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Network device 'lo' link is down
Sat Mar  5 00:42:27 2022 daemon.notice netifd: Interface 'loopback' has link connectivity loss
Sat Mar  5 00:42:28 2022 daemon.notice netifd: wan (2232): udhcpc: received SIGTERM
Sat Mar  5 00:42:28 2022 daemon.notice netifd: wan (2232): udhcpc: unicasting a release of 10.254.8.239 to 192.0.2.1
Sat Mar  5 00:42:28 2022 daemon.notice netifd: wan (2232): udhcpc: sending release
Sat Mar  5 00:42:28 2022 daemon.notice netifd: wan (2232): udhcpc: entering released state
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: Remove interface 'wlan0-1'
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: wlan0-1: interface state ENABLED->DISABLED
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: wlan0-1: AP-DISABLED
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: nl80211: deinit ifname=wlan0-1 disabled_11b_rates=0
Sat Mar  5 00:42:28 2022 daemon.notice hostapd: nl80211: Failed to remove interface wlan0-1 from bridge br-lan: No such device
Sat Mar  5 00:42:28 2022 daemon.notice netifd: Network device 'wlan0-1' link is down
Sat Mar  5 00:42:28 2022 daemon.notice netifd: wan (2232): Command failed: Permission denied
Sat Mar  5 00:42:28 2022 daemon.notice netifd: Interface 'wan' is now down
Sat Mar  5 00:42:28 2022 daemon.notice netifd: Interface 'wan' is disabled
Sat Mar  5 00:42:28 2022 daemon.warn dnsmasq[1936]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Sat Mar  5 00:42:28 2022 kern.info kernel: [  138.159440] wlan0: deauthenticating from <addr> by local choice (Reason: 3=DEAUTH_LEAVING)
Sat Mar  5 00:42:28 2022 daemon.notice netifd: Network device 'wlan0' link is down
Sat Mar  5 00:42:28 2022 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sat Mar  5 00:42:28 2022 daemon.notice wpa_supplicant[1154]: wlan0: CTRL-EVENT-DISCONNECTED bssid=<addr> reason=3 locally_generated=1

I see the device connect and authenticate with the network and receive a dhcp lease. However, you can see that udhcpc receives a SIGTERM for some reason which causes the device to leave the network. I have no idea why this is happening and need help figuring it out. I did notice that the ip address I get starts with a 10 rather than 192 which is what my home network does. Not sure if this has anything to do with it though. I'm very new to networking.

2

Does the upstream AP have a statically-set [non-DFS] channel?

It needs one set for you to connect a downstream AP without disconnects.

  • The upstream IPs can't be identical to your LAN, so this is OK
  • This means this is the network addressing scheme of the upstream AP you're connecting to - that's not an issue since they're not identical (which would cause a conflict)
1 Like
3

I have enabled only channel 6 on my device for radio0 but am still running into the same issue. Here are my wireless and network configs. Perhaps I have something misconfigured?

/etc/config/wireless

config wifi-device 'radio0'
    option type 'mac80211'
    option hwmode '11g'
    option path 'platform/10300000.wmac'
    option htmode 'HT20'
    option disabled '0'
    option channel '6'

config wifi-iface 'wan'
    option device 'radio0'
    option network 'wan'
    option mode 'sta'
    option encryption 'psk2'
    option key <my_key>
    option ssid <my_ssid>

/etc/config/network

config interface 'loopback'
    option device 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fdd0:3928:3eaa::/48'

config device
    option name 'br-lan'
    option type 'bridge'
    list ports 'eth0'

config interface 'lan'
    option device 'br-lan'
    option proto 'static'
    option netmask '255.255.255.0'
    option ip6assign '60'
    option ipaddr '192.168.2.1'

config interface 'wan'
    option proto 'dhcp'
4

What about the other device - that's the one I'm asking about.

It would need to be set to channel 6 too.