Ax23 Wifi issues

Was looking for a while to swap out my Community Fibre ISP provided Linksys. Waited too long and the Netgear I had my eye on was out of stock. Got a TP-Link AX23 V1.2, this suggests Is tplink AX23 v1.2 the same as v1 support wise it should work. The router bit seems fine but some of my devices will not connect tot he WiFi. I know there are issues in some cases with mixed mode so I disabled all the WiFi 6 bits and they did fix a few items but a lot not. The devices not connection are

A Kindle paperwhite I think this is V10 about 2 years old.
Smartplugs and switches
An old Samsung tablet (2015)
Samsung washer and Samsung dryer
A new Chromecast connects but drops out

All are solid on the ISP router. The smartplugs and Kindle are 2.4 only, not sure about the washer and dryer, both the tablet and the Chromecast are 5G. Stupidly I did not check before flashing if the standard firmware works. I can try to revert but thought I'd check if maybe I am missing anything obvious. Quite possibly I am doing something silly.

config wifi-device 'radio0'
 3         option type 'mac80211'
 4         option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
 5         option channel '13'
 6         option band '2g'
 7         option cell_density '0'
 8         option legacy_rates '1'
 9         option country 'GB'
10         option txpower '20'
11
12 config wifi-iface 'default_radio0'
13         option device 'radio0'
14         option network 'lan'
15         option mode 'ap'
16         option ssid 'house'
17         option encryption 'psk2+ccmp'
18         option key 'password'
19
20 config wifi-device 'radio1'
21         option type 'mac80211'
22         option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0+1'
23         option channel '44'
24         option band '5g'
25         option htmode 'HT40'
26         option cell_density '0'
27         option country 'GB'
28         option txpower '20'
29
30 config wifi-iface 'default_radio1'
31         option device 'radio1'
32         option network 'lan'
33         option mode 'ap'
34         option ssid 'house-5GHz'
35         option encryption 'psk2+ccmp'
36         option key 'password'

EDIT adding the devices appear in the radio list but no IP and the Kindle at least complains unable to conenct, so they see the signal.

Can you connect to the router via ssh and use logread -f before trying to connect one of the devices that have problems to the wifi? The logread entries that follow this could give some hints.

Did you add the legacy_rates option on purpose to test whether it changes the device behaviour? Same question for cell_density.

Hello fellow UK citizen,

I see you are using channel 13 for 2.4Ghz, are you sure all of your smart devices support this channel as I see so many devices only support channels 1 - 11 as apparently smart devices developers are lazy.

1 Like

Thanks. I tried a few channels including 1 but no difference.

Ok,

If you go to wireless, interface configuration, general setup, under network is LAN selected, as what you are describing is that the authentication is fine but the dhcp server is not assigning an ip address.

Are you assigning the same ssid to both wireless interfaces?

No, I've always used different ones, some of the devices the switches and the Kindle do not support 5Ghz. I've copied the SSID etc from the ISP router and it is exactly the same SSID arrangement I use in my other place with an older router.

Nihilokrat made some other suggestion I need to check but I shall have wait until tomorrow when I can disconnect the ISP router again without getting grief from others.

CommunityFibre is a dhcp connnection, so you could connect the ax23 behind the community fibre router for testing purposes,

As suggested to avoid the issue of disconnecting the house I put it behind the CF router, I don't seem to get access to the internet that way but I could connect my mobile but not the kindle.

Kindle

ri Mar 22 09:00:57 2024 daemon.info hostapd: phy0-ap0: STA 74:ec:b2:7d:b9:b9 IEEE 802.11: authenticated
Fri Mar 22 09:00:57 2024 daemon.info hostapd: phy0-ap0: STA 74:ec:b2:7d:b9:b9 IEEE 802.11: associated (aid 2)
Fri Mar 22 09:00:58 2024 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 74:ec:b2:7d:b9:b9 auth_alg=open
Fri Mar 22 09:00:58 2024 daemon.info hostapd: phy0-ap0: STA 74:ec:b2:7d:b9:b9 WPA: pairwise key handshake completed (RSN)
Fri Mar 22 09:00:58 2024 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 74:ec:b2:7d:b9:b9
Fri Mar 22 09:01:07 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 74:ec:b2:7d:b9:b9
Fri Mar 22 09:01:07 2024 daemon.info hostapd: phy0-ap0: STA 74:ec:b2:7d:b9:b9 IEEE 802.11: disassociated
Fri Mar 22 09:01:08 2024 daemon.info hostapd: phy0-ap0: STA 74:ec:b2:7d:b9:b9 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

Mobile

Fri Mar 22 09:06:34 2024 daemon.info hostapd: phy1-ap0: STA 1c:15:1f:8f:bd:a3 IEEE 802.11: authenticated
Fri Mar 22 09:06:34 2024 daemon.info hostapd: phy1-ap0: STA 1c:15:1f:8f:bd:a3 IEEE 802.11: associated (aid 1)
Fri Mar 22 09:06:34 2024 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 1c:15:1f:8f:bd:a3 auth_alg=open
Fri Mar 22 09:06:34 2024 daemon.info hostapd: phy1-ap0: STA 1c:15:1f:8f:bd:a3 WPA: pairwise key handshake completed (RSN)
Fri Mar 22 09:06:34 2024 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 1c:15:1f:8f:bd:a3

I can try again putting it onto the fibre connection before the rest are up and about.

