• node entry with no pkt password

    From Louis Northmore@2:250/8 to All on Wednesday, January 10, 2024 18:28:32

    Hello everybody!

    What's the correct way to configure a link without a pkt password?
    Currently I have the following setup but doesn't let them connect:

    node 2:1/1@network address:24554 password,,password i

    Louis


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: SonicBBS :: sonicbbs.co.uk :: North Yorkshire, England (2:250/8)
  • From Mick Manning@1:229/307 to Louis Northmore on Wednesday, January 10, 2024 19:13:28
    On 10 Jan 2024, Louis Northmore said the following...

    What's the correct way to configure a link without a pkt password? Currently I have the following setup but doesn't let them connect:

    Hi. You have to arrange with your uplink as to if you need a PKT,or TIC password set, as well as the usual session password.

    Mick

    Mick Manning
    https://centralontarioremote.com
    telnet centralontarioremote.com:2300

    ... There's no present. There's only the immediate future and the recent past

    --- Mystic BBS v1.12 A49 2023/04/30 (Windows/32)
    * Origin: Central Ontario Remote Systems (1:229/307)
  • From Nil Alexandrov@2:5015/46 to Mick Manning on Thursday, January 11, 2024 03:45:24
    Hello, Mick!

    Wednesday January 10 2024 19:13, from Mick Manning -> Louis Northmore:

    What's the correct way to configure a link without a pkt
    password? Currently I have the following setup but doesn't let
    them connect:

    Hi. You have to arrange with your uplink as to if you need a PKT,or
    TIC password set, as well as the usual session password.

    No passport, no link. Pretty obviously, cause your files will end up in the non-password inbound aka unprotected, whatever it is called in husky.

    Best Regards, Nil
    --- GoldED+/LNX 1.1.5
    * Origin: Linux 2.6.32-042stab145.3 (2:5015/46)
  • From Wilfred van Velzen@2:280/464 to Louis Northmore on Thursday, January 11, 2024 09:47:20
    Hi Louis,

    On 2024-01-10 18:28:32, you wrote to All:

    What's the correct way to configure a link without a pkt password? Currently I have the following setup but doesn't let them connect:

    node 2:1/1@network address:24554 password,,password i

    You don't need to configure a pkt-password in your binkd config unless you are also using the 'share' option in your binkd.conf. And I very much doubt you are. The pkt-password in normally set (or not if not specified) by your tosser.

    And don't specify the default port.

    And you also don't need to specify the 'flavour' ("i"), unless you are using a filebox outbound directory for this node, which you haven't configured in this line, so leave it out.

    So the 'node' line would become:

    node 2:1/1@network host_address password



    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Mike Powell@1:2320/105 to WILFRED VAN VELZEN on Thursday, January 11, 2024 11:43:00
    And don't specify the default port.

    I have found that if my own system is not using the default port, it is
    best to specify it for systems that do.


    * SLMR 2.1a * War is God's way of teaching us geography.
    --- SBBSecho 3.14-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Wilfred van Velzen@2:280/464 to Mike Powell on Thursday, January 11, 2024 17:55:01
    Hi Mike,

    On 2024-01-11 11:43:00, you wrote to me:

    And don't specify the default port.

    I have found that if my own system is not using the default port, it is best to specify it for systems that do.

    Your current node is using BinkIT (on the default port), not binkd... ?


    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.0
    * Origin: FMail development HQ (2:280/464)
  • From Mike Powell@1:2320/105 to WILFRED VAN VELZEN on Friday, January 12, 2024 09:27:00
    And don't specify the default port.

    I have found that if my own system is not using the default port, it is best to specify it for systems that do.

    Your current node is using BinkIT (on the default port), not binkd... ?

    This system is, yes. 2320/107 is running binkd on a non-standard port. If I don't specify the default port, it will try to use the port that binkd is defined to on that system.

    Mike


    * SLMR 2.1a * A paid up computer is, by definition, obsolete.
    --- SBBSecho 3.14-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Tommi Koivula@2:221/1 to Mike Powell on Friday, January 12, 2024 20:19:34
    Hi Mike.

    12 Jan 24 09:27, you wrote to WILFRED VAN VELZEN:

    And don't specify the default port.

    I have found that if my own system is not using the default port, it is
    best to specify it for systems that do.

    Your current node is using BinkIT (on the default port), not binkd... ?

    This system is, yes. 2320/107 is running binkd on a non-standard port. If I
    don't specify the default port, it will try to use the port that binkd is defined to on that system.

    Have you changed "oport" in binkd.conf to some non-standard port? In that case you have to define :24554 if you want to poll standard binkp. ;)

    'Tommi

    --- GoldED+/LNX 1.1.5-b20231112
    * Origin: =-=---------------------------=-= (2:221/1)
  • From Wilfred van Velzen@2:280/464 to Mike Powell on Friday, January 12, 2024 19:25:56
    Hi Mike,

    On 2024-01-12 09:27:00, you wrote to me:

    And don't specify the default port.

    I have found that if my own system is not using the default port, it
    is
    best to specify it for systems that do.

    Your current node is using BinkIT (on the default port), not binkd... ?

    This system is, yes. 2320/107 is running binkd on a non-standard port. If
    I don't specify the default port, it will try to use the port that binkd is
    defined to on that system.

    You probably set both iport and oport in your binkd config, then the behaviour is as expected. While you only supposed to set the iport for incoming connections!


    This is translated from the russian docs, by google translate:

    4.27. iport

    The iport directive specifies the TCP port that will be opened by binkd to receive incoming connections. This directive can be used to set a non-standard port for binkd to run on, in particular to bypass the deny rules of a network gateway firewall.

    Parameter ? a positive integer or a string (the name of the port number from the /etc/services file in unix and c:\winnt\system32\drivers\etc\services in Windows NT and 2000, in c:\windows\system32\drivers\etc\ services in Windows XP and 2003). The default value is 24554.

    This directive is optional.

    Example:

    iport 24555


    4.41. oport

    The oport directive specifies the port on which binkd will try to establish a connection when the port for the link is not explicitly specified in the link's host address in the node line.

    Parameter ? a positive integer or a string (the name of the port number from the /etc/services file in unix and c:\winnt\system32\drivers\etc\services in Windows NT and 2000, in c:\windows\system32\drivers\etc\ services in Windows XP and 2003). The default value is 24554.

    This directive is optional.

    Example:

    oport 24555


    Bye, Wilfred.

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