ChrisJenkins
Up to speed
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: IPv6 support on Virgin media
tjw-ie wrote: If Virgin Ireland don't support IPv6 officially then they shouldn't provide a routable prefix! Most things will default to ipv6 if it's available. Mostly, in a very naive way, ipv6 appears to work. But I do egress filtering as well as ingress filtering, I run a proxy server etc, and it looks like the only way I'm going to get IPv6 to work for me is to use NAT66 which is "really not nice!" If it seems to partially work, and Virgin say that IPv6 is supported on your connection (have they said that?), then you could try and take this up with their support (but, well, good luck with that...). If they haven't explicitly stated that it is available / working then, like in some places in the UK, the presence of RAs etc. sadly means nothing. If I were you I would start by clarifying if it is available / supported (assuming you can find anyone at VM who even knows want IPv6 is...).3.4KViews0likes0CommentsRe: IPv6 support on Virgin media
ksim wrote: How do you solve issues with geolocation and tunnel? most ipv6 enabled websites sent me to the lake in the US 😞 I mean a lot of websites redirect me to the US version instead of the UK For those services that I care about I contact their support and explain the problem. Usually then they direct me to their IP geolocation provider and I submit a correction. There are not a huge number of those services so in most cases now all of my IPv6 global prefixes geo-locate to the UK (London).3.4KViews0likes0CommentsRe: IPv6 support on Virgin media
AFAIK, Virgin have not officially deployed IPv6 anywhere, including Ireland (I might be wrong about Ireland). Here in the UK in some areas you can see some RAs etc. if you go looking but it doesn't really work. The good news is that if you have one of the more recent hubs than a suitable tunnel (such as Hurricane Electric TunnelBroker) works just fine and achieves near native speeds. I have the tunnel configured on my router so as far as my home network goes it behaves just like native IPv6. I also get a /64 and a /48 as well and they work as expected.3.5KViews0likes10CommentsRe: IPv6 support on Virgin media
adhawkins wrote: Got my pre-order in with Giganet for FTTP with City Fibre. Static IPv4 and fully working IPv6 at 900 MBits/sec symmetric (for £41 a month). Just got to wait for them to finish the laying of the infrastructure so I can sort out an install date. Andy When CityFibre come to my area (it is' scheduled' apparently) I will certainly look at them. if they can provide a service at a suitable price point and do it without needing to dig up my front garden/drive then it may well be a no-brainer.2.3KViews0likes32CommentsRe: IPv6 support on Virgin media
IllLustration wrote: ChrisJenkins wrote: IllLustration wrote: Well, to be completely fair, it's only 28 pages if you use the maximum page size ... Until they deploy and assuming you can't go elsewhere without going back to the dark ages of speed, your best option really is to think of VM as mere connectivity, and tunnel IPv6 traffic over IPv4. If you tunnel all your traffic, you can get back a static IPv4 address as well, and keep mass surveillance at bay to boot. As long as you have one of the latest VM routers (Hitron Chita or SuperHub 4) then tunnelling IPv6 via, say, HE TunnelBroker achieves nearly native speed. Not sure how you would tunnel your IPv4 though, or what the overhead of that might be. Do you mean use a VPN? I tried that a while back but (a) the (IPv4) slowdown was way too much and (b) tunnelling IPv6 via a VPN endpoint isn't very reliable. I'm happy to use native IPv4 (with a dynamic address that is essentially static) and tunnelling IPv6 via HE until such times as VM offer it natively (maybe in 20+ years perhaps!). Actually, what I had in mind was a VPS, in my case specifically a Linode to terminate SMTP traffic (that's something you just can't do on VM because all their IP space in some DUHL or other), but this could be used to reach other sites when necessary. It's true that I generally prefer to have as direct a route as possible though, especially to CDNs. I guess what I mean specifically is that on VM you're still basically at the level of residential client-only IPv4 service and it's best to think of it like that. Establish outbound connections only if possible, don't rely on inbound traffic unless you have a dynamic DNS on it and are prepared for it to become unavailable or to (even temporarily) resolve to someone else, and tunnel any traffic that needs a "real" IP address on a permanent basis, and IPv6. It also means you can e.g. use cell service for failover. With these "mesh" VPNs or even Cloudflare Zero Trust it's now quite plausible to get access to your network services wherever they're located, even from behind a CGN. The only TCP port I expose on my address is SMTP, as a primary MX for my email. The HE tunnel is very good, and I'm fortunate to still have the permission to enable SMTP on my tunnels because it's an older account, but moving from A&A to VM really does emphasise what having a single "ultrafast" ISP in the area really means for discerning folk such as we. And yes, I'm aware that this reply is, um, a teeny bit late. 🙂 I run my own mail server, and so I have SMTP in/out to my VM IPv4 address and my HE IPv6 address, no problem. It is very rare for me not to receive mail as I should, and for sending I use a reputable outbound relay service, for a small fee, just to ensure trouble free operation. Of course, I do have SPF, DMARC and DKIM configured as well. Although my IPv4 public address is dynamic, it changes very rarely and I have suitable DynDNS setup to update my public DNS provider (and the HE tunnel endpoint) within a few minutes at most. So for me at least the (kind of) dynamic nature of the IPv4 address has never caused me any real issues.2.3KViews1like1CommentRe: IPv6 support on Virgin media
fyonn wrote: IllLustration wrote: Well, to be completely fair, it's only 28 pages if you use the maximum page size ... Until they deploy and assuming you can't go elsewhere without going back to the dark ages of speed, your best option really is to think of VM as mere connectivity, and tunnel IPv6 traffic over IPv4. If you tunnel all your traffic, you can get back a static IPv4 address as well, and keep mass surveillance at bay to boot. who does one tunnel to? are there choices? can I have the tunnel configured (easily) through my UDM? There are several (free) Ipv6 tunnel brokers. One of the most popular is HE (https://tunnelbroker.net) and there is also https://www.tunnelbroker.ch and others. I'm not sure what a UDM is? I have the tunnel configured in my NetGate Security Gateway which handles everything and makes it behave exactly like a native connection for all my home networks.2.7KViews2likes4CommentsRe: IPv6 support on Virgin media
IllLustration wrote: Well, to be completely fair, it's only 28 pages if you use the maximum page size ... Until they deploy and assuming you can't go elsewhere without going back to the dark ages of speed, your best option really is to think of VM as mere connectivity, and tunnel IPv6 traffic over IPv4. If you tunnel all your traffic, you can get back a static IPv4 address as well, and keep mass surveillance at bay to boot. As long as you have one of the latest VM routers (Hitron Chita or SuperHub 4) then tunnelling IPv6 via, say, HE TunnelBroker achieves nearly native speed. Not sure how you would tunnel your IPv4 though, or what the overhead of that might be. Do you mean use a VPN? I tried that a while back but (a) the (IPv4) slowdown was way too much and (b) tunnelling IPv6 via a VPN endpoint isn't very reliable. I'm happy to use native IPv4 (with a dynamic address that is essentially static) and tunnelling IPv6 via HE until such times as VM offer it natively (maybe in 20+ years perhaps!).2.7KViews2likes3CommentsRe: IPv6 support on Virgin media
The issue isn't really the dynamic nature of the address itself but rather the potential changing, more or less frequently, of the delegated prefix. For example, with my HE tunnel I get a global /64 prefix of 2001:xxxx:yyyy:aaaa so all of the IPv6 addresses used in my home network have to start with this prefix if they want to be able to access the Internet. Also, since I primarily use Ipv6 at home, all of my 'servers' (of which I have several) must be assigned static (i.e. well known) addresses within this prefix range. I also like to assign, via DHCP[6] reservations, static addresses to all of my 'client' systems (this includes phones, tablets, laptops and even some smart home devices). I also maintain my own (internal) DNS servers to provide name <-> address resolution for the 100+ devices on my home network. So all of those IPv6 addresses, including the prefix, have to be defined there too. If HE were to change the delegated IPv6 prefix to something else, say 2001:zzzz:ffff:qqqq, then I would have to (a) reconfigure all my 'servers' with the new IPv6 addresses, (b) reconfigure my DHCPv6 server with a new prefix, (c) modify every DHCPv6 reservation with the new prefix/address, (d) modify all of my DNS forward and reverse zones (around 10) accordingly. That's a good 12+ hours of work and during that period IPv6 essentially does not work for me anymore. So dynamic addresses are fine and normal/expected. Regularly changing delegated prefixes are also fine for simple setups where you are just using IPv6 to access the Internet and don't really care what the prefix/address is. If you do care then you absolutely need a fixed prefix that never changes otherwise it is unworkable. Many home setups fall into the 'don't care' category but equally many do not. I am currently on VM Business, so I really hope that if they ever do deploy IPv6 that I have the option to pay for a fixed prefix otherwise I will have to change ISP (and currently in my area there really isn't a viable alternative).