Alright, so there is indeed an issue with DHCP, since the device disconnects before any DHCP-related message comes in. We may need more info, especially, if you have made adjustments to network, DHCP and firewall config files that can't be drawn from the wifi config excerpt you posted initially.

Please connect to your OpenWrt device again using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
1 Like

Thanks. I'll put it back as the only router in the morning, pretty well all the setting bar the WiFi are copied from my other place where I use a Pi4b and the wireless comes from a separate AP. My laptop and both our phones were working fine, the Chromecast was intermittent but did work for lengthy periods. Sure I may have goofed something somewhere.

I think I have found the issue and of course finger trouble. I will include the files etc. That way there is some data and if someone else has a similar problem and comes looking it might help to point then in the right direction.

systemboard

{
        "kernel": "5.15.137",
        "hostname": "Boleyn-Router",
        "system": "MediaTek MT7621 ver:1 eco:4",
        "model": "TP-Link Archer AX23 v1",
        "board_name": "tplink,archer-ax23-v1",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.2",
                "revision": "r23630-842932a63d",
                "target": "ramips/mt7621",
                "description": "OpenWrt 23.05.2 r23630-842932a63d"
        }
}

DHCP - I've left out all bar one of the static leases otherwise it is a massive file


  2 config dnsmasq
  3         option domainneeded '1'
  4         option localise_queries '1'
  5         option rebind_protection '1'
  6         option rebind_localhost '1'
  7         option local 'home'
  8         option domain 'home'
  9         option expandhosts '1'
 10         option cachesize '1000'
 11         option authoritative '1'
 12         option readethers '1'
 13         option leasefile '/tmp/dhcp.leases'
 14         option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
 15         option localservice '1'
 16         option ednspacket_max '1232'
 17         option sequential_ip '1'
 18         option filterwin2k '1'
 19         list server '192.168.1.250'
 20         list server '192.168.1.252'
 21
 22 config dhcp 'lan'
 23         option interface 'lan'
 24         option start '65'
 25         option limit '29'
 26         option leasetime '1'
 27         option dhcpv4 'server'
 28         list dhcp_option '4,192.168.1.1'
 29         list dhcp_option '42,192.168.1.1'
 30         list dhcp_option '6,192.168.1.250,192.168.1.252'
 31         option force '1'
 32
 33 config dhcp 'wan'
 34         option interface 'wan'
 35         option ignore '1'
 36
 37 config odhcpd 'odhcpd'
 38         option maindhcp '0'
 39         option leasefile '/tmp/hosts/odhcpd'
 40         option leasetrigger '/usr/sbin/odhcpd-update'
 41         option loglevel '4'
 42
 43 config host
 44         option name 'Smaug-DNS'
 45         option dns '1'
 46         option mac 'DC:A6:32:91:0C:51'
 47         option ip '192.168.1.250'
 48         option leasetime '12h'

Wireless, albeit after getting working I have altered some of the more conservative settings that I'd changed before ins earch of the issue.

config wifi-device 'radio0'
 3         option type 'mac80211'
 4         option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
 5         option channel '1'
 6         option band '2g'
 7         option cell_density '0'
 8         option legacy_rates '1'
 9         option country 'GB'
10         option txpower '20'
11
12 config wifi-iface 'default_radio0'
13         option device 'radio0'
14         option network 'lan'
15         option mode 'ap'
16         option ssid 'home'
17         option encryption 'psk2'
18         option key 'password'
19         option wmm '0'
20
21 config wifi-device 'radio1'
22         option type 'mac80211'
23         option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0+1'
24         option channel '44'
25         option band '5g'
26         option htmode 'HT40'
27         option cell_density '0'
28         option country 'GB'
29         option txpower '23'
30
31 config wifi-iface 'default_radio1'
32         option device 'radio1'
33         option network 'lan'
34         option mode 'ap'
35         option ssid 'home-5GHz'
36         option encryption 'psk2'
37         option key 'password'
38         option wmm '0'

network

config interface 'loopback'
 3         option device 'lo'
 4         option proto 'static'
 5         option ipaddr '127.0.0.1'
 6         option netmask '255.0.0.0'
 7
 8 config globals 'globals'
 9         option ula_prefix 'fdae:0325:2ced::/48'
10         option packet_steering '1'
11
12 config device
13         option name 'br-lan'
14         option type 'bridge'
15         list ports 'lan1'
16         list ports 'lan2'
17         list ports 'lan3'
18         list ports 'lan4'
19
20 config interface 'lan'
21         option device 'br-lan'
22         option proto 'static'
23         option ipaddr '192.168.1.1'
24         option netmask '255.255.255.0'
25         option ip6assign '60'
26         list dns '192.168.1.250'
27         list dns '192.168.1.252'
28
29 config interface 'wan'
30         option device 'wan'
31         option proto 'dhcp'
32         option hostname '*'
33         option peerdns '0'
34         list dns '192.168.1.250'
35         list dns '192.168.1.252'
36         list dns '208.67.220.220'
37         list dns '208.67.222.222'
38
39 config interface 'wan6'
40         option device 'wan'
41         option proto 'dhcpv6'

I swear I'd copied this direct from my other OpenWrt router but obviously not. In dhcp I have

  7         option local 'home'
  8         option domain 'home'

Whereas in the other router it is

option domain 'home'
option local '/home/'

I'd missed the forward slash for option local. Initially I've just blanked those options but I will put back as per the other router.

Thanks for all the help.

2 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.