Paul Smedley
Occasional Visitor
I have a site to site config working between an AX88U and an AC68U with beta 1..... As others have said, it's just about configuring things the right way....on ax88u there is no net to net
I have a site to site config working between an AX88U and an AC68U with beta 1..... As others have said, it's just about configuring things the right way....on ax88u there is no net to net
I've had sporadic issues with both 2.4Ghz disappearing and 5Ghz doing strange things with channels on both AX88U master plus AX56U nodes. I think there's still something wrong with the stock binaries out of RMerlin's control.Have any users of the RTAX88U on Beta 386 here experienced finding wireless radios randomly turned off?
I have the same issue. Is it related to X3 and R3 encryption? I don't understand this part really. Here is an example I found before.
on ax88u there is no net to net
I have not noticed this on mine. Been running the beta on my AX88U for 4 days now.Have any users of the RTAX88U on Beta 386 here experienced finding wireless radios randomly turned off?
Have any users of the RTAX88U on Beta 386 here experienced finding wireless radios randomly turned off?
I have not noticed anything either. Everything has been running good so far. Just waiting on Beta 2 to release for my RT-3100 model, so I can move it back over.I have not noticed this on mine. Been running the beta on my AX88U for 4 days now.
It's been mentioned several times that Guest Network 1 will use a different subnet, but other guest networks will behave as you expect, using the same subnet as the router.I'm sorry if this has been already brought up but I ran into an issue with Beta and had to flash back to the stable release.
I have the 2.4 and 5 bands split. I set the 2.4 band to isolation mode and then create a guest network for my IoTs on that band. Finally, I run a VPN client with policy based routing to tunnel all IPs except the ones I add as exceptions. The issue is that somehow the Beta build is issuing guest network IPs on a completely different subnet (192.168.101.0/24) than the LAN (192.168.50.0/24) and everything breaks once the VPN rules get applied. I didn't have that issue with the stable build. Is that a bug or a feature? If it is a feature is there an option to disable it?
I have a site to site config working between an AX88U and an AC68U with beta 1..... As others have said, it's just about configuring things the right way....
https://www.snbforums.com/threads/asuswrt-merlin-386-1-beta-is-now-available.68205/post-640396can you send a screenshot net to net on beta1? I'm whit ax88u stable 384.19 and I don't have net to net in gui.
I'm sorry if this has been already brought up but I ran into an issue with Beta and had to flash back to the stable release.
I have the 2.4 and 5 bands split. I set the 2.4 band to isolation mode and then create a guest network for my IoTs on that band. Finally, I run a VPN client with policy based routing to tunnel all IPs except the ones I add as exceptions. The issue is that somehow the Beta build is issuing guest network IPs on a completely different subnet (192.168.101.0/24) than the LAN (192.168.50.0/24) and everything breaks once the VPN rules get applied. I didn't have that issue with the stable build. Is that a bug or a feature? If it is a feature is there an option to disable it?
www.snbforums.com
can you send a screenshot net to net on beta1? I'm whit ax88u stable 384.19 and I don't have net to net in gui.
@RMerlin .. Eric.. in the official Beta Firmware, there is a problem with the Guest network ignoring block internet access and time scheduling for clients attached to any of the 3 possible SSIDs, Is this something in the closed source section of the code or is this "by design" or can/do you enforce this adherence in your code? Thank you for all you do for us..
It's been mentioned several times that Guest Network 1 will use a different subnet, but other guest networks will behave as you expect, using the same subnet as the router.
You could just try defining a route for those subnets through the VPN, which is something that YAZFI does not do yet.I'm sorry if this has been already brought up but I ran into an issue with Beta and had to flash back to the stable release.
I have the 2.4 and 5 bands split. I set the 2.4 band to isolation mode and then create a guest network for my IoTs on that band. Finally, I run a VPN client with policy based routing to tunnel all IPs except the ones I add as exceptions. The issue is that somehow the Beta build is issuing guest network IPs on a completely different subnet (192.168.101.0/24) than the LAN (192.168.50.0/24) and everything breaks once the VPN rules get applied. I didn't have that issue with the stable build. Is that a bug or a feature? If it is a feature is there an option to disable it?
#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
pc_delete "dhcp-range=br1,192.168.101.2,192.168.101.254,255.255.255.0,86400s" $CONFIG
pc_delete "dhcp-range=br2,192.168.102.2,192.168.102.254,255.255.255.0,86400s" $CONFIG
pc_replace "dhcp-option=br1,3,192.168.101.1" "dhcp-option=br1,3,192.168.2.1" $CONFIG
pc_replace "dhcp-option=br2,3,192.168.102.1" "dhcp-option=br2,3,192.168.5.1" $CONFIG
Or use PPTP/L2TP (which does basically the same). It's also much easier to configure.
Did you check if universal beamforming is turned off? It might be on after resetting to factory defaults.I've had sporadic issues with both 2.4Ghz disappearing and 5Ghz doing strange things with channels on both AX88U master plus AX56U nodes. I think there's still something wrong with the stock binaries out of RMerlin's control.
We use essential cookies to make this site work, and optional cookies to enhance your experience.