• Question about compiling

    From Joacim Melin@2:221/242 to All on Thu Jul 2 19:59:53 2026
    All,

    I had to compile Binkd on Rocky Linux 10 and everything seems to work fine. Outgoing packets are sent properly but Binkd does not respond to incoming traffic from the Internet. I have verified that the firewall rules in OPNsense (which powers my Firewall) is not the issue and Binkd responds fine if I telnet to port 24554 on my internal network.

    I'm wondering if there is a compile flag I missed?

    This is what binkd -vv says:

    Binkd 1.1a-115 (Jun 13 2026 11:48:51/Linux)
    Compilation flags: gcc, zlib.
    Facilities: fts5004 ipv6


    I've been trying to find documentation covering all available compilation flags (I'm not a developer) so any information on this is more than welcome.

    Thanks.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Thu Jul 2 20:27:40 2026
    Hi Joacim,

    On 2026-07-02 19:59:53, you wrote to All:

    I had to compile Binkd on Rocky Linux 10 and everything seems to work fine. Outgoing packets are sent properly but Binkd does not respond to incoming traffic from the Internet. I have verified that the firewall rules in OPNsense (which powers my Firewall) is not the issue and
    Binkd responds fine if I telnet to port 24554 on my internal network.

    Did you try both 127.0.0.1 (localhost), and the local ip number on your network (like: 192.168.0.x), and their IPv6 counterparts?

    If both work, it must be a firewall or router problem...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Joacim Melin@2:221/242 to Wilfred van Velzen on Thu Jul 2 21:31:08 2026
    Hi Joacim,

    On 2026-07-02 19:59:53, you wrote to All:

    I had to compile Binkd on Rocky Linux 10 and everything seems to work
    fine. Outgoing packets are sent properly but Binkd does not respond to
    incoming traffic from the Internet. I have verified that the firewall
    rules in OPNsense (which powers my Firewall) is not the issue and
    Binkd responds fine if I telnet to port 24554 on my internal network.

    Did you try both 127.0.0.1 (localhost), and the local ip number on
    your network (like: 192.168.0.x), and their IPv6 counterparts?

    If both work, it must be a firewall or router problem...


    Bye, Wilfred.

    Yes both localhost and the local IP address works. There are no local firewall active on the server and other services (nntp, etc) works fine from the Internet. The port (24559, forwarded to 24554 in the OPNSense firewall) works fine with my other Binkd installation for this node number when I tried to direct the traffic to that server as a test. Binkd on the new server will simply not work with any traffic from the Internet.

    I enabled this in the binkd configuration:

    iport binkp
    oport binkp
    oblksize 4096
    timeout 5m
    connect-timeout 5m
    bindaddr 10.0.2.237
    listen *


    It did not help.

    I agree this looks like a firewall configuration issue but I have tested everything and the only conclusion I can find is that Binkd is the issue.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
  • From Nigel Reed@1:124/5016 to Joacim Melin on Thu Jul 2 15:25:55 2026
    On Thu, 2 Jul 2026 21:31:08 +0000
    "Joacim Melin" (2:221/242) <Joacim.Melin@f242.n221.z2.fidonet> wrote:

    Hi Joacim,

    On 2026-07-02 19:59:53, you wrote to All:

    I had to compile Binkd on Rocky Linux 10 and everything seems
    to work fine. Outgoing packets are sent properly but Binkd does
    not respond to incoming traffic from the Internet. I have
    verified that the firewall rules in OPNsense (which powers my
    Firewall) is not the issue and Binkd responds fine if I telnet
    to port 24554 on my internal network.

    Did you try both 127.0.0.1 (localhost), and the local ip number
    on your network (like: 192.168.0.x), and their IPv6
    counterparts?

    If both work, it must be a firewall or router problem...


    Bye, Wilfred.

    Yes both localhost and the local IP address works. There are no
    local firewall active on the server and other services (nntp, etc)
    works fine from the Internet. The port (24559, forwarded to 24554 in
    the OPNSense firewall) works fine with my other Binkd installation
    for this node number when I tried to direct the traffic to that
    server as a test. Binkd on the new server will simply not work with
    any traffic from the Internet.

    I enabled this in the binkd configuration:

    iport binkp
    oport binkp
    oblksize 4096
    timeout 5m
    connect-timeout 5m
    bindaddr 10.0.2.237
    listen *


    It did not help.

    I agree this looks like a firewall configuration issue but I have
    tested everything and the only conclusion I can find is that Binkd is
    the issue.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)

    While it's running...

    sudo netstat -anp|grep bink

    and see if it's actually listening on the binkp port. I assume that
    binkp is pulled from /etc/services. I have all those commented out in
    my config and it just works. I am not sure what listen is, I don't have
    one of those.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.37-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Joacim Melin@2:221/242 to Joacim Melin on Thu Jul 2 22:18:02 2026
    Another option I'm concidering is whether I can use my working Binkd to route packets for one node number to another Binkd on my other (new) server. I'm guessing this is done with processing the incoming packets with a tosser and sending them to the correct node number?

    I'm grasping for straws here but I'm really at a loss about how to solve this.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
  • From Joacim Melin@2:221/242 to Nigel Reed on Thu Jul 2 22:38:14 2026
    On Thu, 2 Jul 2026 21:31:08 +0000
    "Joacim Melin" (2:221/242) <Joacim.Melin@f242.n221.z2.fidonet> wrote:

    Hi Joacim,

    On 2026-07-02 19:59:53, you wrote to All: >>
    I had to compile Binkd on Rocky Linux 10 and everything seems >> JM>> to work fine. Outgoing packets are sent properly but Binkd does >> JM>> not respond to incoming traffic from the Internet. I have >> JM>> verified that the firewall rules in OPNsense (which powers my >> JM>> Firewall) is not the issue and Binkd responds fine if I telnet >> JM>> to port 24554 on my internal network.

    Did you try both 127.0.0.1 (localhost), and the local ip number >> WvV> on your network (like: 192.168.0.x), and their IPv6 >> WvV> counterparts?

    If both work, it must be a firewall or router problem... >>

    Bye, Wilfred.

    Yes both localhost and the local IP address works. There are no >> local firewall active on the server and other services (nntp, etc) >> works fine from the Internet. The port (24559, forwarded to 24554 in >> the OPNSense firewall) works fine with my other Binkd installation >> for this node number when I tried to direct the traffic to that >> server as a test. Binkd on the new server will simply not work with >> any traffic from the Internet.

    I enabled this in the binkd configuration:

    iport binkp
    oport binkp
    oblksize 4096
    timeout 5m
    connect-timeout 5m
    bindaddr 10.0.2.237
    listen *


    It did not help.

    I agree this looks like a firewall configuration issue but I have >> tested everything and the only conclusion I can find is that Binkd is >> the issue.

    I'll just walk over to the corner of shame here - it was my firewall (OPNsense) that was the problem. Starting with OPNSense 26.1 the old Port Forward stuff was removed and now you configure a Destination NAT and then you have to make sure you set the firewall rule setting in that Destination NAT setting to "Pass". It doesn't seem to help to create the rule on the WAN interface manually, you have to do it when you create the Destination NAT setting for that port.

    Thanks all for patience and answers.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
  • From Javier Sturman@4:900/733 to Joacim Melin on Thu Jul 2 18:44:56 2026

    Hello Joacim!

    02 Jul 26 19:59, you wrote to all:


    I'm wondering if there is a compile flag I missed?

    This is what binkd -vv says:

    Binkd 1.1a-115 (Jun 13 2026 11:48:51/Linux)
    Compilation flags: gcc, zlib.
    Facilities: fts5004 ipv6

    Can you try netstat -a4n? Or with the new tools, ss -tuln



    I've been trying to find documentation covering all available
    compilation flags (I'm not a developer) so any information on this is
    more than welcome.

    Thanks.


    --- NiKom v2.6.0
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)

    Javier


    --- GoldED+/BSD 1.1.5-b20260304 + HPT 1.9.0 + Binkd 1.1a-115
    * Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)