Are you ready for the IPcalypse?

IPcalypse?

  • It's like the 2000 fears... we will be fine! No biggy!

    Votes: 13 36.1%
  • This is a serious problem.

    Votes: 12 33.3%
  • I don't care. Somebody will figure it out.

    Votes: 7 19.4%
  • I just don't know what to make of it.

    Votes: 2 5.6%
  • Buy that static IP now!!!!!

    Votes: 2 5.6%

  • Total voters
    36
Hey Daffy,

Will be interesting, at the end of the day it will land up being Cisco's call.

If the usage of their Half-duplex VRF functionality is still quite prevelent amongst some of the more heavy-weight global telcos/ISPs, there may be enough pressure for them to update it to support IPv6.

Alternatively they could mandate the roadmap is to migrate to PPPoE Relay (over L2TP) for IPv6 support?

Its unfortunate that telcos/ISPs insist on using IPConnect. Its archaic and needlessly complex.
PPPoE Relay over L2TP VPDNs just makes so much more sense, given its transparency.
 
What I want to know is, with IPv6, who do we speak to, ISP's or Afrinic? Do I need to give strong motivation for this, or the obvious will do?

Depends on what you want.
Do you want IPs from your ISP that you'll never be able to move? ie: tied to that ISP
Or do you want your own IP allocation so you can change ISPs and take your IPs with you.

If you're happy to stick to the same ISP, the you get a chunk of their PA space.
If you want your own portable IP's, you get PI Space (Provider independent).

Personally, I think PI space is the way to do it. Then you can get multiple upstream providers.
 
What I want to know is, with IPv6, who do we speak to, ISP's or Afrinic? Do I need to give strong motivation for this, or the obvious will do?
Who do you get your IPv4 addresses from? Sounds like Telkom issues them to you. So I'd go to them.

Telkom has IPv6 and if you are not getting your connectivity via ADSL then they can probably get IPv6 connectivity to you.
 
Fundament flaw and CGN cannot be used in the same sentence because CGN is a fuindamental fix (not flaw). 65536 sockets are good enough if you use it wisely.

Simple - you will need to sign it or use an OpenID of sorts. This whole nonsense of using an IP address to see who you are is bullcrud, it may have worked in the 90's but its retarded and with the increasing use of NATing it is unreliable. IPs are there for one machine to talk to another - and that is the only reason we have IPs. Not to ban people or identify them, find other ways to do that.

You said it yourself. IPs are there for one machine to talk to another. But in a CGN, its not. Its for one machine talking to an entire ISP.
CGN breaks things. Badly. Remember when Screamer couldn't figure out how to route with their own IP space and ended up NATing all their customers from a single IP? It wasn't pretty. They shut down their ADSL offering.

IPv4 vs IPv6 isn't just about addresses, there are other protocol enhancements and capabilities in IPv6 that were built in from the start. Not hacked on like most extensions on IPv4.

Think of it as an "upgrade" for the internet, its not just about giving extra addresses.
 
True, IPv6 is a much needed upgrade and it is not just to solve the address space issues. But realistically speaking do you really think they are going to change the world to IPv6 in 90 days? I don't think so. A much likelier solution is some form of patch, like NATing or Cnames or anything that will get them to stick with what is working and make it work a little longer,
 
True, IPv6 is a much needed upgrade and it is not just to solve the address space issues. But realistically speaking do you really think they are going to change the world to IPv6 in 90 days? I don't think so. A much likelier solution is some form of patch, like NATing or Cnames or anything that will get them to stick with what is working and make it work a little longer,

No-one said it was going to take 90 days to convert to IPv6. Sure, there will be a need for some level of CGN, but when it comes down to costs, it'll probably cost just as much to deploy a CGN properly as it will to deploy IPv6. (Note that I said properly. Quick and dirty deployments of CGN will end up costing more than you expect.)

The truth is, ISPs should have been doing this for a long time already. If they're only waking up to IPv6 now, then IPv6 is the least of their problems.
I've had native IPv6 at home for almost 2 years already, long before there was any useful content on IPv6.

The biggest problem with commercial IPv6 deployments are in Layer 8 and 9, as with many network problems.
The marketers and sales people need to stop trying to market and sell IPv6 to customers.
 
