Hello Deon,

On Sunday October 11 2020 11:50, you wrote to Bj”rn Felten:
^

@MSGID: 763.fdn_ipv6@3:633/509 23e78fc2
@REPLY: 2:203/2 5f820762
@PID: Synchronet 3.18c-Linux Oct 9 2020 GCC 8.3.0
@TZUTC: 1100
@TID: SBBSecho 3.11-Linux r3.179 Oct 9 2020 GCC 8.3.0
@CHRS: ASCII 1

^^^^^^^

By: Björn Felten to Deon George on Sat Oct 10 2020 09:11 pm

^
CHRS kludge doesn't match character encoding in use....

It just seems logical to me, that if you wanted to have a f1d0
convention, you would choose hex, since numbers that are used to
represent a node can be between 0-32767, and that can be represented completely in a IPv6 address if somebody chose to do so.

I must admit that from the techie POV there is some logic to this line of reasoning.

As ever so often in life however, that is not how this evolved. The one that started it - it wasn't me - apparently thought it was a good idea to present the node number in human readable, and human easy to remember, form. iow in the from that node numbers are usually presented to humans: in decimal.

So far 29 others have followed this idea.

So, I'm guessing I cant have the little "f" next to my listing? :(

Sorry, no. Decimal is the game.

If you do not like the rules you are free to start your own game of course. But if you do, please be so kind to use something other than "f1d0" for the first 16 bits of the host part of the address. "f1d0" is already in use as a keyword for representing the node number in decimal.


Cheers, Michiel

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

Michiel wrote (2020-10-11):

So, I'm guessing I cant have the little "f" next to my listing? :(

MvdV> Sorry, no. Decimal is the game.

MvdV> If you do not like the rules you are free to start your own game of
MvdV> course. But if you do, please be so kind to use something other than
MvdV> "f1d0" for the first 16 bits of the host part of the address. "f1d0" is
MvdV> already in use as a keyword for representing the node number in decimal.

new game:

f1d<zone>:<net>:<node>:<point> in hex
*::f1d0:0:0:0/76


(btw, who gives a shit about the rules?)

---
* Origin: (2:280/464.47)

Hello Oliver,

On Monday October 12 2020 15:13, you wrote to me:

new game:

f1d<zone>:<net>:<node>:<point> in hex
*::f1d0:0:0:0/76

So go ahead. Make your binkp server available for incoming calls, set the IPv6 address to *::f1d2:118:1d0:2f, advertise it and see how many follow...


Cheers, Michiel

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

Hi Oli.

12 Oct 20 15:13:26, you wrote to Michiel van der Vlist:

new game:

f1d<zone>:<net>:<node>:<point> in hex
*::f1d0:0:0:0/76

Isn't that 'f1d' part useless. Zone 2 is fido anyways.

How about this, try the origin line.

(btw, who gives a shit about the rules?)

Indeed. ;)

'Tommi

---
* Origin: 2001:470:1f15:cb0:2:221:0:1 (2:221/0.1)

(btw, who gives a shit about the rules?)

I seem to recall a certain POTUS and his followers that does not just that. Maybe it's spreading like the corona virus...?



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Tommi wrote (2020-10-12):

f1d<zone>:<net>:<node>:<point> in hex
*::f1d0:0:0:0/76

Isn't that 'f1d' part useless. Zone 2 is fido anyways.

I guess :1: and :2: is used more often by non-fido systems than fid0. But isn't the whole idea useless anyway? Most nodes have multiple FTN addresses. You cannot map the FTN address to an IP address, if you don't know the most significant 64bit of the system. The Domain / IP is in the nodelist anyway. It would be somewhat useful in a VPN / overlay network though.

How about this, try the origin line.

---
* Origin: 2001:470:1f15:cb0:2:221:0:1 (2:221/0.1)

---
* Origin: (2:280/464.47)

Hello Oliver,

On Tuesday October 13 2020 10:42, you wrote to Tommi Koivula:

f1d<zone>:<net>:<node>:<point> in hex
*::f1d0:0:0:0/76

Isn't that 'f1d' part useless. Zone 2 is fido anyways.

I guess :1: and :2: is used more often by non-fido systems than fid0.

Not in the first 16 bits of the host part of the address.

But isn't the whole idea useless anyway? Most nodes have multiple FTN addresses. You cannot map the FTN address to an IP address,

Most nodes do not have more than one Fidonet address. Some have more than one, but most have just one. An IP interface can (and normally does have) more than one IPv6 address. And while one can not match the Fidonet address to the IP address, one can match the address to the node number. If I see
07 Oct 18:00:10 [1404] incoming from 2a02:e840:1000:90:f1d0:2:5053:58,
I know where it comes from even if the session fails to connect. is that useful? Maybe. But why does it have to be useful at all? Is Fidonet "useful"? It is a hobby. Hobbies can not be judged bu usefulness.

So far 30 sysops have configured their systems to use an f1d0 address for their fidonet node. Good enough for me.


Cheers, Michiel

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

Hi Tommi!

Monday October 12 2020 19:02, you wrote to Oli:

How about this, try the origin line.

[fido@localhost ~]$ ping -6 -c 4 2001:470:1f15:cb0:2:221:0:1
PING 2001:470:1f15:cb0:2:221:0:1(2001:470:1f15:cb0:2:221:0:1) 56 data bytes From 2001:470:1f14:cb0::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:470:1f14:cb0::2 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:470:1f14:cb0::2 icmp_seq=3 Destination unreachable: Address unreachable
From 2001:470:1f14:cb0::2 icmp_seq=4 Destination unreachable: Address unreachable

-+- 2001:470:1f15:cb0:2:221:0:1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3075ms

;-)

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

On 15.11.2020 21:50, Stas Mishchenkov - Tommi Koivula :

Monday October 12 2020 19:02, you wrote to Oli:

How about this, try the origin line.

[fido@localhost ~]$ ping -6 -c 4 2001:470:1f15:cb0:2:221:0:1
PING 2001:470:1f15:cb0:2:221:0:1(2001:470:1f15:cb0:2:221:0:1) 56 data bytes From 2001:470:1f14:cb0::2 icmp_seq=1 Destination unreachable: Address

unreachable

From 2001:470:1f14:cb0::2 icmp_seq=2 Destination unreachable: Address

unreachable

From 2001:470:1f14:cb0::2 icmp_seq=3 Destination unreachable: Address

unreachable

From 2001:470:1f14:cb0::2 icmp_seq=4 Destination unreachable: Address

unreachable

-+- 2001:470:1f15:cb0:2:221:0:1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3075ms

;-)

Maybe the laptop that runs the point 2:221/0.1 should be turned on and
the VPN to my home also up. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.7) Goanna/20201028 Interlink/52.9.7606
* Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/360.0)