Asus RT-AC86U /w 384.6 - DDNS?

[Chrisgtl]

Hi all,

Finally got round to getting a refund on my Netgear R8000 today so went out and bought the Asus RT-AC86U instead.

First impressions are great - WiFi speeds are better than the R8000 even though the Netgear is rated higher....just goes to show. I didn't even look at the default firmware as I went straight to Merlin 384.6 so I'm a little clueless as to my question.

I am using my AC86U as an AP from my Sky Q Hub (disabled all the wireless on it). This is a fresh Sky FTC install two weeks ago so wanted to see what my line settles at before making any further decisions on changing the modem - actually the modem looks nice and seems solid so all it good apart from I can't change the DNS :-(

On my Netgear R8000 I was able to setup DDNS in AP mode. I can't see it on the Asus though - is this normal or am I blind? I'd like to be able to tap into my Asus when away from the home and because my IP isn't static I have a DDNS setup on my Sky modem and NAS etc.

Is this possible?

Also, if I was to change the Sky modem does anyone have any recommendations for something as solid but one that I can modify SNR and DNS settings? I'm in the UK by the way.

 

[Grisu]

no possibility right now, but Merlin wrote maybe soon he will implement DDNS in double-NAT, so probably you need Asus in router-mode too to have it run.
In router-mode you will see it in WAN-settings but not supported with private IP you get from modemrouter with recent firmwares.

Use DDNS from modem would be best option for now.

 

[RMerlin]

Might be possible to do it through manual scripting with my firmware, however I'd wait for the next release first, because I am dropping the current DDNS client.

 

[Grisu]

than have a look here for workaround: https://www.snbforums.com/threads/double-nat-custom-ddns-script.34431/page-3#post-428034

 

[sfx2000]

Might be possible to do it through manual scripting with my firmware, however I'd wait for the next release first, because I am dropping the current DDNS client.

I know a lot of folks are looking for double-NAT on IPv4, esp. in these days of Carrier Grade NAT - what's going on with IPv6 there?

(i'm not asking for myself, there are solution, but for the general audience...)

 

[RMerlin]

I know a lot of folks are looking for double-NAT on IPv4, esp. in these days of Carrier Grade NAT - what's going on with IPv6 there?

Dunno what's going on from inadyn's end, but from my end nothing is gonna happen, as I don't have IPv6 support to test anything (and don't expect my ISP to for many years). I guess inadyn using the new External check might possibly work if the DDNS provider supports AAAA, and you happen to connect with them over IPv6. But personally I wouldn't hold my breath.

 

[sfx2000]

Dunno what's going on from inadyn's end, but from my end nothing is gonna happen, as I don't have IPv6 support to test anything (and don't expect my ISP to for many years). I guess inadyn using the new External check might possibly work if the DDNS provider supports AAAA, and you happen to connect with them over IPv6. But personally I wouldn't hold my breath.

Grrr... I agree - sooner or later though, DDNS and IPv6 has to work...

The incumbent broadband providers know what they're sitting on (big blocks of public IPv4 and the value there) and will be moving more towards CGNAT, which breaks IPv4 personal end-points....

Remind me - up in Montreal - you're either Shaw or Rogers right?

Either direct or upstream... anyways, check again, you might be getting IPv6 if your router asks for it. That being said, IPv6 to the premises is still a bit of a mess, so many purposely disable it - I know, I do, as CoxHSI hasn't been very consistent there...

 

[RMerlin]

Remind me - up in Montreal - you're either Shaw or Rogers right?

No, Montreal is either Vidéotron or Cogeco (in certain areas) for cable, Bell and a few others for DSL/FTTH. Many TPIA ISPs are available going through Bell/Vidéotron/Cogeco. I'm with a TPIA going through Vidéotron.

On the DSL front, TPIAs are able to provide IPv6 since they handle routing and DHCP. For cable however, DHCP is handled by the incumbent (using IP blocks provided by the TPIA), so IPv6 support has to be done by the incumbent first. Vidéotron's IPv6 plans are quite vague. They had a poorly known 6rd offering for a few years, which was discontinued a year or two ago as they are gearing up for native, with no ETA. Right now they are finalizing network upgrades which are going, among other things, allow them to fully offer DOCSIS 3.1 probably starting next year. For now they use an hybrid 3.0/3.1 to be able to offer up to 960 Mbps downstream but 50 Mbps upstream.

Rogers (in Ontario) started IPv6 deployment recently.

 

[john9527]

I know, I do, as CoxHSI hasn't been very consistent there...

I see you keep saying this.....but Cox IPv6 has been rock solid for me for a long time.

 

[sfx2000]

I see you keep saying this.....but Cox IPv6 has been rock solid for me for a long time.

You apparently don't run BSD then...

 

[john9527]

You apparently don't run BSD then...

Haven't had any problems with OPNsense (FreeBSD)......taking a /60 prefix length...

 

[sfx2000]

Haven't had any problems with OPNsense (FreeBSD)......taking a /60 prefix length...

Cox has a big network - I'm still running into issues with v6 in my market with DHCP-PD with pfSense, which is a problem with FreeBSD (and NetBSD as well, for those running Airports 11n/11ac devices). It's not a problem specifically with BSD, it's how they're assigning and updating IPv6 here, and it's a known issue, and Cox doesn't care to fix it.

Had a good casual conversation about this with ka9q back in june...