A well known and respected italian ex-amigan launched this alarm on:

http://www.amigapage.it

He reports that from incoming year 2006 the switch off of IPV4 internet address protocl will start worldwide.

First nations that will pass to new IPV6 protocol will be China, Japan, Korea, and India.

India is one of the countries in which there were plans to sell Amigas and Amiga-like platforms.

«Are AmigaOS compatible, MOS and AROS TCP-IP stacks, browsers, FTP software and other P2p and radio thingies ready for IPV6 protocol?»

- «Obviously not!» He continued!

I agree with him.

But, I am a bit lesser worried because all software for Amiga, MOS and AROS are now open sourced and the developing teams are working with a steady rythm.

Browsers, ftp progs, P2P, etc. could be updated in a few.

But really problems are the TCP-IP Stacks.

Any MOS bounty to update our incoming TCP stack?

Heh...
It would change the current status and development way, but it IS possible for ezTCP. Its current status you can see in the corresponding thread, i'll finish v0.12 on monday. Since it's opensource it is possible to upgrade it basing on the recent FreeBSD (for example) code. This would automatically add IPv6, PPP, PPPoE, T/TCP, etc, support.
Unfortunately i have no time if we speak about current conditions. I already have to extend the deadline since it's approaching and only quite a small part of GUI is ready.

Thank you.

Even if you take a look only later at freeBSD Kernel regarding IPV6 incoming problem, it will be fine.

We all amigans apprecciate your work and your professional skills.

Ciao,

Raffaele

This is nonsense, IPv4 isn't going to be switched off over night, and even if it were there'd be no problem, as routers would solve that problem quite neatly (ie, IPv4 locally and IPv6 externally)...


- CISC

by CISC on 2005/10/28 20:20:40

This is nonsense, IPv4 isn't going to be switched off over night, and even if it were there'd be no problem, as routers would solve that problem quite neatly (ie, IPv4 locally and IPv6 externally)...

I agree to the fact that the switch off IPV4->IPV6 will not be an immediate...

...but is it recommended a router based solution?

Am I wrong, or with this "trick" of using router then you could locate resources only by typing name of the site (example: "www.type_name_of_the_site_here.com") , and you couldn't use numeric URL???

Or at least, if you joe-user want to use IPV6 numeric addresses by working into IPV4 environment...

...then you must have into TCP-IP stack (and then - again - you have to deal with it) an interpreter progam (sort of "hack") to tunnel IPV6 addresses into IPV4 packet...