Forums

Issues with Access Point mode

• Author
  Posts
• September 24, 2025 at 10:14 pm #6920
  strima

  Participant

  Hello,

  I have two PW-AX1800, one configured in AP mode. My first issue is no settings can be changed on the Network settings page, it just says Internal Server Error. This is preventing me from troubleshooting my second issue, which may or may not be a bug or user error. I’m unable to change VLAN tagging or change back to router mode, only option seems to be full wipe which I don’t prefer.

  My second issue is I have a NAS attached to the LAN port on the AP, it can pull an IPv4 addr from the GW router but cannot ping it or see the internet. I have VLAN tagging enabled for the single port on each in the GW-AP connection but no others (that’s where I suspect user error, perhaps I need the NAS port to be tagged as well).

  Thank you!

  September 24, 2025 at 10:22 pm #6939
  support

  Keymaster

  @strima Sorry, we missed your post previously. Do you still need help on this issue? What’s your firmware version?

  September 24, 2025 at 10:50 pm #6940
  strima

  Participant

  Yes please! Primary router 2.8.0, AP mode router 2.7.8 (forgot to mention firmware update also errors out on AP router)

  September 26, 2025 at 4:02 pm #6943
  support

  Keymaster

  @strima Can you create a backup file from the AP router and send to [email protected]? We’ll need to take a look at it.

  September 29, 2025 at 8:10 pm #6956
  strima

  Participant

  Sent a couple days ago. Might have figured it out but having trouble persisting changes to /etc/config/network (uci seems to take it but it keeps reverting. I have had 3 devices plugged into the AP LAN ports – two linux based (TrueNAS and fresh Ubuntu 24.04) and a Windows 10 box. The Windows box can reach the GW and the internet, not the linux devices. Anyway, I’m naive with VLAN tagging but Gemini suggested this – which would hopefully fix connectivity with devices plugged into LAN ports – that still leaves the issue of being unable to edit AP mode router settings or update firmware.

  Current Configuration:

  config bridge-vlan
  option device ‘eth-lan’
  option vlan ’10’
  list ports ‘eth3:t*’ # Tagged (Trunk) port
  list ports ‘eth2’ # Untagged (Access) port – NO PVID
  list ports ‘eth1’ # Untagged (Access) port – NO PVID

  Proposed Configuration:

  config bridge-vlan
  option device ‘eth-lan’
  option vlan ’10’
  list ports ‘eth3:t*’ # eth3: Tagged (Trunk) port – sends/receives tagged
  list ports ‘eth2:u*’ # eth2: Access port – untagged egress/ingress
  list ports ‘eth1:u*’ # eth1: Access port – untagged egress/ingress
  option pvid ’10’ # Set PVID 10 for all listed UNTAGGED ports (eth1, eth2)

  September 30, 2025 at 5:26 pm #6961
  support

  Keymaster

  @strima I assume you upgraded the AP to 2.8.0? Don’t edit /etc/config/network directly, it will be overwritten. Configure the VLAN assignment from the UI. Only the LAN port connecting to the main router should be tagged. Other LAN ports should be untagged, but you can assign them to different VLANs.

  October 3, 2025 at 4:43 pm #6985
  strima

  Participant

  So this is two different bug reports. The first is preventing me from doing what you suggest – upgrading firmware on the AP mode router and configuring VLANs within the UI. The bug is, any changes to network settings are met with Internal Server Error, and firmware upgrades time out / fail to resolve. If 2.8.0 for sure resolved these issues over 2.7.8, I will just need a way to pull the firmware file (possibly from my primary router which is on 2.8.0) and I’ll upgrade it manually.

  The second bug seems to relate to VLAN tagging on my AP router LAN ports. I have it set up as you suggest, the only tagged port is the one being fed from the primary router. Linux devices plugged into the other LAN ports cannot talk to the primary router or the internet – and I believe it has to do with the network config not properly assigning VLAN tags to the packets coming in from those interfaces (in this case VLAN 10 for the default LAN). The config above did not work (I ended up figuring out how to persist my changes due to the first issue above) but I suspect it’s on the right track.

  October 7, 2025 at 3:24 am #6992
  support

  Keymaster

  @strima Thanks for the additional info. We’re still looking into this.

  October 13, 2025 at 10:00 pm #7006
  support

  Keymaster

  @strima Upgrade in AP mode is broken. We’ll fix this in the next release, coming in the next few days.

• Author
  Posts