Hello There,

After seeing the functionality of the IP6 tunnel that I acquired not long ago. I decided to acquire a second tunnel for my 1:282/1031 node. I should mention that due to some software issues I have decided to once again merge 1:282/1031, 1:14/5, 1:14/0 into one system. While the FQDN's will be differant. The IP4 and IP6 addresses will the same. I have updated the DNS to reflect the new IPv6 address of 2001:470:1f10:133::2 for 1:282/1031 (bbs.ouijabrd.net) and 1:14/5 (ftn.region14.org).


Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net

Hello Jeff,

On Wednesday July 31 2019 22:07, you wrote to All:

After seeing the functionality of the IP6 tunnel that I acquired not
long ago. I decided to acquire a second tunnel for my 1:282/1031 node.

10:10 [2924] creating a poll for 1:282/1031@fidonet (`d' flavour)
10:10 [2924] clientmgr started
+ 10:10 [1812] call to 1:282/1031@fidonet
10:10 [1812] trying bbs.ouijabrd.net [2001:470:1f10:133::2]...
10:10 [1812] connected
+ 10:10 [1812] outgoing session with bbs.ouijabrd.net:24554 [2001:470:1f10:133::2]
- 10:10 [1812] SYS The Ouija Board
- 10:10 [1812] ZYZ Jeff Smith

It works!

I should mention that due to some software issues I have decided to
once again merge 1:282/1031, 1:14/5, 1:14/0 into one system.

I have updated the list of IPv6 nodes.

I have updated the DNS to reflect the new IPv6 address of 2001:470:1f10:133::2 for 1:282/1031 (bbs.ouijabrd.net) and 1:14/5 (ftn.region14.org).

I see that it all ends on ::2. So you are using the tunnel endpoints for your nodes.

Are you aware that - if they are on the same LAN - you do not need a sepearate tunnel for each node, but that you can have a routed subnet (/64 or /48) from he.net and use just one tunnel for all the nodes om your LAN?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel,

On Wednesday July 31 2019 22:07, you wrote to All:

I see that it all ends on ::2. So you are using the tunnel endpoints for

your

nodes.

Are you aware that - if they are on the same LAN - you do not need a sepearate
tunnel for each node, but that you can have a routed subnet (/64 or /48)

from

he.net and use just one tunnel for all the nodes om your LAN?

I had the understanding that the tunnel was related to a static v4 endpoint IP. Here each PC (FTN Node) has it's own static v4 IP. Are you saying that a single tunnel can support multiple static v4 IP endpoints?

Jeff


--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidonet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)

Hello Jeff,

On Thursday August 01 2019 09:43, you wrote to me:

Are you aware that - if they are on the same LAN - you do not need a
sepearate tunnel for each node, but that you can have a routed subnet
(/64 or /48) from he.net and use just one tunnel for all the nodes om
your LAN?

I had the understanding that the tunnel was related to a static v4 endpoint IP. Here each PC (FTN Node) has it's own static v4 IP. Are
you saying that a single tunnel can support multiple static v4 IP endpoints?

The tunnel does not "support" a static IPv4 endpoint. It is more the other way around. A tunnel needs a public IPv4 address for its end point. The same public IPv4 address can be used for other purposes, such as a Fidonet Binkp server. But it need not be. The fact that the tunnel is used to supply an IPv6 address to the same binkd server is irrelevant. The binkp server can be on a different IPv4 address than the tunnel servicing the IPOv6 part.

Yes, for a second tunnel, you need a different public IPv4 address for the end point.

My point is: you probably do not need a second tunnel. A tunnel is a channel to the rest of the world that can handle many IPv6 addresses. Just like an IPv4 router can make you connect many device to the IPv4 internet via a single channel, so can a tunnel for IPv6.

You can assign different IPv6 addresses to 1:282/1031 and 1:14/6 over one and the same tunnel.

How this is done and if it is "better" in your situation is another matter.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel,

The tunnel does not "support" a static IPv4 endpoint. It is more the other way
around. A tunnel needs a public IPv4 address for its end point. The same publi
IPv4 address can be used for other purposes, such as a Fidonet Binkp server.
But it need not be. The fact that the tunnel is used to supply an IPv6 address
to the same binkd server is irrelevant. The binkp server can be on a different
IPv4 address than the tunnel servicing the IPOv6 part.

Yes, for a second tunnel, you need a different public IPv4 address for the end
point.

My point is: you probably do not need a second tunnel. A tunnel is a channel
the rest of the world that can handle many IPv6 addresses. Just like an IPv4 router can make you connect many device to the IPv4 internet via a single channel, so can a tunnel for IPv6.

You can assign different IPv6 addresses to 1:282/1031 and 1:14/6 over one

and

the same tunnel.
How this is done and if it is "better" in your situation is another matter.

I am learning as I go here. :-) Now... If my line of reasoning is reasonable I could setup a tunnel to a reflashed router with a public IP which would then service the IP's in use here. I have a router provided by my service provider that I am better off not messing with. I think I might have an older LinkSys router that I could use for testing different ideas. I may not be totally on the mark with my thinking "Yet" but I am working on it. :-)

Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidonet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)

Hello Jeff,

On Friday August 02 2019 11:07, you wrote to me:

I am learning as I go here. :-) Now... If my line of reasoning is reasonable I could setup a tunnel to a reflashed router with a public
IP which would then service the IP's in use here.

That is exactly how I did it before I got native IPv6 ftom my ISP. I reflashed a Linksys WRT 54G with OpenWrt.

I wrote a series of Fidonews articles about it. IIRC the first one is titled "A second life for the Linksys".

Here is the binary for the flash:

http://www.vlist.eu/downloads/openwrt-wrt54g-squashfs-r25759.bin

I will post the articles in the next messages.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)