I'm curious if anyone who had issues with TimeMachine is getting better results with this release?
AX88U Pro, TimeMachine working well for me. I did not try it with the previous FW, as I was using AC86U before then.
I'm curious if anyone who had issues with TimeMachine is getting better results with this release?
Are you connecting to VPN? If so, could kill switch have activated?On my AX88U I tried a dirty upgrade from 388.7 to 388.8 and that has placed things in a very bad configuration from where no kind of network (wireless or wired) was working. Since unfortunately for the next two weeks or so I can't investigate further on that router what is wrong I had to factory reset, return to 388.7 and restore JFFS/configuration.
Are you connecting to VPN? If so, could kill switch have activated?
The wireless log will use the actual hostname whenever possible, while the Network Map is just a description label. This is working as intended.I still see that changing a device name in the network map client list does not change it in the wireless log.
This made me a sad panda
perhaps a better answer is “not in the foreseeable future”No. Wifi Radar was based on Broadcom's Visualizer, an example application from their SDK. They never updated it over the years, so Asus chose to stop using it, both because it was partly broken (didn't support WIfi 6e or 7 as Broadcom never updated it), and because of inherent security issues since the code was unmaintained.
@RMerlin, is this true even if the client is disabled? I have tried adding the router IP through the WAN but it's still not letting any traffic through when the VPN client is not enabled. What's the trick here? Am I missing something?
Did a dirty upgrade from 7 to 8 and everything is fine and the traffic block is probably due to the change log, I guess, I'll figure it out sooner or later.
Edit: Never mind, I forgot the /24 next to the router IP and that fixed it. Note to all, if you have a VPN client setup and even if it is not in use WITH the killswitch option, your traffic will be blocked after this upgrade by default. To fix this, just create a rule like this for the WAN interface under VPN Director:
Local IP
Your Router IP/24
You can leave the Remote IP field blank. That should do it.
So yeah, same issue here... GT-AX11000.... banging my head against the wall trying to figure out why the entire system goes down just inputting a VPN an never turning on. To the point it won't even let me get to the router configuration page. Static iP and cannot even ping the router .1 router after hitting aplly. Super frustrating.
I patially understand what you are saying in VPN Director but can you cleariy what you mean?
Local is what? The router IP? 192.168.50.1?
Your RouterIP/24? Again router IP or WAN IP? /24 suggests 192.168.50.1/24 so what is the above local ip then?
Thaks.
Ah I see, no had it downloaded from a few days ago. Will check. Thanks.
Which builds are you referring to?Why no info about the new test builds, or a new thread..?
From the other thread:Which builds are you referring to?
(The pre-beta tests folder is currently empty)
Probably referring to RMerlin's post in another discussion:Which builds are you referring to?
(The pre-beta tests folder is currently empty)
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!