Hi João, This sounds familiar to me, but it was a while back so forgive me if I can't remember all the details.
If I remember correctly though, I encountered this whilst working for an ISP that did mainly CGNAT for their customers. They would take their CGNAT customers and NAT them through a pool of public IPs, which caused issues for customers with SkyQ boxes. Either of the following worked for them: - Giving the customer a static IPv4 address (interesting that you mention this doesn't seem to always work for your customers, but it could be you're seeing a different issue anyway!) - Ensuring that the CGNAT router always mapped connections from a given CGNAT address to the same public IP address, ensuring that multiple sessions appear from the same public IP. (The ISP ran MikroTik, so this was setting the CGNAT rule to use action=same) which is described on their wiki as: - same - gives a particular client the same source/destination IP address from supplied range for each connection. This is most frequently used for services that expect the same client address for multiple connections from the same client Is there something similar you can configure with your CGNAT rules? Kind regards, Ali Clubb On Fri, 4 Jun 2021 at 14:27, João Basto <[email protected]> wrote: > Good Morning, > > We have been experiencing customer issues frequently by SkyQ users with > issues downloading on-demand content. > Work-around's we have in place seem to be "hit and miss" as in they will > work for some users, but not for others. > The behaviour is that when a user attempts to download a on-demand content > in their SkyQ device the download gets interrupted mid-way and never > finishes the download. > > Work-around's we have seen work for some is change DNS settings on the Sky > equipment to override the one provided by our CPE (uses dnsmasq), this only > works sometimes > Another one is assigning the customer's CPE a static Public IPv4 Address > instead of the CGNAT Address we provide by default, but this also doesn't > always work. > From what we can tell this does not affect users with SkyQ Devices with > IPv6 support (where we have IPv6 coverage) > > Was wondering if anyone else has had similar experience with SkyQ users. > > Best Regards, > > > > > > > > > *João Basto Senior Network Architect [image: Airband Logo] T: 01905 958489 > M: 07950158402 E: [email protected] <[email protected]> W: > www.airband.co.uk Twitter:@UKairband <https://twitter.com/UKAirband> > [image: Challenge3000] <https://gofund.me/50a89df9> Company no. 07114545. > Registered in England and Wales. Airband Community Internet Ltd, Kirkham > House, John Comyn Drive, Worcester, WR3 7NS * >
