Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Confirm the AX6S hardware revision and ImmortalWrt build, then use the radio and interface names shown by that LuCI release.
- An enabled radio and visible SSID do not prove client authentication; association does not prove a DHCP address was assigned.
- Use wireless status and logs to check radio, encryption mode and association errors. Do not publish the SSID, Wi-Fi key, MAC address or device identity.
- Change one wireless or DHCP setting at a time and keep wired management access until client connectivity is verified.
Confirm the device and firmware scope
The AX6S radio names, driver, band support and LuCI menus can vary by hardware revision and ImmortalWrt build. Confirm the model and hardware revision from the device label or management interface, and record the firmware build. Do not copy radio, channel or UCI settings from another router.
Keep a wired LAN connection or local console available before changing Wi-Fi. If the computer currently uses the Wi-Fi network to manage the router, establish an independent management path first so an authentication or bridge change cannot lock you out.
Check the radio and interface in LuCI
In LuCI's Network and Wireless pages, confirm that the intended radio exists and is enabled, then check that the Wi-Fi interface belongs to the expected LAN network. Bands can use different interfaces, security modes and client capabilities. Confirm that the client supports the band and security mode before setting an SSID and WPA key.
Do not put a real SSID, Wi-Fi password, BSSID or device serial number in a public tutorial, command, screenshot or support ticket. A saved settings page only shows that settings were written; it does not prove the radio is broadcasting or a client completed authentication.
Read wireless state and related logs
Wireless status can help identify whether a radio is enabled, which band an interface uses and whether clients are associated. hostapd or driver logs may show authentication, key negotiation or interface-start errors. Output may include an SSID, BSSID/MAC address, client name or band information; inspect it on the router and redact it before sharing.
Read radio, interface and authentication state
shubus call network.wireless status
iwinfo
logread | grep -iE 'hostapd|wpa|wireless|wifi' | tail -n 80
Separate authentication problems from DHCP
If a client cannot see the network, check radio and interface state, then confirm the selected band, SSID and regulatory-domain setting; do not reset the entire network first. If the client sees the SSID but authentication fails, compare its supported WPA modes with the interface's encryption setting and verify the entered key locally. Never paste the key into a command or log.
If the client reports connected but has no address, check whether the Wi-Fi interface belongs to the intended LAN, whether that network's DHCP server is running, whether the pool has addresses left and which gateway and DNS the client received. No lease after successful authentication is a separate path; repeatedly changing the Wi-Fi password will not fix it.
Change only the setting identified by the symptom
If the radio is confirmed disabled, enable only that radio in its LuCI page. If logs show an unsupported security mode, confirm the client capability and change only that interface's authentication mode. If association works but DHCP does not, check the interface-to-LAN binding and DHCP service. Do not change the bridge, VLAN, firewall and wireless settings together.
Save the current wireless and network configuration before each change, and change one setting at a time. Applying LuCI changes may reload wireless service and disconnect clients; keep a wired connection and confirm a recovery path before continuing. Radio names and interface relationships must be checked against the local ImmortalWrt build.
Confirm client access end to end
From a test device, confirm that the target SSID is visible, the client uses a supported security mode and association completes. Then check that it receives an address in the intended subnet, the correct gateway and DNS. Test the router management page, name resolution and an authorized external destination. An SSID or an interface-up log alone is not a complete connectivity check.
If authentication succeeds but the client gets no address, retain the association state, DHCP service status and lease evidence, then trace the network-interface path. Mark client authentication, DHCP, DNS and access as pending until each has been observed. Do not include a real Wi-Fi name, password, MAC, serial number or local screenshot path in public diagnostics.
Sources
Frequently Asked Questions
Does LuCI showing Wi-Fi enabled mean clients can reach the internet?
No. Verify SSID visibility, client authentication and association, DHCP addressing, gateway, DNS and actual access.
Should I change the Wi-Fi password when a connected client has no IP?
Not first. Authentication and DHCP are separate stages; check the LAN binding, DHCP service and address pool.
Can I post wireless status or config output in a forum?
Redact SSIDs, keys, BSSID/MAC addresses, client names, serial numbers and private paths first. Never publish the wireless key or a complete configuration.