I have a GPON ONT modem router as my primary router.
This device is shared between multiple people,
some of those people keeps sharing wifi password wifi QR code
So,
I purchased Xiaomi 4A and flash with openwrt and applied mac filter to all(60) (my GPON don't support more than 16 mac filter and also openwrt not supported for that).
It was working for sometime but then Internet keeps stopping in openwrt router.
restart solves the issue but it keeps happening
openwrt router is connected via LAN cable to GPON router
openwrt ip range -> 10.20.30.40 (I change to this bcz I thought maybe both having same ip range was causing the issue)
GPON ip range -> 192.168.1.1
also both router is running its own DHCP server
also both router is in same room
I wonder if running openwrt router in Bridge mode will solve the issue?
If the limit on the ISP's ONT/router is purely about the number of devices that can connect via wifi, you could set your OpenWrt router up as a dumb AP:
If, however, the limit is on the number of devices in general (wired or wireless) that can connect to the ONT/router device, a dumb AP (bridge device) won't help.
We cannot say at this point why your internet connection is stopping -- it could be related to the upstream ONT/router (i.e. too many devices connected), or it could be due to a misconfiguration of your router... to rule in/out the latter, let's look at your configuration:
c
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:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
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 REJECT
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
### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
# option src lan
# option src_ip 192.168.45.2
# option dest wan
# option proto tcp
# option target REJECT
# block a specific mac on wan
#config rule
# option dest wan
# option src_mac 00:11:22:33:44:66
# option target REJECT
# block incoming ICMP traffic on a zone
#config rule
# option src lan
# option proto ICMP
# option target DROP
# port redirect port coming in on wan to lan
#config redirect
# option src wan
# option src_dport 80
# option dest lan
# option dest_ip 192.168.16.235
# option dest_port 80
# option proto tcp
# port redirect of remapped ssh port (22001) on wan
#config redirect
# option src wan
# option src_dport 22001
# option dest lan
# option dest_port 22
# option proto tcp
### FULL CONFIG SECTIONS
#config rule
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 80
# option dest wan
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
# option target REJECT
#config redirect
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 1024
# option src_dport 80
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
Hi. I think i had same problem as you, i.e. my brother. He has 3 Xiaomi 4A GE in Mesh and the Mesh gateway is connected to ISP router and sends 2,4GHz WLAN. Mesh is on 5GHz. After updating from 22.03.6 to 23.05.02 (same as your version) he expirienced some issue (Inaccessable LUCI, very slow SSH and of course no internet connection). Those issues would suggest there is some OOM problems with 23.05.2 version.
We upgraded all 3 routers to snapshot from 21-03-2024 and there were no OOM issues anymore, but some other issues that make some nodes of the mesh inaccessable (There is some other problem, i have to investigate).
You can try 22.03 series and i am sure it will work really great. I have only good expirience with this model. We had 90+ uptime days with those releases.
We upgraded now to 23.05.3 and we will see if it is any better. I hope someone from dev is going to see this. I have one 4AGE running on 23.05.2 on my own mesh and waiting for it to crash, then i can post some dmesg messages and more details.