• binkd on Raspberry Pi

    From eggy@21:4/143 to All on Sunday, March 01, 2020 11:51:09
    So.. I've been trying to get binkd to work on my rPI, using a point instead
    of requesting another node and I'm having no joy in doing so. Below is my binkd.conf

    # Number @ end is the root zone
    domain fsxnet /home/e/bbs/ftn_out 21

    #fsxNet address
    address 21:1/143.1@fsxnet
    .......
    #Primary HUB
    node 21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c ---------------------------------------------------------

    When I try to poll, using the following command:

    /usr/local/sbin/binkd -p -P 21:1/143@fsxnet /home/e/binkd.conf

    I get the following errors:
    11:37 [31698] BEGIN, binkd/1.1a-101/Linux -p -P 21:1/143@fsxnet /home/e/binkd.conf
    11:37 [31698] creating a poll for 21:1/143@fsxnet (`d' flavour)
    11:37 [31698] clientmgr started
    $ -d 21:1/143@fsxnet
    + 11:37 [31699] call to 21:1/143@fsxnet
    + 11:37 [31699] getaddrinfo failed: Name or service not known (-2)
    11:37 [31698] rc(31699)=0
    11:37 [31698] the queue is empty, quitting...

    Any help would be appreciated (password has been censored in this example).. From a networking side, I'm able to resolve my dns and I've also tried this using an IP address directly.. I'm getting the same errors.

    Thanks,
    Matt // eggy
    Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
    fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Eggy BBS (21:4/143)
  • From Netsurge@21:4/154 to eggy on Sunday, March 01, 2020 12:59:26
    node 21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c

    You don't need :24554 as it is the default port for the binkp protocol. Try
    it without it and make sure you can ping bbs.eggy.cc from your pi.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From Bucko@21:4/131 to eggy on Sunday, March 01, 2020 12:59:29
    On 01 Mar 2020, eggy said the following...

    # Number @ end is the root zone
    domain fsxnet /home/e/bbs/ftn_out 21


    Not being an expert on binkd (Far from it I might add) but try adding quotes around the /home and close them after ftn_out

    domain fsxnet "/home/e/bbs/ftn_out" 21

    Probably wrong but it's worth a try as that is how I have my domains setup..

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From Al@21:4/106 to eggy on Sunday, March 01, 2020 10:19:00
    Hello eggy,

    /usr/local/sbin/binkd -p -P 21:1/143@fsxnet /home/e/binkd.conf

    That's a curious error. When I poll my boss I use the same command as you are using without @fsxnet. I wonder if that would make a difference.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From pokeswithastick@1:1/0 to eggy on Sunday, March 01, 2020 19:01:39

    On Mar 1st 6:00 pm eggy said...
    21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c

    On the pi does running

    telnet bbs.eggy.cc 24554

    work?





    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.16.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From eggy@21:4/143 to all on Sunday, March 01, 2020 14:38:12
    On 01 Mar 2020, pokeswithastick said the following...


    On Mar 1st 6:00 pm eggy said...
    21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c

    On the pi does running

    telnet bbs.eggy.cc 24554

    work?
    Yeah, telnet works... I've even tried without the port.. and I'm still getting the same error on my pi and my desktop running Linux.. I'm guessing there is something wrong with my binkd.conf, but google hasn't really helped me very much.. I've also confirmed my pi can resolve dns, so can my linux desktop.. It's a very puzzling error message..

    Thanks,
    Matt // eggy
    Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
    fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Eggy BBS (21:4/143)
  • From tenser@21:1/101 to eggy on Monday, March 02, 2020 09:47:52
    On 01 Mar 2020 at 02:38p, eggy pondered and said...

    Yeah, telnet works... I've even tried without the port.. and I'm still getting the same error on my pi and my desktop running Linux.. I'm guessing there is something wrong with my binkd.conf, but google hasn't really helped me very much.. I've also confirmed my pi can resolve dns,
    so can my linux desktop.. It's a very puzzling error message..

    Hmm. That error looks suspiciously like the error I
    got before I fixed the use-after-free bug in service
    resolution. However, it appears that your `binkd`
    is recent enough that it has my fix in it. Where'd
    you get it from, and when did you compile it?

    --- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From eggy@21:4/143 to tenser on Sunday, March 01, 2020 15:04:14
    Hmm. That error looks suspiciously like the error I
    got before I fixed the use-after-free bug in service
    resolution. However, it appears that your `binkd`
    is recent enough that it has my fix in it. Where'd
    you get it from, and when did you compile it?
    I compiled it yesterday from https://github.com/pgul/binkd.git
    Is there a more recent fork I should be using?

    Thanks,
    Matt // eggy
    Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
    fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Eggy BBS (21:4/143)
  • From pokeswithastick@1:1/0 to eggy on Sunday, March 01, 2020 21:02:45
    I followed NuSkooler's instructions with my set up which seems to work fine on a raspberry pi. Did you compile from source?

    http://l33t.codes/enigma-12-binkd-on-centos-7

    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.16.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From eggy@21:4/143 to all on Sunday, March 01, 2020 15:58:57
    On 01 Mar 2020, eggy said the following...

    Hmm. That error looks suspiciously like the error I
    got before I fixed the use-after-free bug in service
    resolution. However, it appears that your `binkd`
    is recent enough that it has my fix in it. Where'd
    you get it from, and when did you compile it?
    I compiled it yesterday from https://github.com/pgul/binkd.git
    Is there a more recent fork I should be using?
    I've done a bit more testing, I built this code on my Linux desktop and this version of binkd works (I got a password error, which I expected to get). Whatever this particular issue is, seems specific to the raspberry pi (raspbian).

    Thanks,
    matt // eggy
    Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
    fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Eggy BBS (21:4/143)
  • From Al@21:1/100 to eggy on Sunday, March 01, 2020 14:02:34
    Hello eggy,

    I've done a bit more testing, I built this code on my Linux desktop
    and this version of binkd works (I got a password error, which I
    expected to get). Whatever this particular issue is, seems specific to
    the raspberry pi (raspbian).

    I've encountered that error before but I forget now what the problem or solution was. I'll import my binkd.conf below for you to compare if you like. I'll remove most of my node lines. Not sure if it'll help or not..


    === Cut ===
    # Binkd sample configuration file
    # Copyright (C) 1996-1997 by Dima Maloff, 2:5047/13
    # $Id: binkd.conf,v 1.3 2012/01/22 13:54:12 green Exp $

    #
    # Path and name for the logfile, loglevel
    #
    log /usr/local/fido/log/binkd.log
    loglevel 4

    #
    # Your FTN domains:
    # domain <name> <main-outbound> <default-zone> [<root-domain>]
    # or
    # domain <new-name> alias-for <name>
    # First specified domain sets as default domain for the 3D/4D addresses.
    #
    domain fidonet /usr/local/fido/outbound 1
    domain fsxnet /usr/local/fido/outbound 1
    domain gamenet /usr/local/fido/outbound 1
    #
    # Aliases to support known wrong 5D configurations
    domain fido alias-for fidonet
    domain fidorus alias-for fidonet
    domain fido7 alias-for fidonet
    #
    # Aliases to support known DNS domain zones
    # (some people is mix up the terms "FTN domain" and "DNS internet domain") domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet


    #
    # Your addresses, 5D or 4D or 3D:
    # address <addr1> ...
    # If first address specified as 3D/4D then domain for it sets from domain
    # defined in the first "domain" token. If second and more addresses specified
    # as 3D/4D then domain sets from first address.
    #
    address 1:153/757@fidonet
    address 1:153/0@fidonet
    address 21:4/106@fsxnet
    address 32:1/5@gamenet

    #
    # Hide or present the specified AKAs if remote AKAs match the address mask
    # hide-aka <my-aka> [!]<mask>
    # present-aka <add-aka> [!]<mask>
    # Mask is compared to the 5d-form of address string, `*' matches any number
    # of any symbols (so you have to write '2:5020/*' but not '5020/*')
    # Use `!' to invert the mask
    # These rules apply in the same order as in config, you can present any address #
    #hide-aka 2:5020/999.* !2:*@fidonet # hide aka from all but fido zone 2 #hide-aka 21:4/106 !21:*@fsxnet
    #present-aka 2:5047/999.1 2:5047/*.0* # present aka to all nodes in 2:5047

    #
    # The name of your system, its location and your name
    #
    sysname "The Rusty MailBox"
    location "Penticton, BC Canada"
    sysop "Alan Ianson"

    #
    # System capabilities
    #
    nodeinfo 115200,CM,XW,IBN

    #
    # Uncomment it if you want binkd's log at your console
    #
    conlog 4

    #
    # If a log message matches one of these masks it won't be written to log
    # (masks are in shell/glob style, case-insensitive)
    #
    nolog "*socket # [0-9]*"
    nolog "*.[bc]sy"

    #
    # Uncomment if you want T-Mail(FrontDoor)-style binary log
    # (Will work and have sense on PCs only?)
    #
    #binlog binkd.sts
    #fdinhist in.his
    #fdouthist out.his

    #
    # TCP settings. Leave this unchanged if not sure.
    #
    # Suffixes for time intervals are w for weeks, d for days,
    # h for hours, m for minutes, s or no suffix for seconds.
    # You can mix the suffixes, i.e. 1d12h is the same as 36h.
    #
    #iport binkp
    #oport binkp
    #oblksize 4096
    #timeout 30s
    #connect-timeout 30s
    #bindaddr 192.168.0.3

    #
    # Zlib compression parameters (if built with zlib support)
    # zlevel - compression level (zlib only, bzlib2 uses 100kb always),
    # set to 0 to use default value of 6
    # zminsize <size> - files smaller than <size> won't be compressed anyway
    # Rules:
    # zallow <mask1>[ <mask2>... <maskN>] - allow compression for the masks
    # zdeny <mask1>[ <mask2>... <maskN>] - deny compression for the masks
    # If remote accepts compressed blocks (OPT GZ) its name will be checked
    # against these rules before sending each file. If the name matches a zallow
    # rule the file will be sent with compression. If the name matches a zdeny rule # it will be sent as-is. The rule matched first is applied. If a file doesn't
    # match any rule zdeny is assumed.
    #
    zminsize 1024
    #
    zallow *.pkt *.PKT
    zdeny *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa?
    zdeny *.zip *.rar *.arj *.ha *.gz *.tgz *.bz2 *.z[0-9][0-9] *.r[0-9][0-9] zallow *

    #
    # Compression dll names, for win32 versions built with ZLIBDL
    #
    #zlib-dll zlib.dll
    #bzlib2-dll bzlib2.dll

    #
    # HTTPS or SOCKS settings.
    #
    # proxy 192.168.0.3:3128 # <- regular http/https proxy (i.e. squid)
    # proxy 192.168.0.3:3128/user/password # <- proxy required username/password
    # # (as in browser)
    #
    # proxy 192.168.0.3:3128/user/password/your_host/your_domain
    # ^- proxy required NTLM authorization with username/password
    # your_host -- Windows host name without domain (i.e. MY_HOST)
    # your_domain -- Windows domain name (not FQDN, i.e. DEFAULT_DOMAIN)
    #
    # socks 192.168.0.3:1080 # <- socks4 proxy
    # socks 192.168.0.3:1080/ # <- socks5 proxy without authorization
    # socks 192.168.0.3:1080/user/password # <- socks5 proxy with # username/password
    # # (RFC-1929)

    #
    # Delay of calls and outbound rescans in seconds
    #
    call-delay 30s
    rescan-delay 30s

    #
    # Max. number of inbound/outbound connections
    #
    #maxservers 2
    #maxclients 2

    #
    # Binkd will try to call a node N times. If failed it will
    # hold the node for S seconds. The feature is off by default.
    #
    try 2
    hold 3h

    #
    # hold-skipped <S>
    # Binkd will hold for S seconds all mail skipped by a node. (Def. -- 1h)
    #
    #hold-skipped 1h

    #
    # Don't send (only receive) files if no password for an inbound session
    #
    #send-if-pwd

    # Tzoff corrects UTC time returned by time() under DOS-derived OS
    # Using system TZ variable or tzselect(8) is preferred.
    #tzoff 3h

    #
    # Use syslog (Only if made with -DHAVE_VSYSLOG and -DHAVE_FACILITYNAMES)
    #
    #syslog local0

    #
    # Print percents while sending or receiving
    #
    percents

    #
    # List queue after rescans
    #
    printq

    #
    # Perform reverse resolving (for logging only)
    #
    backresolv

    #
    # Log pid:
    #
    pid-file /usr/local/fido/binkd.pid

    #
    # Map paths in flo's:
    # ftrans <old-string> <new-string>
    # Use as many ftrans's as you want.
    #
    #ftrans "D:\\fido\\outbound" "/var/spool/fido/outb"
    #ftrans "\\" "/" # this replaces all slashes in a path

    #
    # Inbound directories for secure and non-secure links
    #
    inbound /usr/local/fido/inbound
    inbound-nonsecure /usr/local/fido/inbound/insecure

    #
    # Directory for incomplete receiving files (.hr and .dt),
    # default to inbound for the node
    #
    temp-inbound /usr/local/fido/inbound/tmp

    #
    # Binkd will skip all files from a node if
    # size_of_the_next_file_for_us_there + minfree < free_space_in_inbound
    # The zero value and the value 4294967295 (2**32-1) is equivalented to infinity.
    #
    minfree 2048
    minfree-nonsecure 2048

    #
    # When trying to receive a new file: remove partial files with this
    # name but different size or time from inbound. (If commented out, binkd
    # will left old parts as .dt and .hr in the inbound directory)
    #
    kill-dup-partial-files

    #
    # Remove all old partial files from inbound. (OFF if commented out)
    # kill-old-partial-files <max-age-in-seconds>
    #
    kill-old-partial-files 1d

    #
    # Remove old .bsy/.csy files (If some are left after a system crash). It would # be wise to set this to 12h on almost any system. (Note that binkd always
    # touches .bsy's/.csy's for active sessions)
    #
    # kill-old-bsy is OFF by default.
    #
    kill-old-bsy 12h

    #
    # Create a flag file after receiving a file
    #
    #flag /sbbs/data/fidoin.now *.pkt *.PKT
    #flag /sbbs/data/fidoin.now *.su? *.SU? *.mo? *.MO? *.tu? *.TU? *.we? *.WE? *.th? *.TH? *.fr? *.FR? *.sa? *.SA?
    #flag /sbbs/data/tickit.now *.tic *.TIC

    #
    # Run an external program.
    # The "*S" macro in command line substed with S.R.I.F., see !SRIF.TXT
    # The "!" before program pathname means immediate program execution
    # after receiving the file.
    # *** win32 only:
    # The "@" before program pathname means execute program in separate console
    # The "@@" before program pathname means execute program in hidden console
    # ***
    # Macros: *F - complete name of received file,
    # *A0..*A9 - first 10 AKA of remote system,
    # *A*, *A@ - list of all remote AKA separated by spaces
    # *P - password protected [0|1],
    # *L - listed system [0|1]
    # *H - remote hostname or IP,
    # *N - short file name (win32 only).
    #
    exec "/usr/local/bin/hpt-incoming.sh" *.[pP][kK][tT] *.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[tT][iI][cC]
    exec "touch /usr/local/fido/dofhnr.now" *.FHR
    exec "touch /usr/local/fido/dogd.now" *.GAL
    exec "mfreq-srif -s *S" *.req
    #exec "my-pkt-unpacker /options *S" *.pkt
    #exec "my-tosser /options" #c:\\bbs\\inbound\\????????.[mwtfs][oehrau][0-9a-zA-Z]
    #exec "nice -n 19 hpt toss link" #/var/spool/ftn/inbound/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[pP][kK][tT]

    #
    # Include a file
    #
    #include /etc/ftn/binkd.inc

    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net

    #
    # Scan T-Mail boxes (short and long)
    #
    #filebox d:\\fido\\tmail\\boxes

    #
    # Scan theBrake! long boxes
    #
    #brakebox d:\\fido\\brake\\boxes
    #brakebox /var/spool/ftn/longbox

    #
    # Should binkd delete empty boxes?
    # Uncomment the following line, if yes
    #
    #deletebox

    #
    # Scan node outbound while connecting and send mail size to remote
    #
    prescan

    # t-mail or ifcico (qico) password file.
    # Format of the password file:
    # [password] <FTN address> <inpwd>[,[<pktpwd>][,<outpwd>]]
    # where:
    # [password] optional "password" token;
    # <FTN address> address of a link in the form 1:2/3.4@domain
    # or 1:2/3@domain or 1:2/3 or 1:2/3.4;
    # <inpwd> password for incoming sessions;
    # <pktpwd> packet password, used when "share" token
    # is handled;
    # <outpwd> password for outgoing sessions.
    # Any password is one word without spaces or tabs. If <pktpwd> or <outpwd>
    # is omitted, it is assumed equal to <inpwd>. If a password is defined for
    # a node by the "node" token then the passwords for the node in the password
    # file are ignored.
    #
    #passwords /etc/ftn/passwords

    #
    # Skip files:
    # skip [all|listed|unlisted|secure|unsecure] [!]<sizeKb>|- <mask>...
    #
    # 'all' applies to all sessions (default)
    # 'listed' applies to sessions with the nodes defined by 'node' keyword
    # 'secure' applies to password-protected sessions
    #
    # Use '!' before size for destructive skip, default is non-destructive one.
    # If <size> > 0 then only files larger than <size> in kilobytes are skipped,
    # zero <size> applies to all files,
    # if <size> is set to '-' then the rule allows any file by <mask>'s
    #
    # <mask> is a shell-style mask, case-insensitive (except for symbols in [])
    # multiple masks for a rule are permitted
    #
    # Policy for rule processing is first-match
    #
    #skip all 0 *.mp3 *.avi
    #skip unsecure 256 *.pkt
    #skip unsecure !0 *

    #
    # Overwrite the existing file by the new received,
    # do not save with the changed extension
    #
    #overwrite net_*.*

    #
    # Inbound filename case:
    # inboundcase [save(default)|upper|lower|mixed]
    #
    # 'save' don't change filename case (default)
    # 'upper' uppercase filename (FILE-NAME.EXT)
    # 'lower' lowercase filename (file-name.ext)
    # 'mixed' make filename pretty (File-Name.Ext)
    #
    # * tested only with english filenames
    #
    #inboundcase save

    #
    # Should binkd send empty files?
    # dont-send-empty [no(default)|arcmail|yes]
    #
    # 'no' inhibit only sending *.?ut (netmail) with size <=60 bytes
    # 'arcmail' do not send zero-size arcmail and pkt <= 60 bytes
    # 'yes' do not send all zero-size files and pkt <= 60 bytes
    #
    dont-send-empty yes

    #
    # Should binkd delete empty point dirs in BSO?
    # Uncomment the following line, if yes
    #
    deletedirs

    #
    # Use Amiga Style Outbound (ASO)
    #
    #aso

    #
    # Limit bandwidth (rate):
    # limit-rate [all|listed|unlisted|secure|unsecure] <rate>[kM%]|- <mask>...
    #
    # <rate> is a max allowed rate in bytes-per-second (k=kbytes, M=Mbytes),
    # if % is specified, the node -bw rate is multiplied by this value
    # in percents, if - then rate is unlimited
    # <mask> is a filename mask to apply this rule to
    #
    # limit-rate rules are checked in the order they appear in config, first
    # matcing rule is applied
    #
    # IMPORTANT! If a node has no explicitly defined bandwidth limit, the
    # defnode's limit is used. If defnode has no limit, rate is unlimited.
    #
    #limit-rate unsecure - *.pkt
    #limit-rate unsecure 2k *

    # Define shared aka
    # Add a shared-address as aka for any node from this list, so that
    # uncompessed netmail for shared aka will be sent in the first session with # any node listed in shares; packet header will be updated to match this
    # node's main aka and pkt password
    # share <shared-address> <node1> [<node2> ...]
    # example:
    #share 2:999/999 2:5020/52 2:5020/238

    #
    # Check the sender's address in incoming pkt's, change the file extension
    # to <ext>, if the check failed
    # check-pkthdr [all|secure|unsecure|listed|unlisted] <ext>
    #
    # 'all' applies to all nodes
    # 'listed' applies, if at least one aka is defined by 'node' keyword
    # 'secure' applies, if at least one aka is password-protected
    #
    # It's ok to specify .<ext> as well as <ext> - the dot before ext is ignored
    # Flag order: -nohc (for any aka), -hc (for any aka), check-pkthdr flag
    #
    #check-pkthdr secure .sec

    #
    # Define a link:
    # node [[z:]n/]n[.p][@domain] [-nr|-nd] [-md] [-hc|-nohc] [-ip|-sip] [-bw
    <send_rate>[/<recv_rate>]] [-4|-6] [{hosts|-} [{<inpwd>[,[<pktpwd>][,<outpwd>]]|-} [flavour [{obox|-} [{ibox|-}]]]]]
    #
    # * All non-"-" fields will redefine the values specified for the same node
    # earlier in config.
    # * The meaning of <inpwd>, <pktpwd> and <outpwd> is the same as in
    # the description of the "passwords" token. Any password is one word
    # without spaces or tabs. If <pktpwd> or <outpwd> is omitted, it is
    # assumed equal to <inpwd>.
    # * Flavour is one of i, c, d, -, h; and is the flavour for the outbound
    # filebox ("obox").
    # * Binkd sends from obox all non-dir entries NOT matching ".*" wildcard.
    # EVERY TIME YOU PUT A FILE INTO OBOX CHECK IF BINKD WILL BE ABLE TO
    # UNLINK IT. Otherwise, the session will never end.
    # * Default for ibox is inbound or inbound-nosecure depending on the pwd field. # * Default for port is oport.
    # * `-nr' stands for `Not Reliable Link', this works only on outbound calls
    # with another binkp/1.1 mailer. The option solves the only problem with
    # binkd having no enough time to start receiving of a file from
    # non-zero offset before IP link's down, so don't use it unless you
    # have this problem -- really not effective
    # * `-nd' means "No Dupe Mode", this works only on outbound calls with
    # another binkd 0.9.3 or higher. The option solves problem with
    # duplicating files while losts carrier but link is a bit slower
    # then with "-nr" option
    # * `-md' means "Must have CRAM-MD5". This works only with nodes with
    # binkd or argus supported this method. Do not set it if your link
    # can use the old version of binkd.
    # * `-nomd' - do not use CRAM-MD5 for this node (send plain text password)
    # * `-hc' enables check of sender address in pkt header for this node/aka
    # (overrides the setting of the 'check-pkthdr' statement)
    # * `-nohc' disables check of sender address in pkt header for this node/aka
    # (overrides the setting of the 'check-pkthdr' statement)
    # * `-ip' means "Remote IP check". In this case the node will be
    # rejected, if it comes not from one of its IP-addresses.
    # Remote AKAs with bad IP-address will be dropped on outgoing calls.
    # * `-sip' means "Strict remote IP check". Like "-ip", but node will be
    # rejected, if no IP-addresses allowed ("-" or not resolved).
    # Remote AKAs with bad IP-address will be dropped on outgoing calls.
    # * `-bw' specifies bandwidth (rate) limit for this node
    # if one value is specified, it's used as both send and recv limit
    # if two values are specified,d
    SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 133 SEEN-BY: 1/134 135 136 137 138 139 140 141 143 144 145 146 147 148 149 150 152 SEEN-BY: 1/153 154 155 157 158 159 160 161 162 163 164 165 166 167 168 169 171 SEEN-BY: 1/172 173 174 175 176 177 178 180 181 182 183 184 185 186 187 188 189 SEEN-BY: 1/190 191 192 193 194 195 197 198 199 200 201 202 203 204 205 206 207 SEEN-BY: 1/208 209 995 2/100 3/100 4/100 5/100
  • From Vk3jed@21:1/109 to eggy on Monday, March 02, 2020 09:25:00
    On 03-01-20 11:51, eggy wrote to All <=-

    So.. I've been trying to get binkd to work on my rPI, using a point instead of requesting another node and I'm having no joy in doing so. Below is my binkd.conf

    I use binkd on a Pi with no issues.

    # Number @ end is the root zone
    domain fsxnet /home/e/bbs/ftn_out 21

    #fsxNet address
    address 21:1/143.1@fsxnet
    ^^^^^^^^^^^^^^^^^^
    .......
    #Primary HUB
    node 21:4/143@fsxnet -md bbs.eggy.cc:24554 XXXXXXX c
    ^^^^^^^^
    ---------------------------------------------------------

    When I try to poll, using the following command:

    /usr/local/sbin/binkd -p -P 21:1/143@fsxnet /home/e/binkd.conf
    ^^^^^^^^^^^^^^^

    Your addresses look a bit off, and also, 1/143 happens to be my other BBS. ;)

    Were these copied and pasted from your config file or typed by hand? The "node" entry looks correct, but the "address" line's address and the address used in the poll command look suspect.


    ... Luxuriantly hand-crafted from only the finest ASCII.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Al on Monday, March 02, 2020 09:26:00
    On 03-01-20 10:19, Al wrote to eggy <=-

    Hello eggy,

    /usr/local/sbin/binkd -p -P 21:1/143@fsxnet /home/e/binkd.conf

    That's a curious error. When I poll my boss I use the same command as
    you are using without @fsxnet. I wonder if that would make a
    difference.

    Yeah I dn't use domains in my polls either.


    ... It's funny because *I* said it!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From vorlon@21:1/195.1 to eggy on Monday, March 02, 2020 10:13:46
    So.. I've been trying to get binkd to work on my rPI, using a
    point instead of requesting another node and I'm having no joy in
    doing so. Below is my binkd.conf

    Running binkd as a point is just like a normal setup, but using the point number. My point is on a version 1 pi, at my parents house and has
    no troubles polling the hub.

    All the other settings are as default with binkd.


    # Number @ end is the root zone
    domain fsxnet /home/pi/MagickaBBS/ftn/out 21

    # Our address
    address 21:1/195.1@fsxnet

    # HUB
    node 21:1/195@fsxnet -md ftn.vk3heg.net:24554 fredlikescheese c



    cat bp.sh
    #!/bin/sh
    ./binkd -c binkd.config -p -P 21:1/195






    \/orlon



    --- MagickaBBS v0.14alpha (Linux/armv6l)
    * Origin: \/orlon Empire: Sector 550 (21:1/195.1)
  • From eggy@21:4/143 to Vk3jed on Sunday, March 01, 2020 17:34:23

    Your addresses look a bit off, and also, 1/143 happens to be my other
    BBS. ;)

    Thanks for spotting my error.. I've corrected my addresses in the configs, its working now that I'm polling the correct address.. etc =)

    Thanks,
    matt // eggy
    Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222
    fsxNet (21:4/143) | SciNet (77:1/136) | FidoNet (1:220/50)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Eggy BBS (21:4/143)
  • From tenser@21:1/101 to eggy on Monday, March 02, 2020 12:58:11
    On 01 Mar 2020 at 03:04p, eggy pondered and said...

    I compiled it yesterday from https://github.com/pgul/binkd.git
    Is there a more recent fork I should be using?

    Nope, that's the main one.

    --- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to eggy on Monday, March 02, 2020 10:57:00
    On 03-01-20 17:34, eggy wrote to Vk3jed <=-


    Your addresses look a bit off, and also, 1/143 happens to be my other
    BBS. ;)

    Thanks for spotting my error.. I've corrected my addresses in the
    configs, its working now that I'm polling the correct address.. etc =)

    Cool, all good then. :)


    ... Violence is the last word of the incompetant. Also the first.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Blue White@21:4/134 to eggy on Monday, March 02, 2020 19:34:04
    eggy wrote to All <=-

    /usr/local/sbin/binkd -p -P 21:1/143@fsxnet /home/e/binkd.conf

    I get the following errors:
    11:37 [31698] BEGIN, binkd/1.1a-101/Linux -p -P 21:1/143@fsxnet /home/e/binkd.conf
    11:37 [31698] creating a poll for 21:1/143@fsxnet (`d' flavour)
    11:37 [31698] clientmgr started
    $ -d 21:1/143@fsxnet
    + 11:37 [31699] call to 21:1/143@fsxnet
    + 11:37 [31699] getaddrinfo failed: Name or service not known (-2)
    11:37 [31698] rc(31699)=0
    11:37 [31698] the queue is empty, quitting...

    Just a straw grasp here, but is there an entry for binkp in your
    /etc/services file?




    ... 2 + 2 = 5 for extremely small values of 5
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)