4 ms·

How did you get your ISP to give you a static IP block or prefix? I can get an IPv4 block, but despite the yelling of the IPv6 fanatics regarding how many IPv6

How did you get your ISP to give you a static IP block or prefix? I can get an IPv4 block, but despite the yelling of the IPv6 fanatics regarding how many IPv6 addresses are available, I can't get anyone to allocate me even 20 or so (much less a prefix!). Is there something in the spec that makes this hard to do. It's been 20 years.

naranha 5y ago
Luckily here in France there are 8 static /64 prefixes included in a standard DSL or Fiber offering. Just luck i guess...
zamadatix 5y ago
You don't need a static address or block to NAT and for the internal side there is private space just like v4.
- slownews45 5y ago
  I am asking, under IPv4 I can trivially get a static block of IPs. I can then trivially * put some devices on a VLAN (ie, a VOIP phone) and it will have a public IP, globally routable. This works well in my experience, latency is super annoying on VoIP and for some reason behind a NAT sometimes it seems to route media through a third party server! For a small business you can put a PBX on the VLAN and folks can remote register to it trivially (ie, phone.companyZ.com) - with COVID this is great. You can VPN terminate more easily with a static ip block. At home I can do a game server on the static IP block or I can host some of the simultaneous music composition stuff (trivially). My question is simple - how do I get a static IPv6 block so I can do all this if I want to on IPv6. I get IPv4 is outdated, but how do I do some of this stuff in the fancy IPv6? You are telling me IPv6 means I don't need any public static IPs and can use some private IPv6 space (10.x was already plenty for that for me in ipv4) with a dynamic public IPv6. Fine, how does this work. Seriously, what VPN endpoint am I configuring? How does my VOIP / SIP play with this? Do I need to go back to poking weird holes in a NAT? My OWN experience was this all doesn't play well together. Firewalls seem not to play well with dynamic prefixes - and that's just the start. Devices pick up the wrong IP's internally (SIP etc). In short - 20 years into this, when I try to do something simple -> stick my VoIP phone on a static public IP and VLAN -> its a total pain. At a small biz, if I try and put a PBX on a static public IPv6 - it's a total pain (and BTW - the SIP IPv6 support in most hardware and softphones is terrible). This should be the winning use case. Phone calls / person to person audio would benefit TREMENDOUSLY from direct peering connections without any NAT! But despite an insane number if IPv6 addresses at least in the US they won't assign you a block of even 20.
  - zamadatix 5y ago
    It's a great question for the thread but probably in response to the wrong comment chain. But since we're here: it'll depend on your provider, just like v4. Some won't offer it at all, some will charge, some will force you to buy the "business" connection instead, some will use a static WAN and route the rest to you, some will use a dynamic WAN and route the rest to you, some will require their modem be used (and some will even 802.1x auth it), some will let you directly put it to your own gear. The story isn't any different, there is nothing about IPv6 that changes this dynamic other than you have the additional option to use PD. What may be different is what your ISP requires you to do/purchase - by the sounds of it likely trying to push you to a business account which is a revenue tactic not a technology limitation. As far as NAT with a dynamic IP to private v4 it works the same as NAT with an IPv4 connection with RFC 1918 space internally. As for your performance issues with NAT you shouldn't see any latency with NAT on a network device, if you're using software routing on a Linux box or something try a standard hardware network device for the edge NAT instead as the data path for hardware devices is the exact same for NAT in those as it is for normal routing, in fact normal routing is normally just implemented a special case of NAT where the inside and outside addresses of the NAT are set to the same value. If you're currently using such a device for your edge NAT and experiencing problems with it either the device is broken or something is misconfigured as like I said everything is always "NATed" through such a device so it doesn't make any sense it'd have higher latency with certain internal IP values. But seriously for home use without NAT look at PD, for business use with static routing and statically configured devices behind that routing look at what your ISP wants to sell you and see if you can call them on their crap but to be honest if you're running VOIP the business service is probably worth it anyways as you can get them to honor voice QOS through the oversubscribed local node into their backbone. If you go this route the IP space itself is the same as v4, you can either get it from your ISP or you can get it assigned to your LLC or whatever via your local RIR - literally anyone can get a /48 block assigned to them this way, maintenance fees for the allocation are the same as v4 but the RIRs actually have the space itself for free unlike v4 where you have to buy addresses and pay the maintenance fee. You can tunnel if you want but I really wouldn't recommend it for VOIP. The same options you have for IPv4 VPNs are available for IPv6 and the setup is no different beyond the address type. There is also the option of teredo or 6rd but again I wouldn't really bother with them at this point in the game, they were intended for deploying v6 prior to its availability in ISPs not for this use case. But the general idea is there is nothing about IPv6 that changes the way static addresses, static routing, or static allocation works beyond the size of the address field. That doesn't mean your ISP is choosing to give them to you at a reasonable price but it's not because of IPv6.
