Would someone try to connect to binkd on the standard port using IPv6? Any one of these addresses should work:

bbs.quinnnet.org
binkd6.quinnnet.org
binkd6.us99.us

Thanks!

73 de W6RAY Ray Quinn
Visalia, CA DM06II
Ham Shack Hotline 4655


--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Ray's Road Node | Somewhere in California. (1:214/23)

*** Quoting Ray Quinn from a message to All ***

Would someone try to connect to binkd on the standard port using
IPv6?

Seems to work from here:

22:10 [269083] BEGIN, binkd/1.1a-115/Linux -vpP 1:214/22 binkd.cfg
22:10 [269083] creating a poll for 1:214/22@fidonet (`d' flavour)
22:10 [269083] clientmgr started
$ -d 1:214/22@fidonet
+ 22:10 [269084] call to 1:214/22@fidonet
22:10 [269084] trying binkd6.quinnnet.org [2001:470:1f04:8c6::2]...
22:10 [269084] connected
+ 22:10 [269084] outgoing session with binkd6.quinnnet.org:24554 [2001:470:1f04:8c6::2]
- 22:10 [269084] OPT CRAM-MD5-465f8910a99dc30994a52b33783a4618 CRYPT
+ 22:10 [269084] Remote requests MD mode
+ 22:10 [269084] Remote requests CRYPT mode
- 22:10 [269084] SYS US 99 BBS
- 22:10 [269084] ZYZ Ray Quinn
- 22:10 [269084] LOC Visalia, CA
- 22:10 [269084] NDL 115200,TCP,BINKP
- 22:10 [269084] TIME Fri Jul 29 2022 19:10:22 GMT-0700 (PDT)
- 22:10 [269084] VER BinkIT/2.41,JSBinkP/4,sbbs3.19c/Linux binkp/1.1
+ 22:10 [269084] addr: 1:214/22@fidonet
+ 22:10 [269084] addr: 1:214/0@fidonet
+ 22:10 [269084] addr: 1:214/1@fidonet
+ 22:10 [269084] addr: 9:91/2@survnet (n/a or busy)
+ 22:10 [269084] addr: 24:160/1@sportnet (n/a or busy)
+ 22:10 [269084] addr: 24:160/0@sportnet (n/a or busy)
+ 22:10 [269084] addr: 24:160/22@sportnet (n/a or busy)
+ 22:10 [269084] addr: 64:500/22@cnet (n/a or busy)
+ 22:10 [269084] addr: 110:214/1@linuxnet (n/a or busy)
+ 22:10 [269084] addr: 110:214/0@linuxnet (n/a or busy)
+ 22:10 [269084] addr: 111:6100/1@stn (n/a or busy)
+ 22:10 [269084] addr: 111:6100/0@stn (n/a or busy)
+ 22:10 [269084] addr: 111:6000/0@stn (n/a or busy)
+ 22:10 [269084] addr: 314:314/45@pinet (n/a or busy)
+ 22:10 [269084] addr: 432:1/108@vkradio (n/a or busy)
+ 22:10 [269084] addr: 510:291/0@justaxne (n/a or busy)
+ 22:10 [269084] addr: 510:291/7@justaxne (n/a or busy)
+ 22:10 [269084] addr: 618:300/18@micronet
+ 22:10 [269084] addr: 801:1/108@rdwxnet (n/a or busy)
+ 22:10 [269084] addr: 900:104/3176@rmininet (n/a or busy)
+ 22:10 [269084] done (to 1:214/22@fidonet, OK, S/R: 0/0 (0/0 bytes))
22:10 [269084] session closed, quitting...
22:10 [269083] rc(269084)=0
22:10 [269083] the queue is empty, quitting...


Jay

... The world looks as if it has been left in the custody of trolls

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms/TG ì tg.nrbbs.net ì Binbrook, ON (1:229/664.1)

Good ${greeting_time}, Ray!

28 Jul 2022 19:47:16, you wrote to All:

Would someone try to connect to binkd on the standard port using
IPv6? Any one of these addresses should work:
bbs.quinnnet.org binkd6.quinnnet.org binkd6.us99.us

Connection successful, got an answer from some broken binkp implementation.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... god@universe:~ # cvs up && make world
--- /bin/vi
* Origin: ::1 (2:5020/545)

Hi Alexey,

On 2022-07-30 13:41:42, you wrote to Ray Quinn:

Would someone try to connect to binkd on the standard port using
IPv6? Any one of these addresses should work:
bbs.quinnnet.org binkd6.quinnnet.org binkd6.us99.us

Connection successful, got an answer from some broken binkp implementation.

What is broken about it? I get binkit (synchronet) on the line. My binkd usually has no problem exchanging mail with those...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Travis,

It works:

+ 08:44 [3884] call to 1:134/303@fidonet
08:44 [3884] trying bbs.canerduh.com
[2604:3d09:227b:26af:19:a08b:78ab:5e16]...
08:44 [3884] connected
+ 08:44 [3884] outgoing session with bbs.canerduh.com:24554
[2604:3d09:227b:26af:19:a08b:78ab:5e16]
- 08:44 [3884] OPT CRAM-MD5-0ae3e0f7a0e74036f32f65f3f3d09d2c
+ 08:44 [3884] Remote requests MD mode
- 08:44 [3884] SYS CaNerDUH BBS
- 08:44 [3884] LOC CaNerDUH
- 08:44 [3884] ZYZ The Blade
- 08:44 [3884] TIME Tue, 06 Jun 2023 00:44:04 -0600
- 08:44 [3884] VER Mystic/1.12A48 binkp/1.0
- 08:44 [3884] BUILD 2023/01/15 12:54:07 Raspberry Pi/32
+ 08:44 [3884] addr: 1:134/303@fidonet
+ 08:44 [3884] addr: 21:4/151@fsxnet (n/a or busy)
+ 08:44 [3884] addr: 420:1/11@weednet (n/a or busy)
- 08:44 [3884] QSIZE 0 files 0 bytes
+ 08:44 [3884] done (to 1:134/303@fidonet, OK, S/R: 0/0 (0/0 bytes))

Travis, welcome to the Fidonet IPv6 club!


Cheers, Michiel

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

Travis, welcome to the Fidonet IPv6 club!

Thank you very much! It seems that OPNsense has a few minor issues with IPv6 causing it to lose IPv6 connectivity intermittently. At least now with my kids having Disney+ on our Fire Stick (which defaults to IPv6 when available) I notice pretty quickly when it stops working and can usually get it back up before I lose my current /64 and have to redo all my DNS records again.

Supposedly the latest update for IPv6 has some fixes for this issue so fingers crossed it won't be a problem anymore once I have the chance to upgrade.

Also, apologies for the alias on my other message, the settings for this echo should be fixed now.

Travis

... When cheese gets its picture taken, what does it say?

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: CaNerDUH BBS (1:134/303)