Hello, I have an old TP-Link Archer C7 V2 here that I would like to operate as an Access Point (AP) using OpenWrt. However, my Wi-Fi clients are unable to communicate with the LAN ports.
After flashing the device, I configured the `lan` interface as a DHCP Client. Under the "Network > Switch" settings, I configured three VLAN IDs (see photo). My main router is connected to the WAN port, carrying three tagged VLANs. The `br-lan` bridge is linked to `eth1`; additionally, I created two new bridges: `br-guest` (linked to `eth1.40`) and `br-iot` (linked to `eth1.50`). Subsequently, I created two new interfaces: `guest` (assigned to device `br-guest`) and `iot` (assigned to device `br-iot`). Within the wireless device settings, I am able to successfully assign the desired networks. Unfortunately, however, a Wi-Fi client cannot communicate with a LAN-connected client *within the same VLAN*—even though each client is individually able to access both the Internet and the LuCI interface. Do I need to configure additional firewall rules, or have I overcomplicated things here and is there a simpler solution?
A few questions...
- Is the main router also running OpenWrt?
- if so, what port is used to connect to the C7v2?
- Is the main router directly connected to the C7v2 or is the a switch in between?
- If there is a switch, what is the brand+model of the switch?
- What port is the uplink on the C7v2?
- Finally, let's see the complete configs from the AP (and also the main router, assuming it is OpenWrt)
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
You should only use one VLAN-aware bridge, as the traffic will be separated by the VLANs themselves. No need to create mutuple bridges.
The main router is a Fritz!Box 7520 running OpenWrt; on that device, Port 3 is configured to carry tags for all three VLANs. This is a test setup involving a direct connection, without any intermediate switches. For testing purposes, the Wi-Fi network is currently running unencrypted.
network
config interface 'loopback'
option device 'lo'
option proto 'static'
list ipaddr '127.0.0.1/8'
config globals 'globals'
option dhcp_default_duid ''
option ula_prefix ''
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config interface 'lan'
option device 'br-lan'
option proto 'dhcp'
config interface 'wan'
option device 'eth0'
option proto 'dhcp'
config interface 'wan6'
option device 'eth0'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1t 2 3 6t'
option vid '10'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0t 1t 4 6t'
option vid '40'
config switch_vlan
option device 'switch0'
option vlan '3'
option ports '0t 1t 5 6t'
option vid '50'
config device
option type 'bridge'
option name 'br-gast'
list ports 'eth1.40'
config device
option type 'bridge'
option name 'br-iot'
list ports 'eth1.50'
config interface 'gast'
option proto 'dhcp'
option device 'br-gast'
config interface 'iot'
option proto 'dhcp'
option device 'br-iot'
firewall
config defaults
option syn_flood 1
option input REJECT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input REJECT
option output ACCEPT
option forward DROP
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
# Allow IPv4 ping
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
# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
config rule
option name Allow-DHCPv6
option src wan
option proto udp
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
# Allow essential incoming IPv6 ICMP traffic
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
# Allow essential forwarded IPv6 ICMP traffic
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
dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
list ra_flags 'other-config'
option ra_preference 'medium'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/odhcpd.leases'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
option piodir '/tmp/odhcpd-piodir'
option hostsdir '/tmp/hosts'
wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'pci0000:00/0000:00:00.0'
option band '5g'
option channel '36'
option htmode 'VHT80'
option cell_density '0'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
config wifi-device 'radio1'
option type 'mac80211'
option path 'platform/ahb/18100000.wmac'
option band '2g'
option channel '1'
option htmode 'HT20'
option cell_density '0'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
As a quick addendum: the Archer's WAN port is connected to the main router using a triple-tagged configuration; however, the root of the problem likely lies internally, specifically in the communication between the Archer's LAN and Wi-Fi interfaces.
You did not post your router's config -- it would be useful to see that to make sure everything correct.
That said, let's reset your AP to get it to a known good state.
After the reset:
- configure only the bare minimum
- IP address of the lan interface to an appropriate address or DHCP
- enable wifi.
- disable DHCP
- Please connect directly to your main router via one of the lan ports and make sure that you're connecting to an untagged port on the main router.
Test and see if everything is working properly (for that single network)... then please post the config of the AP (and also of the router).
I think I owe you all an apology for the confusion. I just used a different PC for testing purposes, and now everything is working correctly. The issue was evidently with the PC itself. Regardless, thank you all for your time and assistance.
