Hello Flavio,

On Sunday November 16 2025 23:53, you wrote to All:

Can someone try to connect via binkp to fido.rbt.net.br? (I hope the
AAAA record has been updated)

No AAAA record, plus that 4:801/188 is not present in the list of AKA's


+ 08:41 [2724] call to 4:801/188@fidonet
08:41 [2724] trying fido.rbt.net.br [35.192.92.175]...
08:41 [2724] connected
+ 08:41 [2724] outgoing session with fido.rbt.net.br:24554 [35.192.92.175]
- 08:41 [2724] OPT CRAM-MD5-a6b596e66ca55d24e7c08316b2cef0d8
+ 08:41 [2724] Remote requests MD mode
- 08:41 [2724] SYS Internet Hub
- 08:41 [2724] LOC Rio de Janeiro - Brazil
- 08:41 [2724] ZYZ Flavio Bessa
- 08:41 [2724] TIME Tue, 18 Nov 2025 04:40:41 -0300
- 08:41 [2724] VER Mystic/1.12A48 binkp/1.0
- 08:41 [2724] BUILD 2023/01/15 12:54:18 Linux/64
+ 08:41 [2724] addr: 4:80/1@fidonet
+ 08:41 [2724] addr: 4:801/0@fidonet
+ 08:41 [2724] addr: 4:80/0@fidonet
+ 08:41 [2724] addr: 4:801/1@fidonet
? 08:41 [2724] called 4:801/188@fidonet, but remote has no such AKA


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

Michiel van der Vlist wrote:

No AAAA record, plus that 4:801/188 is not present in the list of AKA's

Why should it, it is a PVT node.

"Pvt,188,Saturn's_Orbit_BBS,Rio_de_Janeiro_RJ,Flavio_Bessa,-Unpublished-,300"

+ 08:41 [2724] call to 4:801/188@fidonet
08:41 [2724] trying fido.rbt.net.br [35.192.92.175]...
08:41 [2724] connected
+ 08:41 [2724] outgoing session with fido.rbt.net.br:24554 [35.192.92.175]
- 08:41 [2724] OPT CRAM-MD5-a6b596e66ca55d24e7c08316b2cef0d8
+ 08:41 [2724] Remote requests MD mode
- 08:41 [2724] SYS Internet Hub
- 08:41 [2724] LOC Rio de Janeiro - Brazil
- 08:41 [2724] ZYZ Flavio Bessa
- 08:41 [2724] TIME Tue, 18 Nov 2025 04:40:41 -0300
- 08:41 [2724] VER Mystic/1.12A48 binkp/1.0
- 08:41 [2724] BUILD 2023/01/15 12:54:18 Linux/64
+ 08:41 [2724] addr: 4:80/1@fidonet
+ 08:41 [2724] addr: 4:801/0@fidonet
+ 08:41 [2724] addr: 4:80/0@fidonet
+ 08:41 [2724] addr: 4:801/1@fidonet
? 08:41 [2724] called 4:801/188@fidonet, but remote has no such AKA

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntps://rbb.fidonet.fi - Finland (2:221/360.0)

Hello Tommi,

On Tuesday November 18 2025 12:04, you wrote to me:

Michiel van der Vlist wrote:

No AAAA record, plus that 4:801/188 is not present in the list of
AKA's

Why should it, it is a PVT node.

"Pvt,188,Saturn's_Orbit_BBS,Rio_de_Janeiro_RJ,Flavio_Bessa,-Unpublishe d-,300"

Yes, but he wrote from that node number and asked us to test it...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

On 17 Nov 2025, Jay Harris said the following...

No AAAA record as of yet:

$ nslookup fido.rbt.net.br

Non-authoritative answer:
Name: fido.rbt.net.br
Address: 35.192.92.175

Thank you! The DNS provider should take a little longer to get it done.

... The person who snores the loudest will fall asleep first

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)

On 18 Nov 2025, Michiel van der Vlist said the following...

No AAAA record, plus that 4:801/188 is not present in the list of AKA's

That is by design. Here at Region 80, we decided that it would be of best interest of the region to have a dedicated MO system that would be independent of any BBS, to avoid the issues we used to have with our previous ZC, which system would fail frequently and disrupt the message flow.

