1. Forum
  2. FidoNET
  3. FIDOMAIL

  • IPv6 connection problem

    From Michiel van der Vlist@2:280/5555.6 to Dmitry Protasoff on Sunday, November 01, 2026 11:37:03
    Hello, Dmitry!

    There is a problem connecting to the binkp server via IPv6 when the client is on the same local network as the server. The IPv6 connection is OK when called in from outside. But when calling from the same local network - same /64 - there is a "no route to host" error. The IPv4 connection fails because the Mikrotik router in use does not support hairpin local loop back by default. I did not install that. Who needs IPv4 local loop back when you have IPv6. ;-). The problem does not occur with my point 1 that runs on a Windows laptop. The reason I did not notice the problem before is that I was dual homed. The IPv6 connection apparently always went via WAN from the one provider to the other. The long path in HAM terminology. ;-) I am in the proces of moving to another location and one of the connections will be moved to the new location first. So now that I am no longer dual homed, the problem emerges. That no one else noticed it either is probably because everyone else has fallback to IPv4 via hairpin loop back.
    Anyway, here is the log. I hope you can fix it.

    --- sync log (6) ---
    11:06:55 [1] wire: binkp (the only wire)
    11:06:55 [1] connecting to fido.vlist.eu:24554
    11:06:55 [1] resolved fido.vlist.eu: 2001:4c3c:7d02:ff00:f1d0:2:280:5555 (IPv6), 81.172.198.189 (IPv4); prefer IPv6: IPv4 waits 2 s for IPv6 unless every IPv6 attempt fails first
    11:06:55 [1] error: connect to fido.vlist.eu failed: fido.vlist.eu:24554: 2001:4c3c:7d02:ff00:f1d0:2:280:5555 (IPv6): No route to host (errno 65); 81.172.198.189 (IPv4): Connection refused (errno 61)
    11:06:55 [1] wire binkp: pathFailure; primary failures 4, cycles on fallback 0 11:06:55 [1] sync failed: connect failed: fido.vlist.eu:24554: 2001:4c3c:7d02:ff00:f1d0:2:280:5555 (IPv6): No route to host (errno 65); 81.172.198.189 (IPv4): Connection refused (errno 61)

    Cheers, Michiel

    --- FidoMailMobile/0.2.3+108 (iOS)
    * Origin: Michiel's iPhone (2:280/5555.6)
  • From Tommi Koivula@2:221/1.1111 to Michiel van der Vlist on Sunday, November 01, 2026 21:55:42
    Michiel van der Vlist wrote:

    Hello, Dmitry!

    There is a problem connecting to the binkp server via IPv6 when the
    client is on the same local network as the server. The IPv6
    connection is OK when called in from outside. But when calling from
    the same local network - same /64 - there is a "no route to host"
    error. The IPv4 connection fails because the Mikrotik router in use
    does not support hairpin local loop back by default. I did not
    install that. Who needs IPv4 local loop back when you have IPv6.
    ;-). The problem does not occur with my point 1 that runs on a
    Windows laptop. The reason I did not notice the problem before is
    that I was dual homed. The IPv6 connection apparently always went
    via WAN from the one provider to the other. The long path in HAM terminology. ;-) I am in the proces of moving to another location
    and one of the connections will be moved to the new location first.
    So now that I am no longer dual homed, the problem emerges. That no
    one else noticed it either is probably because everyone else has
    fallback to IPv4 via hairpin loop back. Anyway, here is the log. I
    hope you can fix it.

    I can connect my ipv6-only binkd server from inside and outside with no problems.

    --- FidoMailMobile/0.2.3+108 (iOS)
    * Origin: Michiel's iPhone (2:280/5555.6)

    Android here.

    --- FidoMailMobile/0.2.3+108 (Android)
    * Origin: FidoMailMobile (2:221/1.1111)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sunday, November 01, 2026 21:51:50
    Hello Tommi,

    On 01 Nov 26 21:55, you wrote to me:

    I can connect my ipv6-only binkd server from inside and outside with
    no problems.

    --- FidoMailMobile/0.2.3+108 (iOS)
    * Origin: Michiel's iPhone (2:280/5555.6)

    Android here.

    So maybe the problem is IOS related?


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schoord (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Dmitry Protasoff on Monday, November 02, 2026 21:32:47
    Hello Dmitry,

    01 Nov 26 11:37, I wrote to you:

    Anyway, here is the log. I hope you can fix it.

    In an attempt to find a work around, I tried to enter an IPv6 link local address, a local IPv4 address and a host name that pointed to the local IPv4 address. That didn't work.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schoord (2:280/5555)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tuesday, November 03, 2026 06:43:57
    On 2.11.2026 22.32, Michiel van der Vlist wrote:

    In an attempt to find a work around, I tried to enter an IPv6 link local address, a local IPv4 address and a host name that pointed to the local
    IPv4 address. That didn't work.

    So it may be a problem in your network. Do you allow connections from your wifi to your lan?

    'Tommi

    ---
    * Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555.6 to Tommi Koivula on Tuesday, November 03, 2026 08:12:24
    Hello, Tommi!

    Tommi Koivula wrote:

    In an attempt to find a work around, I tried to enter an IPv6 link
    local
    address, a local IPv4 address and a host name that pointed to the
    local
    IPv4 address. That didn't work.

    So it may be a problem in your network. Do you allow connections
    from your wifi to your lan?

    Of course. My point 1 running on a laptop with windows 7 binkp connects without problems.

    Safari on the iPhone connects with the. HTTP server om my particle matter sensor on the same network.

    The problem is definitely in the FidoMail + iPhone combination. I already eliminated all else.

    Cheers, Michiel

    --- FidoMailMobile/0.2.3+108 (iOS)
    * Origin: Michiel's iPhone (2:280/5555.6)
  • From Dmitry Protasoff@2:5001/100 to Michiel van der Vlist on Thursday, November 05, 2026 01:07:02
    Hello Michiel!

    In a message of 02 Nov 26 21:32, Michiel wrote to Dmitry:

    MvdV> In an attempt to find a work around, I tried to enter an IPv6
    MvdV> link local address, a local IPv4 address and a host name that
    MvdV> pointed to the local IPv4 address. That didn't work.

    I have no good ideas, so please:

    Check Settings › Privacy & Security › Local Network and check whether FidoMail is listed and switched on. If it is off, switch it on and poll for new mail. If it is already on, toggle it off and on once.

    And the next version will have additional logging for such issues.

    See you,
    dp.
    --- FidoMail v0.1.5-168-g02ee4d75
    * Origin: livin' on the edge (2:5001/100)
  • From Michiel van der Vlist@2:280/5555.6 to Dmitry Protasoff on Thursday, November 05, 2026 10:32:57
    Hello, Dmitry!

    Dmitry Protasoff wrote:

    I have no good ideas, so please:

    Check Settings › Privacy & Security › Local Network and check
    whether FidoMail is listed and switched on. If it is off, switch it
    on and poll for new mail. If it is already on, toggle it off and on
    once.

    It was off. Switched it on. Problem solved!

    I would never have found that without your help. Tnx.

    You may want to make a note of this for the future documentation.

    Cheers, Michiel

    --- FidoMailMobile/0.2.3+108 (iOS)
    * Origin: Michiel's iPhone (2:280/5555.6)