New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mwan3 connected_v6_temp is full #15951
Comments
I try following Preventing IPv6 rules to disable mwan3 ipv6 support,but it did't works. |
This is only valid for the mwan3 which is in the master or in the openwrt-21.02. For the mwan3 in openwrt-19.07 you can change this line so that no IPV6 rules are created. I can't tell you more, because I don't know bird2. |
Hi,I have been upgrade to OpenWrt 21.02-SNAPSHOT r16235-8921e36ed8
But i can ping 1.1.1.1. on hk_1_vpn
It’s not online here, but it’s online again when shown here
|
This problem has been solved. It seems that after openwrt is updated, you need to turn on the add route in iwiregard and allow 0.0.0/0 to open at the same time to use the default gateway |
Hi,i'm runing mwan3 (2.8.16-1) on openwrt 19.07.06.
I found that the console has an output
mwan3 _connected_v6_temp is full maxelem 65536 reached
This will cause mwan3 to fail to diverge normally and luci to be inaccessible, etc.
After investigation,i think it is caused by limition of IPV6 Routing Table.
The routing table is imported init kernal by bird2,So how to remove these restrictions? Is this the problem?
Here's the configuration file
bird.conf
The text was updated successfully, but these errors were encountered: