Are we (Amiga-hardware-software) ready for IPv6?

_________________
A1G3-SE + OS4.1 u1 iso (x2)

@Dirk-B

No.

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@Dirk-B

Aw.net is.

_________________
Site admins are people too..pooff!

@

IPV6 is effective since yesterday.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

Made the test and the net connection is not yet ready. Only 25Mb+ quite new one.

Works Really well.

Unlimited addresses, "users should not notice anything".
Maybe Timberwolf+RoadShow+ mut not maybe the point? Only the operators problem?



Good that this forum is ready.

Called the operator and there is no problem for the change. Our country should be
Top Notch about these. The Amigas should not suffer from the change.

@Dirk-B

Here you go, carry out your own tests: http://test-ipv6.com

Draby

@Dirk-B

It's not ready as per TCP/IP stack but I wouldn't worry, it will takes years before IPv4 will get abondoned.

_________________
OpenWindows Initiative. Port PS3 hardware to bananas. For free. Join today and receive expired $50 cupon from AI!

@Thread

Last time I read what should be done to become V6, I had a headache. Anyone with easy to understand steps that show what to do on PC?

_________________
Philippe 'Elwood' Ferrucci
Sam460 1.10 Ghz
AmigaOS 4 betatester
Amiga Translator Organisation

@elwood

OK, follow those steps:

1. Get a current OS
2. You're done

The rest is up to your ISP (IPv4-IPv6 gateways, up-to-date hardware, etc)

_________________
OpenWindows Initiative. Port PS3 hardware to bananas. For free. Join today and receive expired $50 cupon from AI!

@opi

Quote:

1. Get a current OS

AmigaOS 4.1 Update 5?

_________________
Games, programs, reviews

@opi

Which is precisely the answer I got last time I brought this up. This is not a "do nothing" situation. IPv4 addresses are running out and various hosts will eventually be forced to allocate only IPv6 addresses. You can delay it with NATting etc, but there's only so much you can do before that ceases to be a workable solution.

Basically we should be writing an IPv6 capable TCP/IP stack now. In fact, I'd argue we should already have one. If we wait we get into exactly the same situation we had with CSS capable web browsers, except this time it'll be "host not found" rather than some formatting errors.

Some cross-platform effort between AmigaOS, MorphOS and AROS developers would be ideal here.

Last edited by Chris_Y on 07-Jun-2012 at 06:21 PM.
Last edited by Chris_Y on 07-Jun-2012 at 06:20 PM.

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@Chris_Y

I'm doing just that, just run in too some problems whit TCP/IP handshaking. I have only been using Basilisk as test environment, but now I'm looking in to adding support for the rtl8139c card, if get this running maybe I can monitor traffic and solve some of the problems.

I most admit I have mostly been vesting time on forums, Facebook and Starcraft II and my day time job, so progress is sloooowww...

Yes and that starbar/toolbar thing called Excalibur, by the way have any one noticed any problems whit last 1.1.1 version?

Last edited by NutsAboutAmiga on 07-Jun-2012 at 10:15 PM.
Last edited by NutsAboutAmiga on 07-Jun-2012 at 06:59 PM.
Last edited by NutsAboutAmiga on 07-Jun-2012 at 06:58 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Good luck! I strongly recommend you support the SANA-II device specification rather than writing your own drivers though!

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@Chris_Y

Me too.

Sorry I don't know how to do that and that’s way Basilisk does not have network support for RoadShow, RoadShow has a modified version of SANA-II, there is hardly any new documentation on it, and SANA-II drivers as open source seam to me as a bit complicated and hard to understand.

Last edited by NutsAboutAmiga on 08-Jun-2012 at 06:29 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

NutsAboutAmiga wrote: @Chris_Y Me too. Sorry I don't know how to do that and that’s way Basilisk does not have network support for RoadShow,

How would that work, anyhow? Basilisk likely would have to offer EtherTalk (or MacTCP) support, and that kind of thing would sit on top of your basic network layer 2, i.e. the SANA-II packet interface. You can't fit this comfortably into raw sockets or UDP datagrams.

Quote:

RoadShow has a modified version of SANA-II,

Yes, and no. Yes, it's not straight SANA-II (version 1.0, as of 1992), but SANA-IIR3 which is SANA-II release 2.0 (as of 1994) plus enhancements for better buffer management (release 3, as of 1996). No, this is nothing special, and the Roadshow TCP/IP stack doesn't use any fancy secret enhancements beyond that.

Quote:

there is hardly any new documentation on it,

Because the last changes made were done in the early/mid-2000's? Not much new has emerged since then. And, as you are well aware, the documentation was fragmented and not necessarily in readable form.

When I started writing Roadshow, I went the extra mile and compiled my own work documentation on SANA-IIR3. This documentation is now online as Revision 2+3 and should be as complete as it can be.

Of course, you still need a real driver implementation to see how the parts work together. The closest to that might be the modified cslip.device, although the original Commodore example code might make for better reading. I'll try to get that online as well.

Quote:

and SANA-II drivers as open source seam to me as a bit complicated and hard to understand.

I'd say that this is likely the result of not having much good documentation at hand. The driver design itself is pretty simple, but you need to understand both the specification and the implementation. In isolation each is bound to be more cryptic than it ought to be.

I'm surprised you even got as far as you did without having access to decent documentation and driver implementation. It must have been tough

@olsen

Thanks for documents, I read and study what you have provided.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@olsen

Quote:

How would that work, anyhow?

It might work whit network tunneling for my experiments, but I don’t have two AmigaOS4 compatible computers, so that not really useful, the other way is implementing some kind of NAT service, and DNS service, basically build a virtual router.

Anyway there seems to be a problem whit ARP replays from Basilisk, I can emulate this, so that’s not a problem.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Dirk-B

Like Opi said, IPv4 will still be around for a while, several years, but time goes by fast and once the final IPv6 switch takes place it's going to create many issues, the main one being that any software and hardware which can't be updated will become useless outside of LAN applications.

Like ChrisY said, we'll have a problem unless we do something about it sooner than later and it's the perfect example of a situation where collaboration would go a long way because all 4 incarnations of the OS need to make the move to IPv6.

Unfortunately IPv6 isn't human-friendly at all, it's hard enough to remember a few IPs with 12 numbers from 0 to 9, good luck remembering a single one with 16 digits from 0 to F!

Even though it won't change a thing, I'd like to point out that while IANA say that 4 billion IPs isn't enough and that we ran out, they generally fail to mention that we're only using 20% of all the IPs assigned. The root of the problem is their poor resource management and enforcement, such as assigning huge blocks of IPs to some organizations regardless of how many they actually need and use, and the fact that most people don't need their own IP as they're not running public servers at home and wouldn't notice a difference if their ISP assigned a private IP with NAT.

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

There are very few personal computers connected directly to the ISP, most of them use a router in between, which can easily make the connection between V6 and v4 or whatever. So I don't think there will be any problem at all despite the machines used as servers, WAN routers etc.

Last edited by Jose on 11-Jun-2012 at 03:16 PM.
Last edited by Jose on 11-Jun-2012 at 03:16 PM.

_________________

José

@Jose

Translation between v4 and v6 isn't all that easy. It's possible in theory, but it requires something a lot more complicated than current NAT solutions from the router. The problem is that applications also need to understand v6, and they can't do that until the TCP/IP stack supports it. True, it's many years away yet, but things like email clients, web browsers, IRC clients etc. will all eventually stop working unless they're updated to understand v6 addresses...

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X