• Uplinks

    From Joe Schweier@1:342/200 to All on Sun Oct 14 21:32:20 2018
    Okay, I have my binkd running. I was having issues with domains... I used the stock domains, for the most part... slight alterations.

    I need some help with adding in nodes or uplinks in my binkd.cfg file...

    What do I need to add there...

    Thanx
    Joe

    ---
    * Origin: Joe's Mail System 1:342/200 -=joesbbs.com=- (1:342/200)
  • From Joacim Melin@2:201/120 to Joe Schweier on Mon Oct 15 06:49:16 2018
    Okay, I have my binkd running. I was having issues with domains... I
    used the stock domains, for the most part... slight alterations.

    I need some help with adding in nodes or uplinks in my binkd.cfg
    file...

    What do I need to add there...



    Here's from my config. Your paths and network names may vary...

    domain fidonet /fido/outbound 2
    domain amiganet /fido/amiganet 2
    domain fsxnet /fido/fsxnet 2

    address 2:201/120@fidonet
    address 39:160/242@amiganet
    address 21:2/130@fsxnet

    My upstream fidonet hub:

    node 2:201/0.0@fidonet <hostname or IP>:<port> <password>

    For example:

    node 2:201/0@fidonet bejo.dyndns.org:9090 oursecretpassword

    Binkd understands to send the right mail to the right hub via the @domain value
    (specified earlier in the config file, see above) so if you have FSXNet for example, you enter it like this:

    node 21:2/100@fsxnet error404bbs.ddns.net:24555 oursecretpassword

    The routing itself is done by the tosser software. I use Crashmail II for this and I tell it that all packages for 21:*/*.* will go to 21:2/100 and then Binkd
    will pick that up and send it to 21:2/100.


    --- NiKom v2.5.0dev
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Richard Menedetter@2:310/31 to Joe Schweier on Mon Oct 15 20:45:14 2018
    Hi Joe!

    14 Oct 2018 21:32, from Joe Schweier -> All:

    I need some help with adding in nodes or uplinks in my binkd.cfg
    file...
    What do I need to add there...

    It is documented in the default config file.
    Add something like this:
    node a:b/c@domain FQDN password i

    CU, Ricsi

    ... Mr. Garrison, why do poor people always smell like sour milk? -Cartman
    --- GoldED+/LNX
    * Origin: A dirty book is rarely dusty ;) (2:310/31)
  • From Joe Schweier@1:342/200 to Joacim Melin on Mon Oct 15 17:59:26 2018
    Okay, I have my binkd running. I was having issues with domains... I
    used the stock domains, for the most part... slight alterations.

    I need some help with adding in nodes or uplinks in my binkd.cfg
    file...

    What do I need to add there...



    Here's from my config. Your paths and network names may
    vary...

    domain fidonet /fido/outbound 2
    domain amiganet /fido/amiganet 2
    domain fsxnet /fido/fsxnet 2

    address 2:201/120@fidonet
    address 39:160/242@amiganet
    address 21:2/130@fsxnet

    My upstream fidonet hub:

    node 2:201/0.0@fidonet <hostname or IP>:<port> <password>

    For example:

    node 2:201/0@fidonet bejo.dyndns.org:9090
    oursecretpassword

    Binkd understands to send the right mail to the right hub
    via the @domain value (specified earlier in the config
    file, see above) so if you have FSXNet for example, you
    enter it like this:

    node 21:2/100@fsxnet error404bbs.ddns.net:24555
    oursecretpassword

    The routing itself is done by the tosser software. I use
    Crashmail II for this and I tell it that all packages for
    21:*/*.* will go to 21:2/100 and then Binkd will pick
    that up and send it to 21:2/100.

    I have things setup, a lot like yours, but mail doesn't seem to send to the BBS.

    Before I made changes to the binkd.cfg file mail would transfer over.... As soon as I personalized it mail does not transfer... Here's my Internet Rex Log

    :Star
    ---------- Manual fetch: 201
    % 17:52:16 (3) Starting event.
    % 17:52:16 (3) Done.
    - 17:52:16 (1) Performing inbound mail scan.
    % 17:52:16 (1) Starting thread 0 (4, 1, 25150)
    % 17:52:16 (5) Connecting to BinkP site 192.168.0.10...
    % 17:52:16 (5) BinkP: OPT CRAM-MD5-9409d5d28835c94d447cada60594c3ee
    % 17:52:17 (5) BinkP: SYS Joe's BBS
    % 17:52:17 (5) BinkP: ZYZ IB JOE
    % 17:52:17 (5) BinkP: LOC Edmonton, AB Canada
    % 17:52:17 (5) BinkP: NDL 115200,TCP,BINKP
    % 17:52:17 (5) BinkP: TIME Mon, 15 Oct 2018 17:52:15 -0600
    % 17:52:17 (5) BinkP: VER binkd/1.0.4/Linux binkp/1.1
    % 17:52:17 (5) BinkP: 1:342/201.1@fidonet
    ? 17:52:17 (5) BinkP error from remote: Secure AKA 1:342/200@fidonet busy
    % 17:52:17 (1) Task 0 is done.
    * 17:52:17 (1) Received 0 files (0K)
    % 17:52:17 (1) System: BETWEEN.CMD
    :Stop

    Why would 1:342/200@fidonet is busy... The 200 address is the internet rex machine whereas 201 is the binkd machine...

    Is there a flag or semaphore that is active??

    Thanx
    Joe

    ---
    * Origin: Joe's Mail System 1:342/200 -=joesbbs.com=- (1:342/200)
  • From Joacim Melin@2:201/120 to Joe Schweier on Tue Oct 16 06:32:37 2018
    Okay, I have my binkd running. I was having issues with domains... I
    used the stock domains, for the most part... slight alterations.

    I need some help with adding in nodes or uplinks in my binkd.cfg
    file...

    What do I need to add there...



    Here's from my config. Your paths and network names may
    vary...

    domain fidonet /fido/outbound 2
    domain amiganet /fido/amiganet 2
    domain fsxnet /fido/fsxnet 2

    address 2:201/120@fidonet
    address 39:160/242@amiganet
    address 21:2/130@fsxnet

    My upstream fidonet hub:

    node 2:201/0.0@fidonet <hostname or IP>:<port> <password>

    For example:

    node 2:201/0@fidonet bejo.dyndns.org:9090
    oursecretpassword

    Binkd understands to send the right mail to the right hub
    via the @domain value (specified earlier in the config
    file, see above) so if you have FSXNet for example, you
    enter it like this:

    node 21:2/100@fsxnet error404bbs.ddns.net:24555
    oursecretpassword

    The routing itself is done by the tosser software. I use
    Crashmail II for this and I tell it that all packages for
    21:*/*.* will go to 21:2/100 and then Binkd will pick
    that up and send it to 21:2/100.

    I have things setup, a lot like yours, but mail doesn't seem to send
    to the BBS.

    Before I made changes to the binkd.cfg file mail would transfer
    over.... As soon as I personalized it mail does not transfer...
    Here's my Internet Rex Log

    :Star
    ---------- Manual fetch: 201
    % 17:52:16 (3) Starting event.
    % 17:52:16 (3) Done.
    - 17:52:16 (1) Performing inbound mail scan.
    % 17:52:16 (1) Starting thread 0 (4, 1, 25150)
    % 17:52:16 (5) Connecting to BinkP site 192.168.0.10...
    % 17:52:16 (5) BinkP: OPT CRAM-MD5-9409d5d28835c94d447cada60594c3ee
    % 17:52:17 (5) BinkP: SYS Joe's BBS
    % 17:52:17 (5) BinkP: ZYZ IB JOE
    % 17:52:17 (5) BinkP: LOC Edmonton, AB Canada
    % 17:52:17 (5) BinkP: NDL 115200,TCP,BINKP
    % 17:52:17 (5) BinkP: TIME Mon, 15 Oct 2018 17:52:15 -0600
    % 17:52:17 (5) BinkP: VER binkd/1.0.4/Linux binkp/1.1
    % 17:52:17 (5) BinkP: 1:342/201.1@fidonet
    ? 17:52:17 (5) BinkP error from remote: Secure AKA 1:342/200@fidonet
    busy
    % 17:52:17 (1) Task 0 is done.
    * 17:52:17 (1) Received 0 files (0K)
    % 17:52:17 (1) System: BETWEEN.CMD
    :Stop

    Why would 1:342/200@fidonet is busy... The 200 address is the
    internet rex machine whereas 201 is the binkd machine...

    Is there a flag or semaphore that is active?

    You sure it's not supposed to be 1:342/201.0?


    --- NiKom v2.5.0dev
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Joe Schweier@1:342/200 to Joacim Melin on Tue Oct 16 05:07:38 2018

    % 17:52:16 (3) Done.
    - 17:52:16 (1) Performing inbound mail scan.
    % 17:52:16 (1) Starting thread 0 (4, 1, 25150)
    % 17:52:16 (5) Connecting to BinkP site 192.168.0.10...
    % 17:52:16 (5) BinkP: OPT CRAM-MD5-9409d5d28835c94d447cada60594c3ee
    % 17:52:17 (5) BinkP: SYS Joe's BBS
    % 17:52:17 (5) BinkP: ZYZ IB JOE
    % 17:52:17 (5) BinkP: LOC Edmonton, AB Canada
    % 17:52:17 (5) BinkP: NDL 115200,TCP,BINKP
    % 17:52:17 (5) BinkP: TIME Mon, 15 Oct 2018 17:52:15 -0600
    % 17:52:17 (5) BinkP: VER binkd/1.0.4/Linux binkp/1.1
    % 17:52:17 (5) BinkP: 1:342/201.1@fidonet
    ? 17:52:17 (5) BinkP error from remote: Secure AKA 1:342/200@fidonet
    busy
    % 17:52:17 (1) Task 0 is done.
    * 17:52:17 (1) Received 0 files (0K)
    % 17:52:17 (1) System: BETWEEN.CMD
    :Stop

    Why would 1:342/200@fidonet is busy... The 200 address is the
    internet rex machine whereas 201 is the binkd machine...

    Is there a flag or semaphore that is active?

    You sure it's not supposed to be 1:342/201.0?

    I have 2 addresses. One is 1:342/200, a hub address, I want incoming mail going there. I have an OS/2 Box there to receive that mail.... From there I have a Pi box that runs a BBS and it's address 1:342/201.

    Before I go public I'm trying to send mail from the OS/2 bvox to the Pi box amd
    I cannot seem to do this.

    They connect, at least now, but mail is not sent...

    :(

    Thanx
    Joe

    ---
    * Origin: Joe's Mail System 1:342/200 -=joesbbs.com=- (1:342/200)
  • From Michiel van der Vlist@2:280/5555 to Joe Schweier on Tue Oct 16 13:28:13 2018
    Hello Joe,

    On Tuesday October 16 2018 05:07, you wrote to Joacim Melin:

    Before I go public I'm trying to send mail from the OS/2 bvox to the
    Pi box amd I cannot seem to do this.

    They connect, at least now, but mail is not sent...

    There is probably a *.bsy flag left because of an irregular shutdown. Remove all *.bsy flags from the outbound and try adding this to the binkd config:

    kill-old-partial-files 20000
    kill-old-bsy 20000


    Cheers, Michiel


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Ward Dossche@2:292/854 to Joe Schweier on Tue Oct 16 15:00:38 2018

    They connect, at least now, but mail is not sent...

    Maybe a busy file ... this is what I run upon booting binkd:

    DEL C:\BINKD\OUTBOUND\*.BSY
    DEL C:\BINKD\OUTBOUND\*.CST
    DEL C:\BINKD\OUTBOUND\*.HLD
    DEL C:\BINKD\OUTBOUND\*.TRY
    DEL C:\BINKD\OUTBOUND.001\*.BSY
    DEL C:\BINKD\OUTBOUND.001\*.CST
    DEL C:\BINKD\OUTBOUND.001\*.HLD
    DEL C:\BINKD\OUTBOUND.001\*.TRY
    DEL C:\BINKD\OUTBOUND.003\*.BSY
    DEL C:\BINKD\OUTBOUND.003\*.CST
    DEL C:\BINKD\OUTBOUND.003\*.HLD
    DEL C:\BINKD\OUTBOUND.003\*.TRY
    DEL C:\BINKD\OUTBOUND.004\*.BSY
    DEL C:\BINKD\OUTBOUND.004\*.CST
    DEL C:\BINKD\OUTBOUND.004\*.HLD
    DEL C:\BINKD\OUTBOUND.004\*.TRY

    C:
    CD \BINKD
    BINKDWIN BINKD.CFG -cs

    --- D'Bridge 3.99 SR33
    * Origin: A man's most proud moment is when he takes a shit (2:292/854)
  • From Wilfred van Velzen@2:280/464 to Ward Dossche on Tue Oct 16 15:46:08 2018
    Hi Ward,

    On 2018-10-16 15:00:38, you wrote to Joe Schweier:

    Maybe a busy file ... this is what I run upon booting binkd:

    DEL C:\BINKD\OUTBOUND\*.BSY
    DEL C:\BINKD\OUTBOUND\*.CST

    Shouldn't that be *.CSY ?
    CST isn't defined as a file extension in the BSO standard, afaik.

    DEL C:\BINKD\OUTBOUND\*.HLD
    DEL C:\BINKD\OUTBOUND\*.TRY

    TRY files just contain the status of the last connect. So they don't do anything. But they will remain forever for every node you ever had a connection
    with. So it doesn't hurt to clean them up once in a while...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Ward Dossche@2:292/854 to Wilfred van Velzen on Tue Oct 16 16:48:33 2018

    Kees,

    Shouldn't that be *.CSY ?
    CST isn't defined as a file extension in the BSO standard, afaik.

    Yes, of course.

    \%/@rd

    --- D'Bridge 3.99 SR33
    * Origin: A man's most proud moment is when he takes a shit (2:292/854)