di-rect
February 20, 2026, 7:32pm
1
I'm trying to find out how I can use wireless accesspoints as my MWAN "connections".
The issue I have/see is that vlanning/tagging/untagging seems to be more complex as the Wireless interfaces are connected to the CPU.
Does anyone have a (simple) example where my MWAN connections are WLAN clients in OpenWRT so I can see what's the way to accomplish this ?
When using wireless upstream, each radio can only connect to a single upstream SSID. this means that if you have two upstreams to which you want to connect, you need to use two radios for this purpose.
From there, you'll assign the STA mode for each uplink to a different network interface. Those networks will then be referenced in the mwan3 configuration.
You don't need VLANs for this, and VLANs don't actually apply to wireless anyway.
1 Like
di-rect
February 20, 2026, 7:43pm
3
Exactly, that is what I thought. I can do 5Ghz and 2.4Ghz; that would be the plan anyways.
But as in the lucy app/gui for mwan I don't see the interfaces to be available I think; I'm still checking out.
Would this be in need of CLI configuration (as well) ? I like to compare both so I not always need to be on cli for these kinds of things; I live on the cli but not for openWRT to be honest
Let's start with your config...
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 (red circle; this works best in the 'Markdown' composer view in the blue oval):
Remember to redact passwords, VPN keys, 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
di-rect
February 20, 2026, 8:21pm
5
Thanks so far for the quick response.
Here is the most (basic) simple config with one AP to start with; as I think I can start with one and only enable that (M)WAN.
root@OpenWRT-01:~# ubus call system board
{
"kernel": "6.6.119",
"hostname": "OpenWRT-01",
"system": "Qualcomm Atheros QCA9558 ver 1 rev 0",
"model": "TP-Link Archer C7 v2",
"board_name": "tplink,archer-c7-v2",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.5",
"revision": "r29087-d9c5716d1d",
"target": "ath79/generic",
"description": "OpenWrt 24.10.5 r29087-d9c5716d1d",
"builddate": "1766005702"
}
}
root@OpenWRT-01:~# cat /etc/config/network
config interface 'loopback'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
option device 'lo'
config globals 'globals'
option packet_steering '1'
config interface 'lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '64'
option ipaddr '192.168.2.254'
option device 'br-lan'
option ipv6 '1'
config interface 'wan'
option proto 'dhcp'
option device 'eth0.2'
option ipv6 '1'
config interface 'wan6'
option proto 'dhcpv6'
option device 'eth0.2'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option vid '1'
option ports '0t 2 3 4 5'
config switch_vlan
option device 'switch0'
option vlan '2'
option vid '2'
option ports '6t 1'
config switch_vlan
option device 'switch0'
option vlan '3'
option vid '101'
option ports '0t 2t 3t 4t 5t'
config interface 'WAN_WLAN_AP-01'
option proto 'dhcp'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1.1'
root@OpenWRT-01:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'pci0000:00/0000:00:00.0'
option band '5g'
option htmode 'VHT80'
option cell_density '0'
option channel '44'
option txpower '20'
option disabled '0'
config wifi-device 'radio1'
option type 'mac80211'
option path 'platform/ahb/18100000.wmac'
option band '2g'
option cell_density '0'
option txpower '20'
option channel '11'
option htmode 'HT40'
config wifi-iface 'wifinet1'
option device 'radio1'
option mode 'sta'
option network 'WAN_WLAN_AP-01'
option ssid 'WLAN_AP-01'
option encryption 'psk2+ccmp'
option key '*********'
option disassoc_low_ack '0'
root@OpenWRT-01:~# cat /etc/config/dhcp
config dnsmasq
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option expandhosts '1'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option localservice '1'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option local '/*******/'
option domain '*******'
list interface 'lan'
option domainneeded '1'
option strictorder '1'
option serversfile '/etc/dnsmasq.conf.server'
config dhcp 'lan'
option interface 'lan'
option leasetime '12h'
option master '1'
option ndp 'relay'
option start '11'
option limit '99'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
config domain
option name 'openwrt-01'
option ip '192.168.2.254'
config domain
option name 'proxy'
option ip '192.168.2.254'
root@OpenWRT-01:~# cat /etc/config/firewall
config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
config zone
option name 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
list network 'lan'
config zone
option name 'wan'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
list network 'wan'
list network 'wan6'
list network 'WAN_WLAN_AP-01'
config forwarding
option src 'lan'
option dest 'wan'
config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'
config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option src_ip 'fc00::/6'
option dest_ip 'fc00::/6'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type '
unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-IPSec-ESP'
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'
config rule
option name 'Allow-ISAKMP'
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'
config include
option path '/etc/firewall.user'
I'm not sure if it will affect anything, but one thought:
Consider removing the underscores, and maybe just simplifying the name like wwan1.
I don't see anything else that would be a problem.... what do you see in mwan3?
di-rect
February 20, 2026, 10:24pm
7
OK, it works; no issues with the underscores. I had some issues with my policies and routing table.
"Damn" this is nice to have! Thanks for the support so far; I'm going to check out how far you can go... and it seems to be very far!
Great!
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!
di-rect
February 22, 2026, 10:49pm
9
Yes I will; maybe it's good to have one big MWAN topic which is always open for questions... ?
system
Closed
March 4, 2026, 10:49pm
10
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.