I have just flashed my ASUS ac66U-B1 box to merlin 384.4_2 from a totally fresh reset. And then I reconfigured the dual wan settings using WAN port and LAN 4 port .
The problem is my phone and my PC connected to my router frequently failed to open some webpages or opened them very slowly because some resources cannot be fetched from the web. But It worked fine with no problem in version 380.69.
So my investigation began...
1. The dnsmasq works fine so it's not related to DNS.
2. I built a socks5 server on the router, and I set my PC chrome using the socks5 proxy through the proxy server on the router. Now everything worked fine. All webpages were opened without any lag.
My first intuition is to check the iptables NAT table(because through router's socks5 server, traffics in chrome are through router's OUTPUT chain instead of NAT). I found merlin 384 introduced a new balance chain which is used for load balance purpose(I remember 340 doesn't have the balance chain). I flushed it but problems were still there.
Finally I replaced the default route (wight 1 nexthop via 10.160.0.1 dev ppp0 and wight 1 nexthop via 10.160.0.1 dev ppp1) with "default via 10.160.0.1 dev ppp0". Everything worked fine.
So I think it is a bug of the default route setting. If the load balance is achieved by iptables and ip policy rule, so whether the default "nexthop" route rule is redundant?
The problem is my phone and my PC connected to my router frequently failed to open some webpages or opened them very slowly because some resources cannot be fetched from the web. But It worked fine with no problem in version 380.69.
So my investigation began...
1. The dnsmasq works fine so it's not related to DNS.
2. I built a socks5 server on the router, and I set my PC chrome using the socks5 proxy through the proxy server on the router. Now everything worked fine. All webpages were opened without any lag.
My first intuition is to check the iptables NAT table(because through router's socks5 server, traffics in chrome are through router's OUTPUT chain instead of NAT). I found merlin 384 introduced a new balance chain which is used for load balance purpose(I remember 340 doesn't have the balance chain). I flushed it but problems were still there.
Finally I replaced the default route (wight 1 nexthop via 10.160.0.1 dev ppp0 and wight 1 nexthop via 10.160.0.1 dev ppp1) with "default via 10.160.0.1 dev ppp0". Everything worked fine.
So I think it is a bug of the default route setting. If the load balance is achieved by iptables and ip policy rule, so whether the default "nexthop" route rule is redundant?
Last edited: