1. Forum
  2. Fidonet
  3. FIDONEWS

  • Re: FidoNews 42:39 [06/06]: Fidonews Information

    From Wilfred van Velzen@2:280/464 to Björn Felten on Thu Oct 9 22:59:57 2025
    Hi Bj”rn,

    On 2025-10-09 19:49:51, you wrote to me:

    Only IPv6 works. Connects on IPv4 still don't...

    Wonderful news. It only worked with IPv4 with the old setup.

    I don't think so...

    Can you use a traceroute to see where it stops with IPv4?

    # tcptraceroute eljaco.se
    Selected device eth0, address 192.168.178.5, port 36709 for outgoing packets Tracing the path to eljaco.se (94.254.14.141) on TCP port 80 (http), 30 hops max
    1 192.168.178.1 0.482 ms 0.312 ms 0.303 ms
    2 * * *
    3 * * *
    4 * * *
    5 84.241.243.33 36.300 ms 27.609 ms 33.346 ms
    6 84.241.243.20 28.507 ms 29.757 ms 25.381 ms
    7 214-86-143-37.ftth.glasoperator.nl (37.143.86.214) 30.394 ms 34.414 ms 38.462 ms
    8 ams-ix.bahnhof.NET (80.249.208.99) 44.311 ms 36.373 ms 48.386 ms
    9 gbg4-er1.gbg-cr3.as8473.net (46.59.112.114) 48.370 ms 48.397 ms 48.382 ms
    10 a980-gw-c.bahnhof.net (46.59.118.210) 49.472 ms 49.400 ms 48.375 ms
    11 g-br-c1-link.se.telia.net (78.74.2.36) 48.410 ms 49.375 ms 57.372 ms
    12 gw54.A980.priv.bahnhof.se (85.24.226.1) 39.394 ms 50.338 ms 51.426 ms
    13 h-94-254-14-141.A980.priv.bahnhof.se (94.254.14.141) [closed] 100.411 ms 45.410 ms 47.472 ms

    Or this:

    # telnet eljaco.se 80
    Trying 94.254.14.141...
    telnet: connect to address 94.254.14.141: Connection refused
    Trying 2001:9b1:10d:77::52b...
    Connected to eljaco.se.

    So your firewall seems to actively refusing connections on IPv4 for port 80.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Fri Oct 10 10:32:51 2025
    Wilfred van Velzen -> Bj”rn Felten skrev 2025-10-09 22:59:
    So your firewall seems to actively refusing connections on IPv4 for port 80.

    My firewall is open on port 80. DUH!

    But I don't have a telnet server answering on port 80.

    --

    Conning people is easy. You just need to overcome their intelligence. But convincing people they've been conned is much harder. You need to overcome their pride.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.2; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Fri Oct 10 10:59:27 2025
    Wilfred van Velzen -> Bj”rn Felten skrev 2025-10-09 22:59:
    So your firewall seems to actively refusing connections on IPv4 for port 80.

    As I said, my firewall has nothing to do with this. I have only three ports forwarded. One of them is HTTP (80 -> 80).

    If Windows 10 with IIS somehow ignores IPv4 calls, all the better. A quick search in my log files actually seems to confirm that there are only IPv6 calls. Welcome to the 21st century.

    It would have been worse if, after two decades with IPv6, my system still couldn't answer IPv6 calls to my website. :)



    --

    Conning people is easy. You just need to overcome their intelligence. But convincing people they've been conned is much harder. You need to overcome their pride.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.2; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Björn Felten on Fri Oct 10 12:51:18 2025
    Hi Bj”rn,

    On 2025-10-10 10:32:51, you wrote to me:

    So your firewall seems to actively refusing connections on IPv4 for
    port 80.

    My firewall is open on port 80. DUH!

    Well something is blocking port 80 on IPv4 to your server. Maybe it's your provider? Or the server itself?

    But I don't have a telnet server answering on port 80.

    Telnet is just used to check if a tcp/ip connection on port 80 can be established...

    Testing with curl gives the same result:

    # curl -v eljaco.se
    * Rebuilt URL to: eljaco.se/
    * Hostname was NOT found in DNS cache
    * Trying 94.254.14.141...
    * connect to 94.254.14.141 port 80 failed: Connection refused
    * Trying 2001:9b1:10d:77::52b...
    * Connected to eljaco.se (2001:9b1:10d:77::52b) port 80 (#0)
    ...


    Or wget:
    # wget eljaco.se
    --2025-10-10 12:48:39-- http://eljaco.se/
    Resolving eljaco.se (eljaco.se)... 94.254.14.141, 2001:9b1:10d:77::52b Connecting to eljaco.se (eljaco.se)|94.254.14.141|:80... failed: Connection refused.
    Connecting to eljaco.se (eljaco.se)|2001:9b1:10d:77::52b|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    ...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Dan Clough@1:135/115 to Björn Felten on Fri Oct 10 08:08:57 2025
    Bj”rn Felten wrote to Wilfred van Velzen <=-

    Wilfred van Velzen -> Bj”rn Felten skrev 2025-10-09 22:59:
    So your firewall seems to actively refusing connections on IPv4 for port 80.

    My firewall is open on port 80. DUH!

    But I don't have a telnet server answering on port 80.

    Oh! The ignorance.




    ... He does the work of 3 Men...Moe, Larry & Curly
    === MultiMail/Linux v0.52
    --- SBBSecho 3.29-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)