[AIS Fiber] IPv6 possible?

[AgentSmith]

The AIS fiber website now states that every connection gets a public IPv6 address (terms and conditions #5 at bottom of the page). I think by that they mean an IPv6 prefix so that every device behind the router gets its own fixed public address. Our router runs on DD-WRT which supports IPv6 fine (I've successfully tried it with a tunnel broker once) but it doesn't get a prefix from AIS automatically.

For testing purposes I hooked up a Windows laptop and set it up with its own PPPoE client. The fiber modem is in bridge mode effectively disabling its inbuilt router. The laptop gets a public IPv4 address just fine but there is no IPv6 prefix handed out by the ISP. I've already emailed AIS and they asked me for my phone number so they can hook me up with the right department. In the mean time, is anyone using IPv6 successfully?

[GinBoy2]

I didn't think any Thai ISP was using IPv6 yet. TOT certainly isn't.

I think they are all IPv6 ready, I do seem to recall reading a TOT presentation last year that said that. But being ready, and actually deploying, that's two different things, and this is the hub of effective deployment after all <coughs>

[muratremix]

1. The customer who subscribe PowerHome Package receive free Private IPv4 with DDNS and Public IPv6. Can use port forwarding and bridge mode.

Well, they mean you get public ipv6 address and a CGNAT ipv4 (not public, internal ip with 10.x.x.x ip) address. I guess their ipv4 depleted sometime ago.

They were doing this in ais airnet home package. Ais fibrenet was getting normal ipv4 like every other isp.

No public ipv4 == problem with port mapping in case if you use security camera or NAS behind your internet.

[AgentSmith]

You are right! Wished I had realized that sooner. I just spent a half hour trying to explain to the fiber helpdesk that I want to cancel the switch to the new promotion because I want to keep the public IPv4 address. They kept replying "not possible sir if you want to have IPv6." You can understand the frustration. Salvation came when I uttered the words I want to cancel IPv6 and keep IPv4.

That aside, it's pretty lame they don't offer dual stack to existing customers. I understand they're running out of IPv4 addresses and have to resort to CGNAT for new subscriptions but IPv6 is so extremely abundantly available they can easily hand out prefixes on all existing lines. Not in LOS.

It's also not very smart to pull away public IPv4 from existing customers. No way I will ever switch to a new package if that doesn't change and I won't recommend it to my friends either. Better to go with TOT fiber then.

Edited March 30, 2016 by AgentSmith

[muratremix]

Atleast they provide ipv6 which is a first in Thailand.

CGNAT is necessary as ipv4 almost depleted.

if they let you do port mapping, so you can access your camera etc, it is even better.

[AgentSmith]

Atleast they provide ipv6 which is a first in Thailand.

CGNAT is necessary as ipv4 almost depleted.

if they let you do port mapping, so you can access your camera etc, it is even better.

I still don't get though why they only offer it to new customers. I understand that ipv4 addresses are running out, especially in non-western countries. However if you have a public ipv4 address (dynamic or not) you'd need to be a fool to knowingly give it up and have it replaced with some ipv4 tunnel that might not even work properly with your existing router.

Of course I could call AIS again and ask if they'd be willing to give me a dual stack line, so native ipv4/ipv6. It's not as if ipv6 would cost them anything extra.

[zib]

Public ipv4+ipv6 is available on the powerpro package.
They do however do portmapping on the powerhome package also through their portal. Which basically means as long as the port isn't allocated to another customer you get.

I get a /64 ipv6 from them. If you need help setting it up in dd-wrt let me know. It's a bit tricky since it's pppoe.

[Matty83210]

Hello,

 

Can someone explain why I have to use https://www.thddns.net for PORT FORWARDING for my Foscam IP canera ?

 

Port forwarding is usually done on the router directly but AIS fiber is weird ?

 

Thank you for your help.

[graf]

On 9 August 2016 at 5:40 PM, Matty83210 said:

Hello,

 

Can someone explain why I have to use https://www.thddns.net for PORT FORWARDING for my Foscam IP canera ?

 

Port forwarding is usually done on the router directly but AIS fiber is weird ?

 

Thank you for your help.

 

They double NAT:

1. First there is NAT in your router and you get access to the 100.112.x.x network
2. Then there is NAT somewhere in that network and you get access to the internet.

You don't have access to their router, so they use that website for you to setup your mappings.

 

You can see that the IP assigned to your router is not the one appearing in the typical "whats my ip" site.

 

More info about what they're doing: https://en.wikipedia.org/wiki/Carrier-grade_NAT

Edited August 17, 2016 by graf

[mtls2005]

Not that it helps but you can "see" your public-facing IP address here: http://ip-lookup.net/  49.n.n.n

 

Your local-side IP address can be seen in the fiber router: 100.n.n.n

 

The free AIS/THDDNS service https://www.thddns.net/login

 

set-up guide is here: http://www.ais.co.th/fibre/pdf/THDDNS_register_manual_en.pdf

 

I haven't gone through the process yet.

 

[mtls2005]

I successfully set up a free AIS THDDNS account; it was a lot easier than I thought it would be.

 

You choose a domain name, which they map to the changing 49.x.x.x <--> 100.112.x.x. IP addresses. You can utilize up to ten (10) ports.

 

I haven't started using it yet.

[AgentSmith]

On ‎6‎/‎2‎/‎2016 at 0:27 AM, zib said:

Public ipv4+ipv6 is available on the powerpro package.
They do however do portmapping on the powerhome package also through their portal. Which basically means as long as the port isn't allocated to another customer you get.

I get a /64 ipv6 from them. If you need help setting it up in dd-wrt let me know. It's a bit tricky since it's pppoe.

Luckily I managed to cancel the package change earlier this year so we kept the public ipv4 address. I still don't really get why they don't give ipv6 to every customer. And /64 is a bit weird too. ISP's are supposed to give /48 as it makes it possible for end users to divide a network into /64 subnets. Still /64 is better than nothing. I'll just wait and see what happens over time. I might actually just try and see what happens when I enable IPv6. With a bit of luck it works anyway..

[AgentSmith]

Well I'll be damned.. I just enabled IPv6 in the router (DD-WRT) and it works! :D Even better, in build 29218 setting it up is super easy. I simply selected "DHCPv6 with prefix delegation" and now all devices on the network get a public IPv6 address, the router's IPv6 address as gateway and a link-local IPv6 address as well. Test-ipv6.com gives a score of 10/10 on my laptop.

 

"ping google.com" in command prompt uses Google's v6 address as well so that really confirms it.

 

 

I'm not sure but maybe this works because I use opendns ipv6 dns servers. Their addresses are:

 

2620:0:ccc::2

2620:0:ccd::2

Edited November 3, 2016 by AgentSmith

[SooKee]

Still trying to get my head round this as it seems somewhat confusing at the moment.  I use the Plex app which requires port forwarding to enable remote access.  The port forwarding needs to be done for the public facing IP address that the Plex app sees which is a 49.###.###.### address.   I'm still not certain if the DDNS cocktail of numbers that I'll need to set up are going to allow Plex to see and utilise a public IP address that it use for port forwarding.  However AIS do it, it simply won't work if there is a double NAT involved.

 

I've yet to give it a try but thus far I can't even get past the log in / confirm email address phase with AIS and THDDNS.  Every time I try to confirm the email I get 'Bad request' result and I can't even log in to the damn website currently.  Keep getting a 'User name or password invalid' even after trying multiple resets to the password.  Another brilliantly designed system that is more difficult that it should be to get to work.  Seem to spend more time here pi55ing about with trying to get simple things to work than ever!!!

 

Another thing I can't quite get my head round with the way AIS does this CGNAT thing.  I have several devices connected and when you look at the IP address reservation section it gives you only the option of addresses in the 192.1.###.### range.  However I had real fun and games yesterday setting stuff up (service only installed yesterday) because one device that was connected by CAT6 cable had an IP address starting 100?  I see that the WAN setting starts with a 100 address.  But how or why the router has allocated an IP address to a device using DHCP on a different subnet to other devices attached to the router (e.g. 100 vs 198) is confusing to say the least!!!!  Took several attempts by deleting network connections on the cat 6 connected device to finally get a new connection to pull the 192 address I'd reserved for it on the router.  Yet more stuff to read up on.