[Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)

[L&LD]

Yes, expected (alpha build and all...). But does the network, work?

 

[Wallace_n_Gromit]

Shieldsup! Too right!

Yup, I found a old link on grc.com, when Steve Gibson first posted (circa. 2000) about how marvelous ZoneAlarm (v. 2.0) was at the time. [https://www.grc.com/zonealarm.htm]

And during my trip down memory lane I came across this on grc.com [https://www.grc.com/lt/hardware.htm]. Where Steven Gibson gives a "recommend(ation) ... without reservation" to a website called "Practically Networked" run by @thiggins! (I didn't realize how ancient he was!!!)

 

[Linux_Chemist]

Yup, I found a old link on grc.com, when Steve Gibson first posted (circa. 2000) about how marvelous ZoneAlarm (v. 2.0) was at the time. [https://www.grc.com/zonealarm.htm]

And during my trip down memory lane I came across this on grc.com [https://www.grc.com/lt/hardware.htm]. Where Steven Gibson gives a "recommend(ation) ... without reservation" to a website called "Practically Networked" run by @thiggins! (I didn't realize how ancient he was!!!)

Distinct memories of first getting into computing the hard way: defragmenting drive C and watching the little boxes blink red and green and blue for hours trying to tweak performance, and stumbling onto grc to check for 'security holes'! haha The golden age! I hope history underlines well just how awesome the internet was back then - like discovering a new digital frontier and the stargate was a piddly modem that was no good if someone rang you while you were using it haha

Could never have imagined how things would change so much!

 

[Xentrk]

Spoke too soon earlier. System log still getting spammed every 30 seconds using Alpha-3.

Nov 16 11:42:55 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
Nov 16 11:42:55 RT-AC88U-8248 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Nov 16 11:43:25 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
Nov 16 11:43:25 RT-AC88U-8248 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Nov 16 11:43:55 RT-AC88U-8248 rc_service: watchdog 439:notify_rc start_cfgsync
<snip>

 

[princi]

Do you remember the days (around 1999ish) when Zone Labs developed a Internet Activity Monitor which became the first software firewall ZoneAlarm. I remember following that development at grc.com. Used it for years. Those were simpler times.

The golden age! I hope history underlines well just how awesome the internet was back then - like discovering a new digital frontier and the stargate was a piddly modem that was no good if someone rang you while you were using it haha

I remember using an acoustic coupler!

But running Windows 1.0 on a twin floppy system is perhaps my fondest memory.

 

[HeadBanger]

Installed A3 on AX88U and AC68U (node) and it all seems to be running well.

I’ve noticed one small issue on the DNS filtering. Any devices set up with DNS exceptions (either with no filter or a different filter) appear to be ignored and the global filter is applied.

HB

 

[SomeWhereOverTheRainBow]

Installed A3 on AX88U and AC68U (node) and it all seems to be running well.

I’ve noticed one small issue on the DNS filtering. Any devices set up with DNS exceptions (either with no filter or a different filter) appear to be ignored and the global filter is applied.

HB

I am not running into this issue on my setup. What devices are you noticing this behavior with? there are new IOS and android update features that allow these devices to randomize their mac addresses. If you don't disable it within the device, then your devices will run on global since they are no longer matched to the mac addresses on your no filter list.

For more details, check out this thread----
http://www.snbforums.com/threads/by...-on-both-my-2-4-and-5ghz-wifi-networks.67677/
@dave14305 elegantly pointed this out to a similar post.

 

[y-y]

I'm using RT-AC5300 (main) and RT-AC68U (node). Just tried alpha-3 (also tested beta 7 and 8). All three firmwares have the same issue on the RT-AC5300 -- Received the WAN internet IP address, alpha 3 web admin interface showed the internet status was connected (beta 7 and 8 showed the internet was disconnected). WiFi client were able to connect to the internet for a very short period (like a minute) after the router reboot. After that, clients were not able to connect to the internet.

Tried setting WAN MTU to 1500. Still not working.

Any RT-AC5300 testers? Any suggestions? Thanks.

I re-tested it, and found the disconnected internet issue is likely caused by guest network 1. I've updated my test result in the official firmware 386 RC testing thread. Please follow it there if you are interested / affected.

Cheers

 

[zenmota]

I noticed that since flashing to the 386.1 alpha builds that on the Network Map screen where is shows Internet Status it shows my IP address, which is correct. However, if I turn on the VPN Client (SurfShark) it still shows the same IP address (even after refresh page or log off and back into router) even thought going through the VPN I should and do have a different IP Address. All the Merlin Builds before 386.1 when I turn the VPN on it would show not connected to the Internet (for some reason) and I can't remember if it showed a different IP Address or not. Using the ASUS RT-AC86U Router. Hope I explained so you can understand it. Have attached screen shot to show page I was talking about.

Thanks

 

[L&LD]

If it shows anything other than your ISP given address, I'd be very worried.

 

[JSinFCVA]

I remember using an acoustic coupler!

But running Windows 1.0 on a twin floppy system is perhaps my fondest memory.

LOL... those were the days. Cut my teeth building a S100 bus CP/M system and getting WordStar running from 8" floppy disks.

 

[princi]

LOL... those were the days. Cut my teeth building a S100 bus CP/M system and getting WordStar running from 8" floppy disks.

Ah, memories of Grade 7 came flooding back.

Micromation

 

[swejuggalo]

I thought at first that Asus brought back some auto channel issue but the issue don't act the same way.
Tested with manual channels now too. But over time 5GHz stops and does not let any clients connect (using Smart Connect/mac filtering). If I reboot the router 5GHz works again. The 5GHz is still visible when it happens but simply not used/accessible. Don't know the exact time frame this happens yet or exactly what to look for in the logs but we see. But the uptime is just a bit over a day. I'll see if I can find something in the logs.
Anyone else using Smart Connect with this issue? Only on AX88 perhaps?

 

[jerrytouille]

Newbie question: how long does it usually take to go from alpha to beta or release? Thank you.

 

[Treadler]

Newbie question: how long does it usually take to go from alpha to beta or release? Thank you.

How long is a piece of string?
Generally, weeks. As long as it needs/takes.

 

[HeadBanger]

I am not running into this issue on my setup. What devices are you noticing this behavior with? there are new IOS and android update features that allow these devices to randomize their mac addresses. If you don't disable it within the device, then your devices will run on global since they are no longer matched to the mac addresses on your no filter list.

For more details, check out this thread----
http://www.snbforums.com/threads/by...-on-both-my-2-4-and-5ghz-wifi-networks.67677/
@dave14305 elegantly pointed this out to a similar post.

Thank you - I was completely unaware of this. Yes, this is the issue!

Nothing to do with the new firmware then - apologies.

HB

 

[Treadler]

Went from latest stable to alpha 3 on my two RT-AC68U. Cleared NVRAM on both after flash and rebooted a 2nd time on both so JFFS would mount. Set up AiMesh with ethernet backhaul without any problems.

QoS seems broken - using Adaptive QoS sites won't load all the way, or if they do they take forever. Traditional QoS also seems to be poorly performing, with Core 1 hitting 99% load and only able to get 200mbps on speed test (normally my connection tops out at 360mbps). With QoS off I get my 360mbps (though core 1 still shows 99% usage). This is on wired connection -> aimesh node -> wired backhaul -> main router -> cable modem. Only other setting I changed is using my own DNS servers and enabling DNS over TLS.

Edit: QoS issue doesn't seem to be present in the latest ASUS AiMesh2 RC firmware. Then again, it's not quite an Apples to Apples comparison. On the firmware from ASUS, the version number seems higher and there are no DNS over TLS options for me to turn on.

Adaptive QoS working ok here on 100/40.

 

[Treadler]

I thought at first that Asus brought back some auto channel issue but the issue don't act the same way.
Tested with manual channels now too. But over time 5GHz stops and does not let any clients connect (using Smart Connect/mac filtering). If I reboot the router 5GHz works again. The 5GHz is still visible when it happens but simply not used/accessible. Don't know the exact time frame this happens yet or exactly what to look for in the logs but we see. But the uptime is just a bit over a day. I'll see if I can find something in the logs.
Anyone else using Smart Connect with this issue? Only on AX88 perhaps?

Using smart connect with auto channels (no Mac filtering) here, all good. (80mhz wide for 5ghz).

 

[zenmota]

If it shows anything other than your ISP given address, I'd be very worried.

Excuse me but I am somewhat new to the VPN thing, so bear with me. I think that when you are going through a VPN it looks like you have a different IP Address. So when going through a VPN on the Network Map Screen would it show the different IP Address from the VPN or the "real" IP Address you get from your ISP? I do know that in all the builds before, even the ASUS ones, when going through a VPN it would always show that I was disconnected from Internet, even though I wasn't (Internet worked fine, just the speed was about half). I can't remember what IP Address it would show, maybe none since it said not connected to the Internet.

Thanks.....

 

[brummygit]

I thought at first that Asus brought back some auto channel issue but the issue don't act the same way.
Tested with manual channels now too. But over time 5GHz stops and does not let any clients connect (using Smart Connect/mac filtering). If I reboot the router 5GHz works again. The 5GHz is still visible when it happens but simply not used/accessible. Don't know the exact time frame this happens yet or exactly what to look for in the logs but we see. But the uptime is just a bit over a day. I'll see if I can find something in the logs.
Anyone else using Smart Connect with this issue? Only on AX88 perhaps?

I'm seeing similar on 2.4Ghz in my case. The networks still appear using InSSIDer but clients can't connect and work. It needs a full system reboot to get them working again. This happens occasionally, but I can't work out any triggers. Sometimes I have a real game to get things working again as the devices do not reconnect straight away after a simple system reboot and I end up in a world of pain.

I am using Smart Connect with fixed channels on both 2.4Ghz and 5Ghz, and have all AX functionality turned off (however I suspect this last point is snake oil). I have an AX88U (spot a pattern here??) on Alpha 3 and 2 AX56Us on the newer official RC8 code as nodes. I also saw similar behaviour on 384.19 but have done a full reset and manual configure when moving to alpha / beta.

EDIT: My nodes use ethernet backhaul

I also occasionally see a node start moving it's 5Ghz off channel 100 (my manual setting) and start bouncing it around other channels. It's as though it gets stuck thinking it is seeing interference but again devices don't seem to attach to the affected node - my quick fix is to remove the node from the mesh and re-add it.

I personally think there is still some dodgy behaviour in the AX network drivers, however my 2.4Ghz signals seem to be improved on the 386 code.