Beta Asuswrt-Merlin 3004.388.6 Beta is now available

[HeadBanger]

Works as expectedet at my network.

Same router GT-AXE16000?

HB

 

[octopus]

The route/subnet is pushed from the server side. So you need to check that's not creating the conflict you're seeing.

tun11
/usr/sbin/ip addr add dev tun11 10.128.2.92/22

PUSH: Received control message: 'PUSH_REPLY,ping 10,ping-restart 60,persist-key,redirect-gateway def1,explicit-exit-notify 2,route-gateway 10.128.0.1,topology subnet,compress ,dhcp-option DNS 46.227.67.134,dhcp-option DNS 192.165.9.158,ifconfig 10.128.2.92 255.255.252.0,peer-id 29,cipher AES-256-GCM'
tun12
/usr/sbin/ip addr add dev tun12 10.128.2.123/22

PUSH: Received control message: 'PUSH_REPLY,ping 10,ping-restart 60,persist-key,redirect-gateway def1,explicit-exit-notify 2,route-gateway 10.128.0.1,topology subnet,compress ,dhcp-option DNS 192.165.9.158,dhcp-option DNS 46.227.67.134,ifconfig 10.128.2.123 255.255.252.0,peer-id 26,cipher AES-256-GCM'

 

[Treadler]

All working well here.

 

[Damit1]

Waiting anxiously for release.
All looks super solid.
7 Days is way more than enough to confirm.

 

[ColinTaylor]

tun11
/usr/sbin/ip addr add dev tun11 10.128.2.92/22

PUSH: Received control message: 'PUSH_REPLY,ping 10,ping-restart 60,persist-key,redirect-gateway def1,explicit-exit-notify 2,route-gateway 10.128.0.1,topology subnet,compress ,dhcp-option DNS 46.227.67.134,dhcp-option DNS 192.165.9.158,ifconfig 10.128.2.92 255.255.252.0,peer-id 29,cipher AES-256-GCM'
tun12
/usr/sbin/ip addr add dev tun12 10.128.2.123/22

PUSH: Received control message: 'PUSH_REPLY,ping 10,ping-restart 60,persist-key,redirect-gateway def1,explicit-exit-notify 2,route-gateway 10.128.0.1,topology subnet,compress ,dhcp-option DNS 192.165.9.158,dhcp-option DNS 46.227.67.134,ifconfig 10.128.2.123 255.255.252.0,peer-id 26,cipher AES-256-GCM'

Yes I saw that which is why I said you have to check the server side because this is not something you can change on the client side.

 

[RMerlin]

f you disable other WiFi bands whilst leaving 2.4 on

Which specific band did you disable?

 

[Heino]

Am I the only one whose XT12 LEDs are not working properly?
I have not been able to find anything about this and I have had this problem with every Merlin FW I have used (i.e. the last 3 versions...)
I have a setup with 2 XT12 (master and slave, connected via 5GHz-2 backhaul).
I have actually switched off the LEDs, as they bother me.
Nevertheless, after every scheduled reboot (I do this automatically two days a week) the LEDs are switched on again!
Both the app and the web interface show the LEDs as disabled, but they are still on - I then have to switch the LED settings on again and off again so that they are really off again - and that after every reboot - it's driving me crazy...
Please, please to the developer, would be really great if you could take a look at this - THANK YOU!!!

PS: I have done a factory reset after flash on both XT12s, but unfortunately it doesn't help.

 

[Heino]

btw - I have configured the WPS button to switch the LEDs on/off as a workaround so that I don't always have to go into the app.
BUT, this setting only takes effect on the master, this setting is ignored on the slave...

 

[Dedel66]

Same router GT-AXE16000?

HB

My setup is described in my signature and I encourage you to add a signature too.

I'm patiently waiting for the release.

 

[HeadBanger]

My setup is described in my signature and I encourage you to add a signature too.

I'm patiently waiting for the release.

Ah sorry I usually only browse this forum on my phone and signatures are not shown.

HB

 

[Ripshod]

@HeadBanger if you enable auto-rotate on your phone and flip to landscape mode you'll see the signatures.

 

[HeadBanger]

Which specific band did you disable?

To start with I disabled all except 2.4 but if any other band bar 2.4 is disabled, it reports 2.4 is off (when it isn’t). With just 2.4 enabled it actually comes up with an additional warning that I have WiFi switched completely off.

It’s no biggy as it’s just a visual glitch on the GUI (for me anyway).

HB

edit - just checked this again and it's actually only disabling the 6G band that causes the bug - i.e. it reports that 2.4G is disabled when it is actually on.

 

[HeadBanger]

@HeadBanger if you enable auto-rotate on your phone and flip to landscape mode you'll see the signatures.

Thank you! Didn’t know that.
I have learned something new today

HB

 

[octopus]

Yes I saw that which is why I said you have to check the server side because this is not something you can change on the client side.

The reason I ask is that my vpn provider gives out the same route-gateway for both my vpnclients 1&2.
Don't know if it works that way or I have to contact them to fix this.
But different:
dev tun11 10.128.2.92/22
dev tun12 10.128.2.123/22
There of my wonder.

 

[RMerlin]

The reason I ask is that my vpn provider gives out the same route-gateway for both my vpnclients 1&2.
Don't know if it works that way or I have to contact them to fix this.
But different:
dev tun11 10.128.2.92/22
dev tun12 10.128.2.123/22
There of my wonder.

You can't have two tunnels with overlapping subnets, one of them will always have priority over the other one.

 

[Stpa67]

On my RT-AX58U the "System Log => Port Forwarding" doesn't show any UPNP forwards even though i have a few active ones.

It was the same with 3004.388_5.

 

[Damit1]

@HeadBanger if you enable auto-rotate on your phone and flip to landscape mode you'll see the signatures.

I just learned something new today!
Im also mostly on mobile, portrait mode only.
Omce auto-rotate is enabled, click- magic!
Good to know, thanks!

 

[RMerlin]

On my RT-AX58U the "System Log => Port Forwarding" doesn't show any UPNP forwards even though i have a few active ones.

It was the same with 3004.388_5.

Works for me. Are you sure UPNP is enabled and you do have actual UPNP port forwards in place?

iptables -t nat -L VUPNP -vn

should confirm whether you truly have forwarded ports.

 

[RMerlin]

edit - just checked this again and it's actually only disabling the 6G band that causes the bug - i.e. it reports that 2.4G is disabled when it is actually on.

Thanks, fixed.

 

[m0rF1uS]

The reason I ask is that my vpn provider gives out the same route-gateway for both my vpnclients 1&2.
Don't know if it works that way or I have to contact them to fix this.
But different:
dev tun11 10.128.2.92/22
dev tun12 10.128.2.123/22
There of my wonder.

Maybe if you do one connection UDP and the other one TCP?