Recent content by Shino

What are you talking about? The router uses a /64 prefix, which makes it impossible to use SLAAC to segment the IPv6 network segment.

The router automatically obtains the prefix length assigned by the ISP. You can try disabling DHCP-PD.

I use ASUS router for dialing. According to the log information, the ISP seems to assign a prefix of /60, but the prefix of router and ppp0 is /64. I made some attempts but could not configure a shorter prefix. dhcp6_client: WAN Prefix Size Requested:/60, Received:/60 dhcp6_client: bound prefix...

I know VLAN can achieve this feature, but AX86U does not provide it. I just need to isolate the devices, so I hope the method is as simple as possible.

I want to isolate a device connected to LAN from other devices, but the AX86U GUI does not have this feature. I noticed that there is a way to use ebtables, but it doesn't seem to work? ebtables -A FORWARD -i eth1 -o br0 -j DROP

You're right, I tested on another stock firmware because I thought Merlin firmware had synced it. Looks like I got something wrong, is it possible for the Merlin version to optimize this in the future?

I used a WireGuard configuration to test VPN Fusion, and found that since the client's network connection does not change and the router does not forward queries, the DNS settings in the configuration become a gimmick and DNS queries never go through Fusion, which obviously would causing...

You say your script does a daily check to stabilize at 160mhz. But the AX86U downclocks more aggressively, once there is no 160mhz connection it will downclock quickly, so the script doesn't seem to solve the problem.

Are you saying that the regulations stipulate that it needs to scan for 5 minutes from 80mhz to 160mhz? It is also a rule to drop to 80mhz within 1 minute? Is it really suitable for practical application to rigidly follow the rules and make frequent changes?

When you roam between AP devices at 160mhz, you have to wait more than 5 minutes for the node to ramp back to 160mhz from 80mhz, which makes roaming a joke. It might even be worse if you're in a place where multiple routing devices overlap.

This is a very bad change, ASUS does not consider the user experience at all, which brings frequent network outages. My samsung device would lose internet connection right after 160mhz drops to 80mhz, I had to reconnect to WiFi, the 5 minutes automatic switch back was just a waste of time.

When the router drops to 80mhz, you need to wait 5 minutes to switch back to 160mhz when connecting to a device that supports 160mhz. The speed of route degradation is much more aggressive and rapid than that of upgrade.

It's by design that the router automatically drops to 80mhz when no supported device is connected, although this conflicts with practical needs. Naturally, some people will need 160mhz. The fundamental problem is that this is the maximum wireless rate available in some areas (no WIFi 6E/7), or...

I contacted ASUS support, after dozens of days of inefficient communication and futile operations, they just replied "this is the expected result, it will not be modified", I don't know what I'm working on these days.

You seem to be replying to the wrong person, I have no problems with this thread.