Recent content by guho

When I first got started with Aimesh using Ethernet backhaul I had trouble because I just upgraded to 2.5Gbit switches that failed to handle vlan tags! I am not sure if that applies to your problem but if something works on the router but not the nodes it may be worth checking. I sold those...

I am planning to install 3006.102.5 on my GT-AX6000 main router when it comes out of beta. My AiMesh nodes (2xAX86U Pro and 1xAX86u) run stock Asuswrt latest version. When I upgrade the main router from Merlin 3006.102.4 to Merlin 3006.102.5, is it still OK to leave the AiMesh nodes at Asus...

I have the same problem on the GT-AX6000 and also have to use dual WAN with one of the Ethernet LAN ports connected to the FIOS ONT, nothing connected to router WAN port.

Another solution that works for me is to enable Dual WAN with failover, set one of the 4 Ethernet LAN ports as primary WAN, WAN port as secondary, connect FIOS ONT to this selected LAN port of the GT-AX6000 and nothing to the WAN port. Every since I made this change I get full near-gigabit...

Another option is to use Ethernet for the firesticks. If there is ethernet near them. Use a usb-ethernet on an OTG cable.

If I have a main router GT-AX6000 running a future Merlin 3006-based firmware and the two other (non-pro) as wired backhaul AIMesh nodes and the AIMesh nodes only run 3004 (stock or Merlin) (AX86U), will the new VLAN features work across my network?

Yes, I had the same problem of only being able to connect to the router IP, not other LAN IPs from Wireguard client. But why does this need to be a nat/maquerade rule? One would think it should be possible to access LAN resources without NATing, just bridging the wireguard subnet to the LAN...

I just upgraded my AX86U from 386.5_2 to 386.7 and everything went very well. My JFFS scripts survived. AX68U node (AP mode, not AIMesh) also upgraded without problems. Thanks RMerlin!

There's a 386.7 alpha now for the ax68u. I wonder whether it fixes the problem.

My AX86U got into a bootloop after dirty upgrade from 386.4beta2 to 386.4beta3. Fortunately I had settings and jffs backups. So after a reset followed by restore it is back to normal again. Thanks RMerlin for this new beta.

How about RT-AX86U as the main router and RT-AX68U as mesh nodes or access points? Is that a sensible setup? This is what I am considering, coming from an AC86U main router and an AC68U in access point mode (wired backhaul).

I am confronted with the same question. I just ordered an RT-AX86U to replace my main router RT-AC86U. My access point (Not AIMESH) is an AC68U in access point mode (wired backhaul). Would you recommend the RT-AX68U to take its place? Or would an RT-AX58U suffice?

Please read https://github.com/RMerl/asuswrt-merlin.ng/wiki/Custom-config-files In your case, enable custom scripts and create /jffs/scripts/ipsec.postconf containing: #!/bin/sh CONFIG=$1 source /usr/sbin/helper.sh pc_replace "rightsourceip=10.10.10.0/24" "rightsourceip=192.168.2.0/24" $CONFIG

I have my IPK2 at 192.168.2.x and I do this by copying a customized /jffs/scripts/ipsec.conf to $CONFIG in /jffs/scripts/ipsec.postconf. You can also use the helper functions to only change the IPK2 address range, but I have a lot of customizations in mine, so for me it is easier to overwrite...

Under ikev2 config it says 'not authenticated'. Buttons greyed out. Where do I start so it generates an ikev2 certificate? Thanks. I have asuscomm ddns configured.