31–40 of 65 posts
Earlier quoted context omitted.
Has the price per elastic IP ever gone up though on AWS? I don't think so, but you'd expect price to rise over time as less addresses become available.
EIPs only cost money if they're unattached. Otherwise they're free.
In Seattle and surrounding areas, Comcast is more or less the only game in town (with Centurylink a distant, distant second) if you're not in one of a dozen high-rise apartment buildings. For all their marketing around 'extensive IPv6 rollout', I've found their deployment to be hideously broken and their support staff deeply ignorant. Been here 3 years, moved once, and it's just terrible. My latest foray into trying…
Outside the Seattle area, upgrades happened much earlier so its a mix of VDSL2 down in Kent and surrounding areas, and ADSL to the north of Seattle proper (they got no upgrade munnies :c). Seattle has seen a ton of Capex over the past few years, and from what Clink employees tell me they are severely cutting back in Seattle this quarter, so as to wire the South end with VDSL2 and other cities with fiber. Portland also has near 100% fiber coverage by the way.
The crux of why Centurylink doesn't have a ton of customers on fiber comes down to a godawful prequal database, that they take offline starting anywhere from 3pm to 7pm and keep offline till well into the next morning. Techs will actually get orders put in for DSL, and when they go out to install it, see fiber on the pole and go "WTF?", but getting the prequal database amendment is near impossible.
Wrt static IPs on Comcast or worse yet Wave, just don't bother. A dynamic DNS entry will work just as well, while avoiding all the crazy stand on head networking antics both cable providers have to do to give you a static IP. Try portscanning the internal netblock your static IP is provisioned to, last time I did I found a (poorly protected) headend on a 10.x.x.x address.
1 - https://www.seattle.gov/Documents/Departments/SeattleIT/cabl...
Earlier quoted context omitted.
Googling shows that they have some deployments but at least as far as I can tell from my network settings (and http://ipv6-test.com ) I do not have an IPv6 address. Perhaps they never got around to updating my apartment building.
My ISP (Spectrum) only enables IPv6 to a subset of their "supported" cable modem list. In other words, if you don't have the right cable modem, you may get IPv4 but don't get IPv6. It's possible your provider may do the same.
Earlier quoted context omitted.
Googling shows that they have some deployments but at least as far as I can tell from my network settings (and http://ipv6-test.com ) I do not have an IPv6 address. Perhaps they never got around to updating my apartment building.
I think some buildings are actually outright cg-natted and the only IP you actually get is v6...
In Seattle and surrounding areas, Comcast is more or less the only game in town (with Centurylink a distant, distant second) if you're not in one of a dozen high-rise apartment buildings. For all their marketing around 'extensive IPv6 rollout', I've found their deployment to be hideously broken and their support staff deeply ignorant. Been here 3 years, moved once, and it's just terrible. My latest foray into trying…
In Seattle there is also CondoInternet - a fiber company in many of the newer development. But, I've seen an entire building on a NAT private network. It's included in your HOA.
My comment above gives a bunch more detail if you wanna give it a look.
Don't forget you can always use IPv6 as there are gates to 6th internet over 4th internet. After all the words Inter Net mean this technology can work over and between any network, be it Ethernet, Wi-Fi, Token Ring or whatever. And of course it can work over IP of another version.
Earlier quoted context omitted.
Google fo IPv6 tunnel brokers -often free services. I don't know which of them is better, may depend on where you are located.
he.net provides a good one that we used for many years before getting real IPv6 space though our ISP. https://tunnelbroker.net/
Also used SixXS but the aiccu+AYIYA/6in4 requirement isn't ideal when you have some network gear that supports 6to4 tunnelling natively.
I keep wondering what will happen on AWS or Google when available public v4 IPs run out/low... Start charging $15 per address?
They already charge on AWS. The cost of 1 IP is built-in to the hourly cost, with extras and those attached to stopped instances charged explicitly.
If that's the case, then it may make sense to lock the instance price down, and start charging for in-use v4 IPs, not just unused allocated ones.
Let's say the next block of 1 Million IPs that AWS wants to buy from say, GE fails to go through, and AWS is looking at a pool of 500K IPs starting to shrink at the rate of 30k per day. The only way to ensure they don't run out would be to separate the price out and jack up the price considerably so they don't run out.
What I'm saying is that at some point, WHEN the number of IPs that people want outpaces the number AWS (or Google or other cloud provider) can obtain from other companies, they will be forced to change something.
What would be interesting would be to see AWS etc, to try to get their customers to migrate off IPv4 for administrative and back-office services since there really isn't a strong reason to have VPNs and SSH or RDP sessions backed by a v4 address.
Don't forget you can always use IPv6 as there are gates to 6th internet over 4th internet. After all the words Inter Net mean this technology can work over and between any network, be it Ethernet, Wi-Fi, Token Ring or whatever. And of course it can work over IP of another version.
One particular mechanism is 6to4: https://en.wikipedia.org/wiki/6to4 . It works through anycast address 192.88.99.1, so you don't need any provider-specific setup or subscription.