I run a Plex server amongst other things and considered configuring it to use IPv6 but then read a lot of clients (Roku as an example) don't support IPv6 and neither do some of the larger ISP's (Vrgin Media). So I'll probably be biting the bullet and paying the £8 for a 'static' or non-cgnatted IP to save the headache. At £33/month (£37 after 18 months) it's still not a bad price in fairness.

I had a little moan on FB and got this reply.

Hello

In order for port forwarding to work, you'll need a static IP address. Our customer care team will be happy to arrange this for you completely free of charge for your first 6 months (and then £8 per month thereafter).

Please feel free to give us a call on 0800 368 9458 and we'll set this up for you.

Kind regards,
Zoe

Fair play mate

Useful thread. I recently twigged that it was the CGNAT breaking all my stuff here. Quite annoying as when I started with the service it wasn't in place.

I phoned customer services to ask them to do something about it but they completely refused to accept that introducing CGNAT (with no notice) constituted a major change to the provided service.

I'm in the unenviable position now of having to pay £8 a month more to get back to the level of service that I had when I first signed up, and because of the long contract length don't even have an option to cancel.

It's a shame, as the service was really easy to recommend before they nerfed it.

Edited by putty_thing (Fri 18-Nov-22 19:22:24)

I would go down the complaint route with Toob and then escalate to ADR and state that the resolution to your problem would be a public IP for the same price you're paying now, but at the same time I'd look at https://tailscale.com/blog/introducing-tailscale-fun... which is a reverse proxy.

To update on this I've asked them to go ahead on the static IP so that I can have working Internet again. Strongly worded letter writing in progress.

All the usual stuff improved, but one strange thing: I've been troubleshooting slow Google assistant responses for months thinking it was the wireless or IPv6. As soon as the static IP* was enabled the response times went back to normal.

Rate limiting perhaps from the Google end? Either way not great and another strike against Toob's reasoning that CGNAT is only a problem because of my 'non-standard usage' rather than just generally bad.


* For future generations: this is provided via DHCP

Edited by putty_thing (Sun 27-Nov-22 18:17:31)

Looking into it some more, I was using Google public DNS and that may have been where the rate limiting* was coming in, causing the slowness: https://developers.google.com/speed/public-dns/docs/isp

* 1500 QPS per source IP per the document.

Edited by putty_thing (Sun 27-Nov-22 18:31:25)

Out of interest does anyone know what public IP range are Toob using for CGNAT at the moment, is it the one starting 145.40 or 45.13? Also how are they handling the WAN side of the link on a consumer conneciton? Is it using RFC1918 addresses or RFC 5737 shared address space (100.64.0.0/10)

I took them up on a static IP as soon as it was available as it was worth it to me so missed the great CGNAT debacle.

Edited by ionic (Mon 05-Dec-22 12:04:01)

In reply to a post by ionic:

Out of interest does anyone know what public IP range are Toob using for CGNAT at the moment, is it the one starting 145.40 or 45.13? Also how are they handling the WAN side of the link on a consumer conneciton? Is it using RFC1918 addresses or RFC 5737 shared address space (100.64.0.0/10)

From memory I saw a 145.40 address on the WAN interface while in the CGNAT pool.

Edited by putty_thing (Wed 07-Dec-22 11:42:55)

Family member signed up for Toob, pfsense is the planned firewall / router. Do we know what the assigned IPV6 delegated prefix needs to be set to on the WAN interface?