So, we have an instance running at Google Cloud which hosts 4:80/1, and it distributes mail to all 4:801/* nodes. That allowed us to have close to 100% of availability since then.

4:801/188 is as of now a private node, which I use to read Fido email. When I step down from the R80 role, the new RC will take over the administration of that Google Cloud instance.

If you check the nodelist, will notice that 4:80/1 does have a MO flag.

I have already contacted the DNS provider and they will add the AAAA record soon, once this is ready I will ask you guys to retest.

... Everyone has a photographic memory. Some don't have film.

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)

On 18 Nov 2025, Tommi Koivula said the following...

Why should it, it is a PVT node.

"Pvt,188,Saturn's_Orbit_BBS,Rio_de_Janeiro_RJ,Flavio_Bessa,-Unpublished-,3

Yeah, the one to be polled is actually 4:80/1:

Region,80,Rede_Brasil,Rio_de_Janeiro_RJ,Flavio_Bessa,-Unpublished-,300,CM,MO,IB N:fido.rbt.net.br,PING,TRACE ,1,Internet_HUB,Brasil,Flavio_Bessa,-Unpublished-,300,CM,MO,IBN:fido.rbt.net.br ,PING,TRACE

(I know the FQDN is not there at the nodelist, but hopefully it will be after the next Z4 nodelist update)

... Internal Error: The system has been taken over by sheep at line 19960

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)

Hello Flavio,

On Tuesday November 18 2025 09:02, you wrote to me:

No AAAA record, plus that 4:801/188 is not present in the list of
AKA's

That is by design. Here at Region 80, we decided that it would be
of best interest of the region to have a dedicated MO system that
would be independent of any BBS, to avoid the issues we used to have
with our previous ZC, which system would fail frequently and disrupt
the message flow.

So, we have an instance running at Google Cloud which hosts
4:80/1, and it distributes mail to all 4:801/* nodes. That allowed us
to have close to 100% of availability since then.

OK, so it is 4:80/1 that you want us to test.

4:801/188 is as of now a private node, which I use to read Fido email.

Here we normally use a point number if/when we do not want to use the main node number for reading and posting mail.

I have already contacted the DNS provider and they will add the AAAA record soon, once this is ready I will ask you guys to retest.

You can not change it yourself via the web page of the DNS provider? Hmmm...

So give us the literal IPv6 number, so we can test on that...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

On 18 Nov 2025, Michiel van der Vlist said the following...

You can not change it yourself via the web page of the DNS provider? Hmmm...

So give us the literal IPv6 number, so we can test on that...

Yeah, the changes are done manually and take some time.

If you can test, the IPv6 is:

2600:1900:4000:a2b2:0:0:0:0

Let me know how it goes.

... Nine times out of ten the statisticians are wrong

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)

Hello folks,

I am trying to enable my Binkp hub to accept Ipv6 calls, but I don't know if I have configured it correctly.

Can someone try to connect via binkp to fido.rbt.net.br? (I hope the AAAA record has been updated)

... Kilometers are shorter than miles. Save gas, take your trip in kilometers

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)

16 Nov 25 23:53:48 Flavio Bessa (4:801/188) wrote:

==== begin of the message ====
@TID: Mystic BBS 1.12 A48
@MSGID: 4:801/188 3c938225
@TZUTC: -0300
Hello folks,

I am trying to enable my Binkp hub to accept Ipv6 calls, but I don't know if I have configured it correctly.

Can someone try to connect via binkp to fido.rbt.net.br? (I hope the AAAA record has been updated)

... Kilometers are shorter than miles. Save gas, take your trip in kilometers

-+- Mystic BBS v1.12 A48 (macOS/64)
+ Origin: Saturn's Orbit BBS - From Brazil to the World! (4:801/188)
SEEN+BY: 19/10 80/1 153/757 154/10 218/840 840 220/70 221/1 6 360 226/17 SEEN+BY: 267/800 280/464 301/1 335/364 341/66 234 460/58 633/280 712/848 770/1 SEEN+BY: 770/100 340 350 772/210 220 230 801/161 188 189 194 197 202 900/108 SEEN+BY: 5020/1042
@PATH: 801/188 80/1 770/1 218/840 221/6
==== end of the message ====

---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)

On 17/11/2025 4.53, Flavio Bessa wrote:

Hello folks,

I am trying to enable my Binkp hub to accept Ipv6 calls, but I don't
know if I have configured it correctly.

Can someone try to connect via binkp to fido.rbt.net.br? (I hope the
AAAA record has been updated)

Sorry, no AAAA.

--
Tommi

---
* Origin: nntps://rbb.fidonet.fi - Finland (2:221/360.0)

On 16 Nov 2025, Flavio Bessa said the following...

Can someone try to connect via binkp to fido.rbt.net.br? (I hope the AAAA record has been updated)

No AAAA record as of yet:

$ nslookup fido.rbt.net.br

Non-authoritative answer:
Name: fido.rbt.net.br
Address: 35.192.92.175


Jay

... Orion's belt is ok as far as constellations go. I give it three stars

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hello Flavio,

On Tuesday November 18 2025 11:42, you wrote to me:

You can not change it yourself via the web page of the DNS
provider? Hmmm...

So give us the literal IPv6 number, so we can test on that...

Yeah, the changes are done manually and take some time.

I would change DNS provider in that case...

If you can test, the IPv6 is:

2600:1900:4000:a2b2:0:0:0:0

That doesn''t look like a valod host address with all zeros for the host part of he address...

Let me know how it goes.

And indeed, no go...

+ 17:42 [5732] call to 4:80/1@fidonet
17:42 [5732] trying 2600:1900:4000:a2b2:0:0:0:0 [2600:1900:4000:a2b2::]...
? 17:43 [5732] connection to 4:80/1@fidonet failed: {W32 API
error 10060} Connection timed out
17:43 [324] the queue is empty, quitting...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

* Originally in FIDOTEST
* Crossposted in IPV6

Hello Flavio,

Tuesday November 18 2025 19:24, I wrote to you:

Let me know how it goes.

And indeed, no go...

+ 17:42 [5732] call to 4:80/1@fidonet
17:42 [5732] trying 2600:1900:4000:a2b2:0:0:0:0 [2600:1900:4000:a2b2::]... ? 17:43 [5732] connection to 4:80/1@fidonet failed: {W32 API
error 10060} Connection timed out
17:43 [324] the queue is empty, quitting...

This is going nowhere. I suggest we move this to the IPv6 echo.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)