I am sure the FTN community is resourceful and helpful enough to adapt and find workarounds as required.
On 12-31-19 21:49, August Abolins wrote to All <=-
Here's wishing all readers of this echo a great New Year!
I wonder what new technology changes we'll be seeing as we look to the future to the Roaring Twenties! <g>
The rollout of IPv6 may affect legacy fidonet systems sooner than expected.
In my understanding the main issue will be IPv4 systems unable to reach (poll) IPv6-only systems. Otherwise, IPv4 systems will only be able to receive incoming polls from IPv6 systems, and be limited to incoming
and outgoing only to other IPv4 systems. ???
I am sure the FTN community is resourceful and helpful enough to adapt
and find workarounds as required.
The rollout of IPv6 may affect legacy fidonet systems sooner thanexpected.
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
On 01-02-20 09:55, Tommi Koivula wrote to August Abolins <=-
31 Dec 19 21:49, August Abolins wrote to All:
The rollout of IPv6 may affect legacy fidonet systems sooner than
expected.
This system runs on a legacy os: OS/2. It doesn't know anything about IPv6.
However, it runs behind a linux router and is connectable via IPv6. In
and out.
So don't worry. Be happy. :)
This system runs on a legacy os: OS/2. It doesn't know anything about
IPv6.
However, it runs behind a linux router and is connectable via IPv6. In
and out.
So don't worry. Be happy. :)
You forwarding ports on IPv6 to IPv4 LAN addresses?
The rollout of IPv6 may affect legacy fidonet systems sooner
than expected.
This system runs on a legacy os: OS/2. It doesn't know anything
about IPv6.
However, it runs behind a linux router and is connectable via
IPv6. In and out.
So don't worry. Be happy.
Appropriate routing will help. Systems like mine, that have
connectivity both ways on IPv4 and IPv6 will be a key..
On 31/12/2019 6:18 p.m., Tony Langdon : August Abolins wrote:
Appropriate routing will help. Systems like mine, that have
connectivity both ways on IPv4 and IPv6 will be a key..
On 01-02-20 12:01, Tommi Koivula wrote to Tony Langdon <=-
You forwarding ports on IPv6 to IPv4 LAN addresses?
Yes.
And out via proxy.
On 01-02-20 19:53, August Abolins wrote to Tony Langdon <=-
On 31/12/2019 6:18 p.m., Tony Langdon : August Abolins wrote:
Appropriate routing will help. Systems like mine, that have
connectivity both ways on IPv4 and IPv6 will be a key..
Hi Tony,
The solution solving for the new scenario ought to be in each sysop's wheelhouse, purview and interest to make things work. But, there will
be compromises. The direct P2P connectivity as per the nodelist, the luxury of bi-directional crash mail, will have glitches though.
Lots of fun to look forward too. :) Hope it doesn't frustrate too
many and just give up.
On 01-02-20 19:16, August Abolins wrote to Tommi Koivula <=-
I'm impressed with the OS/2 part.
I have a perfectly fine boxed copy of Warp Connect V3. If you ever
feel you need to "upgrade", give me a shout. I still have an unopened
box of Lotus Smartsuite for OS/2 (orig Retail $30). As you can tell, I had plans from long ago that never came to fruition.
However, it runs behind a linux router and is connectable via
IPv6. In and out.
So don't worry. Be happy.
On 01-02-20 23:11, Kees van Eeten wrote to August Abolins <=-
Where is the above problem different from legacy systems, that only support POTS, now that many nodes become IP only.
Cool. Curious what you're using to do the forwarding/proxying. Might be something to experiment with. I don't have a current need, but if I wantto
put some legacy system online, it would be handy to know.
I have a perfectly fine boxed copy of Warp Connect V3. If you ever
feel you need to "upgrade", give me a shout.
I have a perfectly fine boxed copy of Warp Connect V3. If you
ever feel you need to "upgrade", give me a shout.
Warp Connect would be a major downgrade.
On 03/01/2020 5:49 a.m., Tommi Koivula : August Abolins wrote:
I have a perfectly fine boxed copy of Warp Connect V3. If you
ever feel you need to "upgrade", give me a shout.
Warp Connect would be a major downgrade.
Hmmmm. I thought you were using truly "legacy" OS/2, as in 2.0 or 2.1
But I see that Connect does not support USB. That would not be fun.
On 01-03-20 12:46, Tommi Koivula wrote to Tony Langdon <=-
I wrote about this in IPV6 echo a long time ago.
Squid and Privoxy can do the trick, and many others I think. Right now
I am using Privoxy in a linux computer that has a 4G/LTE connection to
the world, so the outbound traffic is much faster than inbound (10/1M ADSL). :)
There is not much to set up in Binkd/OS2. Just to tell binkd to use
proxy, and the proxy in linux will do outbound by IPV6 by default. :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,063 |
Nodes: | 17 (2 / 15) |
Uptime: | 09:56:37 |
Calls: | 501,111 |
Calls today: | 4 |
Files: | 109,393 |
D/L today: |
307 files (36,817K bytes) |
Messages: | 300,307 |