Sponsored Links

IPv4 and IPv6 support

bon

ULTIMATE Member
Toob supports IPv4 but also run dual-stack IPv6.

IPv4:
* Runs on CGNAT, which means you'll be assigned a non-routable 100.x.x.x WAN IPv4 address. For most people this isn't an issue, however the biggest side effect of CGNAT is that you're unable to use port forwarding rules on your firewall for inbound access. Before Toob introduced CGNAT you would be assigned a dynamic (but routable) WAN IP and because of this I used a dynamic hostname service for port forwarding/VPN access to my home firewall. However now I pay Toob an extra £8/month for a routable fixed IP which basically just gives me back what I had before. All in all it now costs me £33/month for 900/900 internet (usually £25/mo) which I'm still very much happy with.

IPv6:
* Toob will delegate to you a /56 prefix which means you can have up to 255 /64 LAN subnets. For most people this isn't important but if you plan on having VLANs / segregating your network this can come in useful.

* The IPv6 WAN address *seems* to be static (I've been monitoring this on a friends Toob connection where they don't pay for the static IP option - the IPv4 address has changed a few times over the year but the IPv6 WAN hasn't). If anyone can offer any clarification on this it would be appreciated.

* The Toob -supplied Sagemcom router appears to suffer from an issue (purely anecdotal - I've not had clarification on this) where it'll dish out IPv6 addresses to clients but after some time they stop working. Which I've found means your mobile phone apps appear to take a long time to load/get a connection as they'll be trying to establish a connection on the IPv6 stack that's been handed to the phone but are unable to, before eventually failing back to IPv4. Rebooting the Sagemcom often resolves the issue. I now use an Opnsense firewall which runs faultlessly with IPv6.
 
Good information regarding this, I was planning to get a static ip with them anyway, as heard they did cgnat ips, as I host games with friends time to time.
 
That's another good point actually. As Toob use IPv6 and so does Xbox Live (apparently) I had assumed strict NAT wouldn't be an issue, but it remained strict until I had my static IP assigned a day later and set up the appropriate port forwarding rule (3074) on the firewall.

My Xbox is assigned an IPv6 address but seemingly still needs an open IPv4 - whether that be for certain games or not I'm not sure.
 
Sponsored Links
Given limited literature on this, this thread seems closest.

Have had Toob for sometime. Very recently, appear to be getting issue with e.g. Twitter images not loading on mobile devices. This is most certainly a IPv6 issue failing to resolve and not falling back promptly to Ipv4.

This link shows fragmentation of the packets and the issue: http://icmpcheckv6.popcount.org/

Disabling ipv6 resolves the issue.... Or reducing Wan Mtu to 1412 vs 1500 (though this seems to the stop apps on Sky Q loading).

I have an Asus router... And rebooting does not resolve (so doesn't appear to be the issue noted at start of this thread)....alongside it has been working fine for more than a year.

Anyone else experiencing? I presume this is a Toob side IPv6 server configuration issue that only they can resolve....?
 
Given limited literature on this, this thread seems closest.

Have had Toob for sometime. Very recently, appear to be getting issue with e.g. Twitter images not loading on mobile devices. This is most certainly a IPv6 issue failing to resolve and not falling back promptly to Ipv4.

This link shows fragmentation of the packets and the issue: http://icmpcheckv6.popcount.org/

Disabling ipv6 resolves the issue.... Or reducing Wan Mtu to 1412 vs 1500 (though this seems to the stop apps on Sky Q loading).

I have an Asus router... And rebooting does not resolve (so doesn't appear to be the issue noted at start of this thread)....alongside it has been working fine for more than a year.

Anyone else experiencing? I presume this is a Toob side IPv6 server configuration issue that only they can resolve....?
Twitter has never had or currently has an AAAA record

Bash:
xyz@pluto /u/h/zyz> uname -a
FreeBSD pluto 13.2-RELEASE-p2 FreeBSD 13.2-RELEASE-p2 GENERIC amd64

xyz@pluto /u/h/xyz> ping -c 3 twitter.com
PING twitter.com (104.244.42.129): 56 data bytes
64 bytes from 104.244.42.129: icmp_seq=0 ttl=59 time=42.364 ms
64 bytes from 104.244.42.129: icmp_seq=1 ttl=59 time=44.522 ms
64 bytes from 104.244.42.129: icmp_seq=2 ttl=59 time=43.372 ms

--- twitter.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 42.364/43.419/44.522/0.881 ms

xyz@pluto /u/h/xyz> ping -c 3 x.com
PING6(56=40+8+8 bytes) 2001:8bd:abcd:8888:5468:6e0e:f0b7:2a5b --> 2606:4700:4400::6812:250e
16 bytes from 2606:4700:4400::6812:250e, icmp_seq=0 hlim=58 time=50.136 ms
16 bytes from 2606:4700:4400::6812:250e, icmp_seq=1 hlim=58 time=45.006 ms
16 bytes from 2606:4700:4400::6812:250e, icmp_seq=2 hlim=58 time=45.492 ms

--- x.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 45.006/46.878/50.136/2.312 ms

==> Browser or Twitter client will attempt to resolve the DNS record, if it resolves to an IPv4 address it will use the clients IPv4 stack to connect. With a browser IPv6 will take precedence but will fail (there is no AAAA record) and the client connects over IPv4.

The official Twitter client it doesn't even try IPv6 (as far as I can see on Apple iOS 16)

No idea how you conclude that Toob's "server" is at fault
 
Similar behaviour referenced here:


And many references to ipv6 issues if search Twitter images delay loading ipv6.

Twitter does not support IPv6 at all. It has no AAAA DNS record therefore no client is connecting via IPv6 protocol. ... basta!!

If an IPv6 DNS address lookup for Twitter fails (assuming the client has an active/valid IPv6 address) the client will not attempt to connect via IPv6 and will immediately fall back to IPv4. This is happens on !the client not at your router or on the network.

Check your client config, test with a browser, tryi ping4/ping6 the address..

Not relevant, this is talking about a site that does serve IPv6 content and then goes on to blame adblocking software (yeah right..). Twitter does not...

 
Sponsored Links
That's another good point actually. As Toob use IPv6 and so does Xbox Live (apparently) I had assumed strict NAT wouldn't be an issue, but it remained strict until I had my static IP assigned a day later and set up the appropriate port forwarding rule (3074) on the firewall.

My Xbox is assigned an IPv6 address but seemingly still needs an open IPv4 - whether that be for certain games or not I'm not sure.

Even though you might have a fully public IPv6 address doesn't automatically mean that people can connect to you. You still have a Firewall between you and the Internet, and the Firewall's job is to block all unsolicited incoming traffic. This means port 3074 on IPv6 is inaccessible for people outside your network unless you tell the firewall to allow incoming traffic. When you set up a NAT rule on IPv4 on most domestic routers, it does two things, adds the forwarding rule AND opens up the firewall. For IPv6, you don't need to worry about forwarding but you do still need to tell the firewall to allow traffic on the port. This might explain why you still had to add the IPv4 forwarding, because IPv6 was blocked because the Firewall didn't have the port open.

Hope that helps.
 
Hi Phil. What you've said makes sense and I did already understand that the firewall will still need a rule to allow inbound ipv6 connections - admittedly I hadn't considered that at the time though and will add this rule to see if it makes a difference :) In my head I just assumed there would be some mechanism that would make this happen automatically but I've realised I'm still thinking along the lines of 'NAT' and IPv4 hole punching which wouldn't apply to IPv6.

I appreciate your comment.
 
There's still a stateful firewall that by default in most broadband routers will allow everything out and block anything coming back unless it's part of an already established flow. I would guess the Xbox connectivity check is only looking at IPv4 when determining what to report as your NAT type.
 
Posting here as like Rham01 I've had some issues on mobile that I think may be IPv6 setup related. I wonder if it's the same problem bon mentions in his first post where the addresses dished out to clients stop working...

I'm using an Asus router (TUF-AX3000 v2 specifically).

I've only been with Toob since June, and using this router since June 20th.

On Aug 5th we found that the BBC News and BBC Weather apps stopped working on various Android devices. The apps would open but no content appeared - just the spinning circle as it tries to load. BBC website is fine.

I tried a reboot - no luck.

Switched back over to the Toob router - BBC apps work again.

Back to Asus - no luck. I decided to change the IPv6 DNS servers to Cloudfare and the BBC apps work again.

Then on 17th Aug the BBC apps stopped working again.

This time I decided to update the IPv4 DNS (in the WAN settings) to Cloudfare and it worked. Then I tried a whole bunch of other DNS setups (between Toob/Cloudfare on IPv4/IPv6 combos) as well as a firmware update, and the BBC apps went from working to not working and back again.

In that testing I noted my IPv6 Gateway address switched between 2 addresses, and more often than not (regardless of DNS settings) one worked with the apps, while the other didn't.

I also noted that when the apps failed, my pings to bbc.com (resolving as the ipv6 address) would also fail. As would the https://test-ipv6.com/ website (0/10 result). However ipv6.google.com worked (accessible and pingable)

For now I'm using the Cloudfare IPv4 DNS 1.1.1.1 and Toob's auto IPv6 DNS and that's got things working again, but I don't think it'll be a permanent solution. There's definitely something up but testing is difficult as it seems random.
 
  • Like
Reactions: bon
Sponsored Links
This morning I went back to the default Toob DNS server and crucially (maybe) the WAN IPv6 Gateway stayed the same and everything is working. It does seem like one of the two WAN IPv6 Gateways they assign me is a little broken.
 
Posting here as like Rham01 I've had some issues on mobile that I think may be IPv6 setup related. I wonder if it's the same problem bon mentions in his first post where the addresses dished out to clients stop working...

I'm using an Asus router (TUF-AX3000 v2 specifically).

I've only been with Toob since June, and using this router since June 20th.

On Aug 5th we found that the BBC News and BBC Weather apps stopped working on various Android devices. The apps would open but no content appeared - just the spinning circle as it tries to load. BBC website is fine.

I tried a reboot - no luck.

Switched back over to the Toob router - BBC apps work again.

Back to Asus - no luck. I decided to change the IPv6 DNS servers to Cloudfare and the BBC apps work again.

Then on 17th Aug the BBC apps stopped working again.

This time I decided to update the IPv4 DNS (in the WAN settings) to Cloudfare and it worked. Then I tried a whole bunch of other DNS setups (between Toob/Cloudfare on IPv4/IPv6 combos) as well as a firmware update, and the BBC apps went from working to not working and back again.

In that testing I noted my IPv6 Gateway address switched between 2 addresses, and more often than not (regardless of DNS settings) one worked with the apps, while the other didn't.

I also noted that when the apps failed, my pings to bbc.com (resolving as the ipv6 address) would also fail. As would the https://test-ipv6.com/ website (0/10 result). However ipv6.google.com worked (accessible and pingable)

For now I'm using the Cloudfare IPv4 DNS 1.1.1.1 and Toob's auto IPv6 DNS and that's got things working again, but I don't think it'll be a permanent solution. There's definitely something up but testing is difficult as it seems random.
I am having the exact same issue/symptoms specifically with BBC News/Weather apps on Android that started this month (issues on other apps too, I suspect it's those that use ipv6 but the problem is immediately apparent on the BBC apps). I've made loads of changes to my Opnsense router as the issue seemed to be sporadic but hadn't noticed the gateway address change. Something I'll keep an eye on!
 
That's another good point actually. As Toob use IPv6 and so does Xbox Live (apparently) I had assumed strict NAT wouldn't be an issue, but it remained strict until I had my static IP assigned a day later and set up the appropriate port forwarding rule (3074) on the firewall.

My Xbox is assigned an IPv6 address but seemingly still needs an open IPv4 - whether that be for certain games or not I'm not sure.
Hi did hou get your xbox working paid for the statc ip
 
Thanks for the helpful information @bon. Saved me much frustration when trying to get a VPN server setup at home. For others who might be trying to do the same, you've got several options:
  1. Pay £8 a month for a static IP which is then routable from the internet and run your own flavour of VPN on your router (I use Wireguard on my OpenWRT router)
  2. Go crazy and setup a VPN server on a VPS and connect to that from your router (paying the monthly fee for the VPS)
  3. Use cloudflare tunnels to access your VPN server on your router (didn't want to do that as it requires updating the cloudflared software regularly, and there are no packages for OpenWRT)
  4. Use IPv6 to route to your router from the internet (didn't work when using my mobile data connection)
  5. Just install Tailscale on _any_ machine in your LAN and then use it as an exit node - my eventual solution
 
Top
Cheap BIG ISPs for 100Mbps+
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Vodafone UK ISP Logo
Vodafone £24.00 - 26.00
150Mbps
Gift: None
NOW UK ISP Logo
NOW £24.00
100Mbps
Gift: None
Plusnet UK ISP Logo
Plusnet £25.99
145Mbps
Gift: £50 Reward Card
Large Availability | View All
Cheapest ISPs for 100Mbps+
Gigaclear UK ISP Logo
Gigaclear £17.00
200Mbps
Gift: None
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Hey! Broadband UK ISP Logo
150Mbps
Gift: None
Youfibre UK ISP Logo
Youfibre £23.99
150Mbps
Gift: None
Large Availability | View All
Sponsored Links
The Top 15 Category Tags
  1. FTTP (6024)
  2. BT (3639)
  3. Politics (2720)
  4. Business (2439)
  5. Openreach (2405)
  6. Building Digital UK (2330)
  7. Mobile Broadband (2144)
  8. FTTC (2083)
  9. Statistics (1899)
  10. 4G (1814)
  11. Virgin Media (1763)
  12. Ofcom Regulation (1582)
  13. Fibre Optic (1467)
  14. Wireless Internet (1462)
  15. 5G (1405)
Sponsored

Copyright © 1999 to Present - ISPreview.co.uk - All Rights Reserved - Terms  ,  Privacy and Cookie Policy  ,  Links  ,  Website Rules