I can't help thinking it shouldn't be this hard. Can anyone tell me what totally obvious thing I'm missing? :-)
I built a fresh husky a week ago following the instructions here..
https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc
https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc
HPT, and the other Husky tools...
For those who are using them on Linux (intel), did you install pre-built binaries, or did you manage to build from sources?
So I run Hub 3 with binkd and hpt - all in a docker container.
You are welcome to use that container - or look at my build (Dockerfile) here: https://dev.leenooks.net/bbs/fidohub
The runner has the build output if that helps.
here: https://dev.leenooks.net/bbs/fidohub
The runner has the build output if that helps.
I'll definitely take a look at that after work - I'll most likely run it natively, but there will be many useful pointers in the way you've got it all set up I'm sure.
Sending a netmail to 1337:2/100, binkd tries to call 1337:2/100@fsxnet...
I assume it's defaulting to fsxnet, since that's first listed in my binkd config file.
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
Presumably this is why it doesn't match the node line for 1337:2/100?
I note that for Fidonet, I could specify a root-domain (binkp.net typically) on the node line and it'll do the FTN to hostname resolution that way. I haven't seen evidence of a root-domain I can use for fsxnet or tqwnet...
I don't have the Perl nodelist stuff setup for binkd at the moment - is that the fix?
Am I wrong in assuming I should be able to send netmail to a node listed in a node line without needing a binkp.net style lookup or nodelist?
node 21:3/100 -4 n3.z21.bbs.leenooks.net:24554 pass,pass,pass -
node 1337:2/100 -4 n2.z1337.bbs.leenooks.net:24554 pass,pass,pass -
I note that for Fidonet, I could specify a root-domain (binkp.net typically) on the node line and it'll do the FTN to hostname resolution that way. I haven't seen evidence of a root-domain I can use for fsxnet or tqwnet...
I don't have the Perl nodelist stuff setup for binkd at the moment - is that the fix?
Am I wrong in assuming I should be able to send netmail to a node listed in a node line without needing a binkp.net style lookup or nodelist?
Sending a netmail to 1337:2/100, binkd tries to call
1337:2/100@fsxnet...
It is the tosser that prepares the netmail to be sent, so I would look there and also check your golded.cfg (if you use that).
Presumably this is why it doesn't match the node line for 1337:2/100?
Actually that will work with binkd although you tosser needs to support 5D also.
I note that for Fidonet, I could specify a root-domain (binkp.net
typically) on the node line and it'll do the FTN to hostname resolution
that way. I haven't seen evidence of a root-domain I can use for fsxnet
or tqwnet...
binkd will use binkp.net by default. There is another for fsxnet that Avon setup but I forget the details ATM.
I don't have the Perl nodelist stuff setup for binkd at the moment - is
that the fix?
No, perl doesn't come into this.
Am I wrong in assuming I should be able to send netmail to a node
listed
in a node line without needing a binkp.net style lookup or nodelist?
Yes, binkd will get node info from your node lines and use binkp.net otherwise if defnode is setup.
node 21:3/100 -4 n3.z21.bbs.leenooks.net:24554 pass,pass,pass -
node 1337:2/100 -4 n2.z1337.bbs.leenooks.net:24554 pass,pass,pass -
Try changing this to 21:3/100@fsxnet and 1337:2/100@tqwnet, and also make sure to include the domain in your address lines if you haven't already, e.g.:
address 21:3/169@fsxnet
address 1337:2/<your node number>@tqwnet
...to see if that makes any difference, as one blurb in the config
says
that:
# If the first address is specified as a 3D/4D address, its domain will be # taken from the domain defined in the first "domain" line. If more addresses # are specified as 3D/4D ones, their domain will be taken from the first # address.
The last part there might be why it "borrows" the fsxnet domain for your additional addresses (1337:2/<your node number>).
I have added "fsxnet.nz" to my config, although I see now that it
doesn't
seem to resolve my address:
host n202.n1.z21.fsxnet.nz
Host n202.n1.z21.fsxnet.nz not found: 3(NXDOMAIN)
Am I wrong in assuming I should be able to send netmail to a node
listed in a node line without needing a binkp.net style lookup or
nodelist?
Yes, I think so.
And if you want binkd to be able to send to any node (e.g. for crashmail), you would add something like:
defnode *
...at the end. But this of course requires that the root domain has been set for each network so that it can resolve the FTN address to an IP number.
Hope this helps!
It is the tosser that prepares the netmail to be sent, so I would
look there and also check your golded.cfg (if you use that).
I'm not seeing any trace of '@fsxnet' in the .cut file in the outbound directory, and the source/destination zone/net/node look to be right.
I looked here earlier and that's what led me to the conclusion it was probably binkd doing it..
I thought HPT did, but I may still have its config wrong...
Thanks for the suggestions - I will indeed go back through my GoldED &
HPT configurations, and do some comparisons between the packets that
get generated for fsxnet vs those for tqwnet to see what, if any,
obvious differences there are.
Tried that (but tried it again, just in case I pooched it up the first time). I didn't have any luck, but I'll do some more fiddling...
Has given me some pointers towards things to look at - muchly
appreciated.
As a sidenote, when I think of it, my outbound has one primary subdirectory
(fsxnet), and the others are adjacent to it:
# NOTE: Specifying a matching (21 = 21) default zone will cause the outbound # directory to become /mnt/bbs/echomail/out/fsxnet in
practice domain fsxnet /mnt/bbs/echomail/out/fsxnet 21 fsxnet.nz
# NOTE: Specifying a non-matching (21 != 2) default zone will cause the
# outbound directory to become /mnt/bbs/echomail/out/fidonet.002 in practice domain fidonet /mnt/bbs/echomail/out/fidonet 21 binkp.net
So, I specify 21 as the default domain for all my FTN networks, and
hence
get .<number> suffixes to the outbound directory names for all but fsxNet.
but I think your setup with one outbound with all in it (right?)
way but I couldn't find the required HPT directives to make HPT use the separate outbound directories. The documentation suggested it only supported Binkley-style outbound directories (so a base directory for
the primary zone, and .xxx hex encoded subdirectories for other zones).
Even though the outbound packets is in <path>.539/, binkd still thinks
it needs to place an outbound call to 1337:2/100@fsxnet, which I have no node line for because, well, it should be 1337:2/100@tqwnet (which I do have a node line for).
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
Still wondering a little about that 1337 there, as specifying it should make binkd believe that anything for zone 1337 shouldn't be placed in a directory named "outbound.1337", but rather in the directory named
...just so that you get a non-match (21 != 1337 and 999 != 1337) for the default zone specified on the domain line, so that binkd knows to look
for tqwnet things in the "outbound.1337" directory rather than in the
On 10 Jul 2022, TassieBob said the following...
way but I couldn't find the required HPT directives to make HPT use
the separate outbound directories. The documentation suggested it
only supported Binkley-style outbound directories (so a base directory
for the primary zone, and .xxx hex encoded subdirectories for other
zones).
OK! So no mention of domains (4D or even 5D) there?
Yep, sounds like binkd believes the "outbound.539" directory is for a different zone but for the same domain (fsxNet) then...
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
Did you try changing this to:
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 21
...or even something more apparent like:
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 999
default zone specified on the domain line, so that binkd knows to look
for
tqwnet things in the "outbound.1337" directory rather than in the "outbound" directory?
The old documentation reference link I have for this would be: https://web.archive.org/web/20171117081757/http://old.vk.pp.ru/docs/bi nkd/index .htm#config.domain
I believe this would be "Example 2".
This is interesting but intriguing stuff. :)
Update: Did this while I was typing the reply, and confirmed, binkd doesn't even look at outbound.539 when configured this way.
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
Still wondering a little about that 1337 there, as specifying it should make binkd believe that anything for zone 1337 shouldn't be placed in a directory named "outbound.1337", but rather in the directory named "outbound". Which would then collide with the fsxNet outbound (which also uses the "outbound" directory).
Did you try changing this to:
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 21
...or even something more apparent like:
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 999
...just so that you get a non-match (21 != 1337 and 999 != 1337) for the default zone specified on the domain line, so that binkd knows to look for tqwnet things in the "outbound.1337" directory rather than in the "outbound" directory?
Sending a netmail to 1337:2/100, binkd tries to call 1337:2/100@fsxnet...
I assume it's defaulting to fsxnet, since that's first listed in my binkd config file.
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
This helps binkd determine which outbound to put "other zone" mail in.
I assume it's defaulting to fsxnet, since that's first listed in my
binkd config file.
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
A trap that gets everybody :)
The number at the end (21 and 1337) is *not* the zone number for the domain, it is the zone number that this "outbound" represents.
having:
domain fsxnet /home/bbs/ftn/outbound 21, and
domain tqwnet /home/bbs/ftn/outbound 21
Means:
* /home/bbs/ftn/outbound is the path prefix for my outgoing mail
* zone 21 mail will go it it directly
* zone 1337 mail will go in it with the hex 539 appended (ie: /home/bbs/ftn/outbound.539
Hope that makes sense :)
Good news is YOU NAILED IT! I can send netmail for both zones now.
Using "the wrong" zone number on the subsequent entry is very
unintuitive, and seems to go against the examples further down in the
THANKYOU!
It does, but I still maintain the configuration is unintuitive :-)
It does, but I still maintain the configuration is unintuitive :-)
Re: HPT
By: TassieBob to tassiebob on Sun Jul 10 2022 04:48 pm
Sending a netmail to 1337:2/100, binkd tries to call
1337:2/100@fsxnet...
I assume it's defaulting to fsxnet, since that's first listed in my
binkd config file.
domain fsxnet /home/bbs/ftn/outbound 21
domain tqwnet /home/bbs/ftn/outbound 1337
A trap that gets everybody :)
The number at the end (21 and 1337) is *not* the zone number for the domain, it is the zone number that this "outbound" represents.
Its normal to use the same "outbound" for all your zones (/home/bbs/ftn/outbound) in your case, and the number on the end should
be what it represents by default. If that is zone 21, then *every* domain line should have 21 for each different domain.
The number at the end (21 and 1337) is *not* the zone number for the domain, it is the zone number that this "outbound"
represents.
Are your sure? If I create a poll for 21:3/100 binkd uses the zone number to figure out the domain.
domain fsxnet /home/bbs/ftn/outbound 21
Re: HPT
By: Oli to deon on Sat Jul 23 2022 08:25 am
The number at the end (21 and 1337) is *not* the zone number for
the domain, it is the zone number that this "outbound"
represents.
Are your sure? If I create a poll for 21:3/100 binkd uses the zone
number to figure out the domain.
Yes.
If you have:
domain fsxnet /home/bbs/ftn/outbound 21
Binkd knows to find any outbound files in /home/bbs/ftn/outbound for that zone, named 00030064.*
If you were sending to 22:3/100, then binkd would look in /home/bbs/ftn/outbound.016 named 00030064.*
It actually makes sense to me why it was implemented this way, but it
isnt an obvious conclusion for the newby.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,040 |
Nodes: | 15 (0 / 15) |
Uptime: | 57:24:37 |
Calls: | 500,215 |
Calls today: | 16 |
Files: | 95,197 |
D/L today: |
1,060 files (169M bytes) |
Messages: | 466,117 |