Checking Dumb AP settings using WAN port

Hi, just passing by, since whenever I can I upgrade most of the routers of my friends and family to opewrt or wrt flavors. Anyways, I wanted to check if something that I did was correct.

I have an old "TP-Link TL-WR741N/ND v4". And I wanted to bridge the wan port into the lan and wifi ports.

This is what I did:

System -> Startup -> "Firewall" set to Disabled.
Network -> Switch -> "Enable VLAN functionality" unckecked.

Network -> Interfaces -> WAN ->

  • "Bring up on boot" unchecked.
  • "Use builtin IPv6-management" unchecked.
  • "Force link" unchecked.

Network -> Interfaces -> LAN -> DHCP Server -> General Setup

  • "Ignore interface" checked.

Network -> Interfaces -> LAN -> DHCP Server -> IPV6 Settings

  • "Router Advertisement-Service" -> disabled
  • "DHCPv6-Service" -> disabled
  • "NDP-Proxy" -> disabled

Network -> Interfaces -> LAN -> Common configuration -> General Setup

  • "IPv4 address" -> Used an IP outside the main DHCP I was going to use from the main router.

Network -> Interfaces -> LAN -> Common configuration -> Advanced Settings

  • "Use builtin IPv6-management" -> unchecked (don't have the need for IPV6).

Network -> Interfaces -> LAN -> Common configuration -> Physical Settings

  • "Bridge interfaces" checked. (Bridging WAN with LAN and WLAN)
  • "Enable STP" checked.
  • "Enable IGMP snooping" checked.
  • "Interface" as follows: eth0.1 - eth1 - wlan0

Network -> Interfaces -> LAN -> Common configuration -> Firewall Settings
"Create / Assign firewall-zone": I moved the WAN into the LAN zone, just in case.

So far, I can access the router via lan port and I'm reaching internet and main router using the wan port as uplink. Also my wifi gets bridge and lan ports as well.

So, is my setup correct? is there anything missing? speed is good too, just checking with you guys if I missed anything that I may need to disable since I'm not using the routing functions, just using it as an AP for "WIFI and LAN" replication from the main.

You can delete the WAN network entirely since there won't be any way for data to enter or leave it. All the physical devices are in LAN.

So that means I did it correctly? :smiley:

I actually followed the guides and assumed that bridging the lan and wan would actually make it work... without actually knowing a lot of it.

Actually I ended up using the WAN port because I had the router in a double NAT, but since the actual router is way to out of reach physically to actually move the cable from wan to lan, I decided to use the lazy way and change the config to just an AP :slight_smile: I cannot believe I actually did it right (after a few minutes of tinkering.

Thanks, really, thank you.

Since you disabled VLANs in the switch, eth0.1 should be turned into eth0.

It still appears even thoug the vlan is disabled, and somehow it works.

Should eth0 be selected instead? or is something still not completely done?

Could it be that I need to delete the vlan too?

This is the OpenWrt default configuration on most devices with an internal switch:

  • the switch has VLANs enabled
  • CPU port is set to VLAN 1 tagged, LAN ports set to VLAN 1 untagged
  • the lan interface uses the physical interface eth0.1

An alternative configuration could be:

  • the switch has VLANs disabled, or the CPU port is set to untagged on VLAN 1
  • the lan interface uses physical interface eth0

But for a dumb AP with a bridge joining WAN and LAN ports, this alternative configuration is not necessary.
I recommend to stay with the default and keep VLANs enabled in the switch because this keeps more flexibility for future configuration changes.

Yes, I am also surprised that it works.

I would guess that these settings are ignored when VLANs are disabled.

Now that I notice:

Could it be that having the traffic tagged can cause high cpu utilization?

Also, I see what you explained with the untagging now:

So, it appears that, unless I untag eth0, even with vlan functionality unckecked, the system will still create eth0.1 regardless.

Also, nice that it auto migrates everything to the next interface :smiley:

And indeed there's less load.