Mike Powell
2023-12-21 11:45:45 UTC
I have two nodes set up with the outbox option on:
node 1:229/***@fidonet darkrealms.ca:24554 mypassword i /path/to/outbox
node 21:1/***@fsxnet agency.bbs.nz:24557 mypassword i /path/to/outbox
When binkd attempts a call out, it does not use the binkd port included in the
address in the config:
14:39 [14990] BEGIN, binkd/1.1a-99/Linux -C /sbbs/binkd.cfg
14:39 [14990] servmgr started
- 14:39 [14990] servmgr listen on *:24556
14:39 [14991] clientmgr started
$ -i 21:1/***@fsxnetn
+ 14:39 [14992] call to 21:1/***@fsxnet
14:39 [14992] trying agency.bbs.nz [103.193.138.76]:0...
It instead uses '0' and the call eventually fails. It only does this with the
two nodes that have the outbox option selected. Is this issue fixed in
versions later than 1.1a-99, or do I have something set up wrong? Thanks!
Mike
#
node 1:229/***@fidonet darkrealms.ca:24554 mypassword i /path/to/outbox
node 21:1/***@fsxnet agency.bbs.nz:24557 mypassword i /path/to/outbox
When binkd attempts a call out, it does not use the binkd port included in the
address in the config:
14:39 [14990] BEGIN, binkd/1.1a-99/Linux -C /sbbs/binkd.cfg
14:39 [14990] servmgr started
- 14:39 [14990] servmgr listen on *:24556
14:39 [14991] clientmgr started
$ -i 21:1/***@fsxnetn
+ 14:39 [14992] call to 21:1/***@fsxnet
14:39 [14992] trying agency.bbs.nz [103.193.138.76]:0...
It instead uses '0' and the call eventually fails. It only does this with the
two nodes that have the outbox option selected. Is this issue fixed in
versions later than 1.1a-99, or do I have something set up wrong? Thanks!
Mike
#