heysoundude
Part of the Furniture
#ThisIsTheWayPassthrough, if your Asus is behind ISP modem/router. Native, if your Asus is connected to modem only. Disabled, if you don't need IPv6.
#ThisIsTheWayPassthrough, if your Asus is behind ISP modem/router. Native, if your Asus is connected to modem only. Disabled, if you don't need IPv6.
It's a closed source Broadcom module. I'm not aware of any publicly available documentation.where can we find a description of what the fc parameters are/do? is there a man page somewhere?
Have the same issue, just with an AX88, with different DDNS provider - same issue and result as you.I have just updated my GT-AX6000 to Beta2 from 386.7.2
My DDNS (Google Domains) was showing an exclamation mark
I disabled IPv6 Update in DDNS (i have native ipv6) and its working fine now for ipv4
is this a google problem or router problem?
Do a reset to defaults and DON'T import that settings file. Hand configure from screenshots.
Have the same issue, just with an AX88, with different DDNS provider - same issue and result as you.
Im not 100% sure what you are getting at, trying to connect back to a Wireguard server via a Wireguard client which offers port-forward?Can anyone can confirm if port forwarding works with wireguard VPN Director?
I tested 2 different clients with Torguard VPN, the port still showing closed! if i try the same client with openvpn the port shows open.
any ideas? thx
I am using the Asuscomm DDNS and although IPv6 didn't work at first after a dirty update (386.8 to beta1) after a reboot it has been fine. Also, no problems after the update to beta2.Have the same issue, just with an AX88, with different DDNS provider - same issue and result as you.
That new portmap implementation is quirky on some models. It's closed source so outside of my control. On my GT-AXE16000 for instance it doesn't even appear at all, as the backend fails to generate the required data.
I have just updated my GT-AX6000 to Beta2 from 386.7.2
My DDNS (Google Domains) was showing an exclamation mark
I disabled IPv6 Update in DDNS (i have native ipv6) and its working fine now for ipv4
is this a google problem or router problem?
Hi,I added wgserver-start, wgserver-stop, wgclient-start and wgclient-stop (with the unit number passed as argument).
I can't see any javascript errors on that page.It does auto-refresh for me. Look for any Javascript error in the browser console that may be preventing the refresh from happening.
This page is in near default mode. Page layout may be affected. For default mode use "<!DOCTYPE html>".
Advanced_VPNStatus.asp Some cookies abuse the recommended "SameSite" attribute 3
Cookie "clickedItem_tab" does not have a correct "SameSite" attribute value. Soon cookies without the "SameSite" attribute or with an invalid value will be treated as "Salmon". This means that the cookie is no longer sent in external contexts. If your application depends on this cookie being available in such contexts, add the "SameSite=None" attribute to it. Read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite to learn more about the "SameSite" attribute state.js:120:67 Cookie "notification_history" does not have a correct "SameSite" attribute value. Soon cookies without the "SameSite" attribute or with an invalid value will be treated as "Salmon". This means that the cookie is no longer sent in external contexts. If your application depends on this cookie being available in such contexts, add the "SameSite=None" attribute to it. Read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite to learn more about the "SameSite" attribute state.js:128:14 Cookie "clickedItem_tab" does not have a correct "SameSite" attribute value. Soon cookies without the "SameSite" attribute or with an invalid value will be treated as "Salmon". This means that the cookie is no longer sent in external contexts. If your application depends on this cookie being available in such contexts, add the "SameSite=None" attribute to it. Read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite to learn more about the "SameSite" attribute state.js:120:6
Synchronous XMLHttpRequest on the main thread is deprecated due to its negative impact on the user experience. For more help, see http://xhr.spec.whatwg.org/
when you refer to the previous stable release, do you mean the one based on 386? If so, I'm also seeing this behaviour on my tuf-ax5400 (not supported by @RMerlin ) on 388 stock. I used to have about 110/120mb of free RAM and now it hovers around 56/62MB, with no instability being detected. Maybe something was changed in terms of RAM management/showing with 388 from 386.Memory consumption on AX86U goes up by 2% every day on Beta2.
This did not happen on previous stable release.
when you refer to the previous stable release, do you mean the one based on 386? If so, I'm also seeing this behaviour on my tuf-ax5400 (not supported by @RMerlin ) on 388 stock. I used to have about 110/120mb of free RAM and now it hovers around 56/62MB, with no instability being detected. Maybe something was changed in terms of RAM management/showing with 388 from 386.
I do recall a change being made in recent builds to not purge RAM in the same way that several older builds were doing so. RAM usage is not a bad thing as it is maintaining items in memory as required and can overwrite as necessary. This change does mean that usage will remain higher than in some of the older builds, though is by design rather than indicative of an issue.Yes, 386.7_2, this one was "RAM stable" for weeks, always same memory percentage used. 388 seems to eat more and more RAM daily. Not sure if it will sustain one month running.
No, it will be in beta 3.Hi,
Is it available in the 2'd beta?
Those are just warnings, they do not stop the page from loading properly. Errors would be in red.I can't see any javascript errors on that page.
Tried today and got 94/94 as usual, it was probably a temporary problem with the city fiber network or my isp. I have been thinking of upgrading to 1Gbit but 100Mbit works fine with qos (appletv, htpc, mobiles, android tabs, 3 laptops ...) and i don't like to increase cost if it is not neededMy internet dl speed seems to be cut down to around 80% with beta 2.
I have 100/100 and usually get around 94/94, now i get 94/80 (ul/dl), tried with aiprot and qos off but no difference.
Yes, that was my point.Those are just warnings, they do not stop the page from loading properly. Errors would be in red.
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!