PPPoE Relay over L2TP VPDNs just makes so much more sense, given its transparency.
Ya, but as with all matters IPv6, cost eventually becomes the determining factor. The cheaper option (e.g. IPC's pure IP routing) will continue to be used right up to the point where it is no longer viable (absolute IPv4 depletion).

PPPoE Relay (e.g. IPv6 IPS) requires some heafty investment in equipement capable of handling large-scale session origination/termination, and unfortunately clusters of N+1 redundant ASR9000s (or equiv.) dont come cheap.
 
Telkom still own the access

And how did you come to this conclusion?

Are Telkom the repository for IP addresses for South Africa? No, AfriNIC are.

So where does Telkom fit into your hypothesis?

OK, sure- but most people connect through an ISP that uses Telkom's IPC - so how do you propose they utilise a IPv6 addressing?
 
True, IPv6 is a much needed upgrade and it is not just to solve the address space issues. But realistically speaking do you really think they are going to change the world to IPv6 in 90 days? I don't think so. A much likelier solution is some form of patch, like NATing or Cnames or anything that will get them to stick with what is working and make it work a little longer,

http://arstechnica.com/old/content/...n-making-ipv6-and-ipv4-talk-to-each-other.ars

http://blog.go6.net/?p=210

http://www.cisco.com/en/US/prod/col..._ns1017_Networking_Solutions_White_Paper.html

Dual-stack is the way to go, IMO. Connect via IPv6 to your ISP, then let the ISP sort out what is IPv6 and IPv4 and route appropriately. You can then use a CGN for IPv4 routing. Trying to extend the current status quo with pure CGN-type solutions is the wrong way to go about it. The longer you force the current scenario, the more pain you will have when you migrate eventually, and in the meantime when resources go IPv6 as well.

Of course, in SA we'll be limited by Telkom. As long as Telkom uses IP Connect, and as long as IP Connect doesn't support IPv6, there is very little the ISP's can do about it.
 
Last edited:
another problem? isn't it only Vista and better can use IPv6? I see XP doesn't have the protocol?
 
another problem? isn't it only Vista and better can use IPv6? I see XP doesn't have the protocol?
Code:
install ipv6
should sort you out on XP :) Linux and Mac have supported IPv6 for ages :D
 
Code:
install ipv6
should sort you out on XP :) Linux and Mac have supported IPv6 for ages :D

I believe there's a implementation (incomplete) for Win2k as well, though I wouldn't really trust it. Only issue I have with Linux support is that 2.6.18 (used in RHEL5) doesn't have stateful firewalling support. That appeared IIRC in 2.6.20. But RHEL6 is out now, so that should be less of an issue.

Opinion question: I currently use a tunnel to Freenet6, terminating in Amsterdam to carry my IPv6 traffic. They delegate a /56 to me for this. Latency is obviously a bit of an issue. Is there a local (free) tunnel broker or similar service I can use for this? Or is there a better PoP or tunnel broker service? HE requires a static IP, while SiXXs and me never got along. The service operator had WAY too many rules and regulation about what may and may not be done.
 
Last edited:
Am I correct in saying that:
If your Internet IP Address is 41.243.9.???, instead of 2010:0f68:0000:0000:0000:0000:1986:???? then your ISP has not activated IPV6, or, your damn ADSL router is not IPV6 ready?

I wonder how much of a problem the hardware is going to be.
 
Last edited:
Am I correct in saying that:
If your Internet IP Address is 41.243.9.???, instead of 2010:0f68:0000:0000:0000:0000:1986:???? then your ISP has not activated IPV6, or, your damn ADSL router is not IPV6 ready?

I wonder how much of a problem the hardware is going to be.

You get the last 32 bits to play with, normally. So 2001:5c0:1507:65ff:????:????:????:???? would be a more accurate representation.

I know of no consumer modems that are IPv6-ready. My Netgear WNR-3500L recently had a IPv6 upgrade in released firmware, but it's a broadband router, not a modem. Perhaps some will release a firmware update, but most manufacturers would want you to re-purchase it. I will wait for the OS'es to add support for this first, before hardware vendors do. You would then put your modem in bridged mode (if it supports it) and use that to dial up. We will have to see what happens in the consumer device space.
 
I know of no consumer modems that are IPv6-ready. My Netgear WNR-3500L recently had a IPv6 upgrade in released firmware, but it's a broadband router, not a modem. Perhaps some will release a firmware update, but most manufacturers would want you to re-purchase it. I will wait for the OS'es to add support for this first, before hardware vendors do. You would then put your modem in bridged mode (if it supports it) and use that to dial up. We will have to see what happens in the consumer device space.
D-link already have a full range of IPv6-ready certified broadband routers. Mikrotiks also support IPv6 and they have a few nice broadband router models. The IPv6 Ready Logo Program lists all the devices that have been tested for compliance.

The trend has been that most of the vendors have no budget to release firmware updates and in most cases you will be forced to buy a new router when you require IPv6 functionality.

All of this is rather moot when none of our local Internet access providers can support native IPv6 on their networks.
 
D-link already have a full range of IPv6-ready certified broadband routers. Mikrotiks also support IPv6 and they have a few nice broadband router models. The IPv6 Ready Logo Program lists all the devices that have been tested for compliance.

The trend has been that most of the vendors have no budget to release firmware updates and in most cases you will be forced to buy a new router when you require IPv6 functionality.

All of this is rather moot when none of our local Internet access providers can support native IPv6 on their networks.

Quite a few more than I thought. But yeah ... we will have to likely re-purchase hardware. Thanks for the link.
 
DoC will announce Legislation for the Liberalisation of Internet Protocols for South Africa and Task ICASA it investigate the feasibility of IPv6, which Telkom will contest in Court, leaving South Africa disconnected from the Global network and paying exorbitant prices for local connectivity to Government Controlled Email Servers for about 5 years after the deadline originally legislated.

And you think that Y2K pundits were paranoid :)

This is a serious issue and one that is hard to explain to the been counters, even by Network Engineers, but the bottom line is that once again Telkom has the country by the nuts is is doing nothing about it as long as they can profit by inaction.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X