node entry with no pkt password

[Louis Northmore]

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/***@network address:24554 password,,password i

Louis

[Mick Manning]

On 10 Jan 2024, Louis Northmore said the following...

LN> What's the correct way to configure a link without a pkt password?
LN> 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

[Nil Alexandrov]

Hello, Mick!

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

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

MM> Hi. You have to arrange with your uplink as to if you need a PKT,or
MM> 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

[Wilfred van Velzen]

Hi Louis,

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

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

LN> node 2: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/***@network host_address password



Bye, Wilfred.

[Mike Powell]

Post by 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.


* SLMR 2.1a * War is God's way of teaching us geography.

[Wilfred van Velzen]

Hi Mike,

Post by Wilfred van Velzen
And don't specify the default port.

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

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


Bye, Wilfred.

[Mike Powell]

Post by Wilfred van Velzen

Post by Wilfred van Velzen
And don't specify the default port.

MP> I have found that if my own system is not using the default port, it is
MP> 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.

[Tommi Koivula]

Hi Mike.

Post by Wilfred van Velzen

Post by Wilfred van Velzen
And don't specify the default port.

MP> I have found that if my own system is not using the default port, it
MP> is
MP> best to specify it for systems that do.
Your current node is using BinkIT (on the default port), not binkd... ?

MP> This system is, yes. 2320/107 is running binkd on a non-standard port.
MP> If I
MP> don't specify the default port, it will try to use the port that binkd is
MP> 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

[Wilfred van Velzen]

Hi Mike,

Post by Wilfred van Velzen

Post by Wilfred van Velzen
And don't specify the default port.

MP> I have found that if my own system is not using the default port, it is
MP> best to specify it for systems that do.
Your current node is using BinkIT (on the default port), not binkd... ?

MP> This system is, yes. 2320/107 is running binkd on a non-standard port.
MP> If
MP> I don't specify the default port, it will try to use the port that binkd
MP> is
MP> 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.