• Update

    From Rick Smith@1:105/81 to All on Tue Jan 3 01:59:34 2023
    Hello All!

    I can get the hub to poll my bbs now, but my bbs still cant poll the hub, so I started my original setup backup and realized that the bbs still cant poll hub I must have never noticed. Here is what it looks like for a poll from bbs to hub,

    bp 1:105/81
    1:105/81
    .
    01:58 [1297] BEGIN, binkd/1.1a-112/Linux -p -P 1:105/81 /home/pi/fido/etc/binkd.cfg
    01:58 [1297] creating a poll for 1:105/81@fidonet (`d' flavour)
    01:58 [1297] clientmgr started
    $ od 1:105/81@fidonet (hold until 2023/01/03 02:01:18)
    01:58 [1297] the queue is empty, quitting...

    then ...

    bp 1:105/81
    1:105/81
    .
    02:01 [1320] BEGIN, binkd/1.1a-112/Linux -p -P 1:105/81 /home/pi/fido/etc/binkd.cfg
    02:01 [1320] creating a poll for 1:105/81@fidonet (`d' flavour)
    02:01 [1320] clientmgr started
    $ od 1:105/81@fidonet
    + 02:01 [1321] call to 1:105/81@fidonet
    02:01 [1321] trying hub.awesomenet.us [65.102.14.165]:24556...
    ? 02:01 [1321] connection to 1:105/81@fidonet failed: Connection refused
    02:01 [1320] rc(1321)=0
    02:01 [1320] the queue is empty, quitting...


    Regards,

    Rick

    ... Taglines: the <real< reason for BBSing.
    --- GoldED+/LNX 1.1.5-b20220504
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From Wilfred van Velzen@2:280/464 to Rick Smith on Tue Jan 3 12:45:20 2023
    Hi Rick,

    On 2023-01-03 01:59:34, you wrote to All:

    bp 1:105/81
    1:105/81
    .
    02:01 [1320] BEGIN, binkd/1.1a-112/Linux -p -P 1:105/81 /home/pi/fido/etc/binkd.cfg 02:01 [1320] creating a poll for 1:105/81@fidonet (`d' flavour) 02:01 [1320] clientmgr started $ od 1:105/81@fidonet + 02:01 [1321] call to 1:105/81@fidonet 02:01 [1321] trying hub.awesomenet.us [65.102.14.165]:24556... ? 02:01 [1321] connection
    to 1:105/81@fidonet failed: Connection refused 02:01 [1320]
    rc(1321)=0 02:01 [1320] the queue is empty, quitting...

    I'm seeing the same thing, when I try to poll him.

    2023-01-03 12:44:13.726 Nodelist for Tuesday, January 3, 2023 -- Day number 003 parsed, 1000 IP-nodes processed (0.013 sec)
    2023-01-03 12:44:28.811 Calling 1:105/81
    2023-01-03 12:44:28.811 hub.awesomenet.us:24556
    2023-01-03 12:44:28.811 (65.102.14.165:24556)
    2023-01-03 12:44:28.811 65.102.14.165 - Error: Connection timed out

    So the problem resides at your hub, not on your system.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: FMail development HQ (2:280/464)
  • From Richard Menedetter@2:310/31 to Rick Smith on Tue Jan 3 12:49:08 2023
    Hi Rick!

    03 Jan 2023 01:59, from Rick Smith -> All:

    02:01 [1321] connection to 1:105/81@fidonet failed: Connection refused

    The other side refuses your connection attempt.
    Either his firewall blocks you, or nothing is listening on the binkp port, or ...

    Check with the guy on the other side.
    It seems to be his problem, not yours.

    CU, Ricsi

    ... Some people cause happiness wherever they go; others, whenever they go.
    --- GoldED+/LNX
    * Origin: Ancient Chinese Curse: May all your wishes be granted. (2:310/31)
  • From Rick Smith@1:105/10 to Richard Menedetter on Tue Jan 3 08:46:06 2023
    Greetings Richard!

    Tuesday January 03 2023 12:49, you wrote to me about an urgent matter!:

    * Forwarded from area 'BINKD'
    Hi Rick!

    03 Jan 2023 01:59, from Rick Smith -> All:

    02:01 [1321] connection to 1:105/81@fidonet failed: Connection
    refused

    The other side refuses your connection attempt.
    Either his firewall blocks you, or nothing is listening on the binkp
    port, or ...

    Check with the guy on the other side.
    It seems to be his problem, not yours.

    I am the other guy, I run that hub its here on my network... Well so if its the hub ill start looking there.


    ----
    Regards,


    Rick Smith (Nitro)

    ... TAGLINE A BBS addict is hooked when: you consider BBSing better than chocolat
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)
  • From Rick Smith@1:105/10 to Wilfred van Velzen on Tue Jan 3 10:25:08 2023
    Greetings Wilfred!

    Tuesday January 03 2023 12:45, you wrote to me about an urgent matter!:

    * Forwarded from area 'BINKD'
    Hi Rick,

    On 2023-01-03 01:59:34, you wrote to All:

    bp 1:105/81
    1:105/81
    .
    02:01 [1320] BEGIN, binkd/1.1a-112/Linux -p -P 1:105/81
    /home/pi/fido/etc/binkd.cfg 02:01 [1320] creating a poll for
    1:105/81@fidonet (`d' flavour) 02:01 [1320] clientmgr started $
    od
    1:105/81@fidonet + 02:01 [1321] call to 1:105/81@fidonet 02:01
    [1321] trying hub.awesomenet.us [65.102.14.165]:24556... ? 02:01
    [1321] connection to 1:105/81@fidonet failed: Connection refused
    02:01 [1320] rc(1321)=0 02:01 [1320] the queue is empty,
    quitting...

    I'm seeing the same thing, when I try to poll him.

    2023-01-03 12:44:13.726 Nodelist for Tuesday, January 3, 2023 -- Day number 003 parsed, 1000 IP-nodes processed (0.013 sec) 2023-01-03 12:44:28.811 Calling 1:105/81 2023-01-03 12:44:28.811 hub.awesomenet.us:24556 2023-01-03 12:44:28.811
    (65.102.14.165:24556) 2023-01-03 12:44:28.811 65.102.14.165 - Error: Connection timed out

    Can you try again and report result? Thank you.



    ----
    Regards,


    Rick Smith (Nitro)

    ... JOIN THE ALL-CAPS BBS CLUB! THE WAY BBSING USED TO BE!
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)
  • From Richard Menedetter@2:310/31 to Rick Smith on Tue Jan 3 20:51:10 2023
    Hi Rick!

    03 Jan 2023 08:46, from Rick Smith -> Richard Menedetter:

    Check with the guy on the other side.
    It seems to be his problem, not yours.
    I am the other guy, I run that hub its here on my network... Well so
    if its the hub ill start looking there.

    Well that makes it very easy ;)
    Check the firewall logs, check that you can ping that host.
    Check that binkd is running and listening on the port that you think it should. Start up tcpdump and check what packets are exchanged.

    If both are behind the same NAT router, and you are using the EXTERNAL address it could be missing NAT loopback.
    In that case you can change the config to use internal addresses when trying to reach the other host.

    CU, Ricsi

    ... A bitch is a girl who will go to bed with anyone, except me.
    --- GoldED+/LNX
    * Origin: Ensign, engage warp drive. Ensign? ENSIGN, WAKE UP! (2:310/31)
  • From Wilfred van Velzen@2:280/464 to Rick Smith on Tue Jan 3 20:49:19 2023
    Hi Rick,

    On 2023-01-03 10:25:08, you wrote to me:

    I'm seeing the same thing, when I try to poll him.

    2023-01-03 12:44:13.726 Nodelist for Tuesday, January 3, 2023 -- Day
    number 003 parsed, 1000 IP-nodes processed (0.013 sec) 2023-01-03
    12:44:28.811 Calling 1:105/81 2023-01-03 12:44:28.811
    hub.awesomenet.us:24556 2023-01-03 12:44:28.811
    (65.102.14.165:24556) 2023-01-03 12:44:28.811 65.102.14.165 - Error:
    Connection timed out

    Can you try again and report result? Thank you.

    It works now:

    2023-01-03 20:48:33.549 Calling 1:105/81
    2023-01-03 20:48:33.549 hub.awesomenet.us:24556
    2023-01-03 20:48:33.549 (65.102.14.165:24556)
    2023-01-03 20:48:33.549 OPT CRAM-MD5-354a24f7c0e66de7128370cf3dc572ee 2023-01-03 20:48:33.549 SYS Awesome Net
    2023-01-03 20:48:33.549 ZYZ Rick Smith
    2023-01-03 20:48:33.549 LOC Portland, Oregon
    2023-01-03 20:48:33.549 NDL 115200,TCP,BINKP
    2023-01-03 20:48:33.549 TIME Tue, 3 Jan 2023 11:48:33 -0800
    2023-01-03 20:48:33.549 VER binkd/1.1a-115/Linux binkp/1.1
    2023-01-03 20:48:33.549 address: 1:105/81@fidonet
    2023-01-03 20:48:33.549 address: 1:105/0@fidonet
    2023-01-03 20:48:33.549 OPT EXTCMD GZ BZ2
    2023-01-03 20:48:33.549 65.102.14.165 - Ok.
    2023-01-03 20:48:33.549 Session with 1:105/81 done.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: FMail development HQ (2:280/464)