lokedhs 5y ago
My old ISP have me a /64, using 6rd. Because of this, I changed ISP's (one of the main reasons I did so was because of the poor IPv6 support) and the new one gave me a /48. This was several years ago though, and hopefully even my old ISP can do proper IPv6 by now. So apparently it depends very much on the ISP. Some are doing a better job than others.

naranha 5y ago

Luckily here in France there are 8 static /64 prefixes included in a standard DSL or Fiber offering. Just luck i guess...

zamadatix 5y ago

You don't need a static address or block to NAT and for the internal side there is private space just like v4.

slownews45 5y ago
I am asking, under IPv4 I can trivially get a static block of IPs. I can then trivially * put some devices on a VLAN (ie, a VOIP phone) and it will have a public IP, globally routable. This works well in my experience, latency is super annoying on VoIP and for some reason behind a NAT sometimes it seems to route media through a third party server! For a small business you can put a PBX on the VLAN and folks can remote register to it trivially (ie, phone.companyZ.com) - with COVID this is great. You can VPN terminate more easily with a static ip block. At home I can do a game server on the static IP block or I can host some of the simultaneous music composition stuff (trivially). My question is simple - how do I get a static IPv6 block so I can do all this if I want to on IPv6. I get IPv4 is outdated, but how do I do some of this stuff in the fancy IPv6? You are telling me IPv6 means I don't need any public static IPs and can use some private IPv6 space (10.x was already plenty for that for me in ipv4) with a dynamic public IPv6. Fine, how does this work. Seriously, what VPN endpoint am I configuring? How does my VOIP / SIP play with this? Do I need to go back to poking weird holes in a NAT? My OWN experience was this all doesn't play well together. Firewalls seem not to play well with dynamic prefixes - and that's just the start. Devices pick up the wrong IP's internally (SIP etc). In short - 20 years into this, when I try to do something simple -> stick my VoIP phone on a static public IP and VLAN -> its a total pain. At a small biz, if I try and put a PBX on a static public IPv6 - it's a total pain (and BTW - the SIP IPv6 support in most hardware and softphones is terrible). This should be the winning use case. Phone calls / person to person audio would benefit TREMENDOUSLY from direct peering connections without any NAT! But despite an insane number if IPv6 addresses at least in the US they won't assign you a block of even 20.
- zamadatix 5y ago
  It's a great question for the thread but probably in response to the wrong comment chain. But since we're here: it'll depend on your provider, just like v4. Some won't offer it at all, some will charge, some will force you to buy the "business" connection instead, some will use a static WAN and route the rest to you, some will use a dynamic WAN and route the rest to you, some will require their modem be used (and some will even 802.1x auth it), some will let you directly put it to your own gear. The story isn't any different, there is nothing about IPv6 that changes this dynamic other than you have the additional option to use PD. What may be different is what your ISP requires you to do/purchase - by the sounds of it likely trying to push you to a business account which is a revenue tactic not a technology limitation. As far as NAT with a dynamic IP to private v4 it works the same as NAT with an IPv4 connection with RFC 1918 space internally. As for your performance issues with NAT you shouldn't see any latency with NAT on a network device, if you're using software routing on a Linux box or something try a standard hardware network device for the edge NAT instead as the data path for hardware devices is the exact same for NAT in those as it is for normal routing, in fact normal routing is normally just implemented a special case of NAT where the inside and outside addresses of the NAT are set to the same value. If you're currently using such a device for your edge NAT and experiencing problems with it either the device is broken or something is misconfigured as like I said everything is always "NATed" through such a device so it doesn't make any sense it'd have higher latency with certain internal IP values. But seriously for home use without NAT look at PD, for business use with static routing and statically configured devices behind that routing look at what your ISP wants to sell you and see if you can call them on their crap but to be honest if you're running VOIP the business service is probably worth it anyways as you can get them to honor voice QOS through the oversubscribed local node into their backbone. If you go this route the IP space itself is the same as v4, you can either get it from your ISP or you can get it assigned to your LLC or whatever via your local RIR - literally anyone can get a /48 block assigned to them this way, maintenance fees for the allocation are the same as v4 but the RIRs actually have the space itself for free unlike v4 where you have to buy addresses and pay the maintenance fee. You can tunnel if you want but I really wouldn't recommend it for VOIP. The same options you have for IPv4 VPNs are available for IPv6 and the setup is no different beyond the address type. There is also the option of teredo or 6rd but again I wouldn't really bother with them at this point in the game, they were intended for deploying v6 prior to its availability in ISPs not for this use case. But the general idea is there is nothing about IPv6 that changes the way static addresses, static routing, or static allocation works beyond the size of the address field. That doesn't mean your ISP is choosing to give them to you at a reasonable price but it's not because of IPv6.

lokedhs 5y ago

My old ISP have me a /64, using 6rd. Because of this, I changed ISP's (one of the main reasons I did so was because of the poor IPv6 support) and the new one gave me a /48. This was several years ago though, and hopefully even my old ISP can do proper IPv6 by now. So apparently it depends very much on the ISP. Some are doing a better job than others.