TP-Link TLWPA8631Pv3

I would like to replace my Community Fibre LinkSys VELOP WHW0301CF-UK with my WRT flashed and tested TLWPA8631Pv3. My TLWPA8631Pv3 has 3x ethernet ports. I need to assign lan1 to my ADTRAN SDX621i XGSPON WAN fibre and bridge lan2/lan3 and wi-fi to my LAN, then add firewall/security between WAN/LAN, internal DHCP, MAC filtering. Has anyone a guide or advice on how to configure? Appreciate any assistance and apologies if I tread on any toes. d:o)

This should be possible, but we should start by looking at your configuration and recommending changes specific to your situation.

Please connect to your OpenWrt device 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

I'm running something similar, @WolfWare:

  • a Mikrotik routerboard RBM33G running OpenWrt, with the fibre GPON as its uplink in the first (WAN) port and a switch connected to one the two other ports
  • the Community Fibre provided Velop (WHW03CFv2, which i think is just a WHW03 v2 pre-configured for Community Fibre, hence the "CF") acting as a wifi hotspot in bridge, connected to the other port of the OpenWrt router (if i remember correctly)

Nothing specific to configure, it essentially just works.

By default, OpenWrt bridges the lan ports in the router's switch, has sensible firewall rules preventing WAN -> LAN traffic, provides DHCP, as you will have seen if you tested your TLWPA8631Pv3.
Mac filtering you'll have to do yourself, but shouldn't be too hard.

Thanks to all. I did get there after some tentative steps and it worked well enough, but in the end I retro-flashed it back to its TP-Link firmware, then stuck it in the shed at the end of the garden, next to the Walnut tree, to improve coverage on warmer days spent outside. I replaced it, in the house with a TP-Link Archer C6, which made a big improvement/performance/difference to the WLAN 2.4/5.0Ghz and allowed me to retire all my other distributed AP devices. I also upgraded all Powerline devices, gaining a 1Gb network in consequence. Very cool.

Poor Points on the Archer C6:

  1. No ability to assign/associate descriptive names to reserved IP nodes.

  2. Far, far, far too much wasted screen real-estate. Roughly a third of the display, across all informational and configurable areas, is just sitting there doing nothing, which can really pi$$ you off. I.E. Instead of being able to scroll through my reserved IP nodes, I suddenly find they have been paged, which is a pain when you want to quickly refer to an entry two pages back in relation to where you have now been corralled. Let's sacrifice real-estate for constipate, really? Hmm...

  3. There is no option to disable or just extend auto logoff. It even logs you off when you are actively typing in the GUI!

TP-Link products are, for me, okay, but they are starting to loose me a little. Oh well, at least the squirrel's love the Walnuts! d:o)

So, most people do not like screenshots unless there is something in a cat call they want to see how it was implemented.

So:
Please connect to your OpenWrt device 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

Do not be surprised if they ask for another config.

:spiral_notepad: My refresh seems to be broken.

:triumph: :angry:

When you enable it in LuCI cat /etc/init.d/sqm should show it as '1'. so check and be sure.

Reboot and do the same call and see if it changes to '0'.
Below explains how to do a cat call; we may not need all that but it won't hurt to provide the results of them too.

Anyway,
I'm leaning toward somehow you have a read-only issue.