• A true rescan of this echo

    From Björn Felten@2:203/2 to All on Thu Apr 20 13:02:39 2017
    I've got some requests for a rescan of this echo, and here you go:

    http://eljaco.se/FILES/Billing/JAMNNTPD.rar

    The echo started out as a local test echo on my site, where a few of us (mostly Johan Billing and I) would try to bring this old project of his to life. I think it was already five or so years old -- version 0.6 or so -- but unfairly dormant.

    Well the first message posted here was dated Date: Sun, 27 Jun 2004 21:39:15 GMT

    The first 100 or so messages were mostly posted from my 2:203/2 message base, but soon more servers went online. That's the reason that the four JAM files in the above package is named test.* in case you wonder; it soon became the JAMNNTPD echo.

    Now there's 2746 messages in the package above. Take it or leave it, rename it to whatever you like -- if you rename it to what you have ATM you'll only miss this message... 8-)



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Bjrn Felten on Thu Apr 20 13:27:42 2017
    * Originally in JAMNNTPD
    * Crossposted in IPV6
    Hi Bjrn,

    On 2017-04-20 13:02:39, you wrote to All:

    I've got some requests for a rescan of this echo, and here you go:

    http://eljaco.se/FILES/Billing/JAMNNTPD.rar

    Got it:

    # wget http://eljaco.se/FILES/Billing/JAMNNTPD.rar
    --2017-04-20 13:26:21-- http://eljaco.se/FILES/Billing/JAMNNTPD.rar
    Resolving eljaco.se (eljaco.se)... 2001:470:27:302::2, 90.231.158.147 Connecting to eljaco.se (eljaco.se)|2001:470:27:302::2|:80... failed: Connection refused.
    Connecting to eljaco.se (eljaco.se)|90.231.158.147|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 566295 (553K) [application/octet-stream]
    Saving to: ‘JAMNNTPD.rar’

    But your http server on IPv6 seems to be broken?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.7-B20170419
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Björn Felten on Thu Apr 20 18:14:29 2017
    On Thu, 20 Apr 2017 13:02:39 +0200 Bjrn Felten wrote:

    http://eljaco.se/FILES/Billing/JAMNNTPD.rar

    Got it. :)

    'Tommi

    --- Sylpheed 3.5.1 (GTK+ 2.24.23; i686-pc-mingw32)
    * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
  • From Bjrn Felten@2:203/2 to Wilfred van Velzen on Thu Apr 20 17:52:57 2017
    But your http server on IPv6 seems to be broken?

    True. I spent a few hours some five or six years ago trying to get IPv6 speak port 80 here on my Windows system, but I gave up.

    It's a shortcoming of my IIS/5.1 server, and I never found a good reason to upgrade to Apache. 8-)




    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Bjrn Felten on Thu Apr 20 18:04:32 2017
    Hi Bjrn,

    On 2017-04-20 17:52:57, you wrote to me:

    But your http server on IPv6 seems to be broken?

    True. I spent a few hours some five or six years ago trying to get IPv6 speak port 80 here on my Windows system, but I gave up.

    It's a shortcoming of my IIS/5.1 server, and I never found a good reason
    to upgrade to Apache. 8-)

    So create a www.eljaco.se without a AAAA record attached to it for your http server...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.7-B20170419
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Bjrn Felten on Thu Apr 20 19:38:46 2017
    Hello, Bj�rn Felten : Wilfred van Velzen.
    On 20/04/2017 6:52 p.m. you wrote:

    But your http server on IPv6 seems to be broken?
    True. I spent a few hours some five or six years ago trying to
    get
    IPv6 speak port 80 here on my Windows system, but I gave up.

    The netsh portproxy should do the trick.

    --
    'Tommi

    --- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1480338873000 Hotd
    * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
  • From Tommi Koivula@2:221/360 to Bjrn Felten on Thu Apr 20 19:38:47 2017
    Hello, Bj�rn Felten : Wilfred van Velzen.
    On 20/04/2017 6:52 p.m. you wrote:

    It's a shortcoming of my IIS/5.1 server, and I never found a
    good
    reason to upgrade to Apache. 8-)

    Ipv6? Security?

    --
    'Tommi

    --- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1480338873000 Hotd
    * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
  • From Bjrn Felten@2:203/2 to Wilfred van Velzen on Thu Apr 20 19:17:51 2017
    It's a shortcoming of my IIS/5.1 server, and I never found a
    good reason to upgrade to Apache. 8-)

    So create a www.eljaco.se without a AAAA record attached to it for your http server...

    I don't understand. Are you saying that it doesn't work for IPv4?



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Bjrn Felten@2:203/2 to Tommi Koivula on Thu Apr 20 19:19:04 2017
    The netsh portproxy should do the trick.

    For the last time: IIS/5.1 doesn't know anything about IPv6.

    EOD?



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Bjrn Felten@2:203/2 to Tommi Koivula on Thu Apr 20 19:20:37 2017
    Ipv6? Security?

    Has never been a problem for the more than 15 years that I've had my web site running.



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Bjrn Felten on Thu Apr 20 19:40:48 2017
    Hi Bjrn,

    On 2017-04-20 19:17:51, you wrote to me:

    So create a www.eljaco.se without a AAAA record attached to it for
    your http server...

    I don't understand. Are you saying that it doesn't work for IPv4?

    It works, but only after the connection on IPv6 fails, because you are advertising an IPv6 address for that domain, which is not correct for your http server. So my suggestion is, use a different hostname for your http server that only advertises an IPv4 address

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.7-B20170419
    * Origin: FMail development HQ (2:280/464)
  • From Richard Menedetter@2:310/31 to Bj≈rn Felten on Thu Apr 20 19:56:08 2017
    Hi Bjrn!

    20 Apr 2017 19:17, from Bjrn Felten -> Wilfred van Velzen:

    So create a www.eljaco.se without a AAAA record attached to it
    for your http server...
    I don't understand. Are you saying that it doesn't work for IPv4?

    You claim to support both by having A and AAAA records.
    IPv6 is preferred when you have a dual stack system.
    Meaning that you have to wait until IPv6 fails, before the fallback to IPv4 occurs.

    So if you do not support IPv6 do not advertise an AAAA record.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: And then I woke up! (2:310/31)
  • From Björn Felten@2:203/2 to Richard Menedetter on Thu Apr 20 20:06:55 2017
    So if you do not support IPv6 do not advertise an AAAA record.

    I can't find any setting in my AAAA record that limits the connectivity to certain IPv4 ports. I *do* support IPv6 on the ports that are opened in my router, is that not good enough?



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Richard Menedetter@2:310/31 to Bj÷rn Felten on Thu Apr 20 20:13:36 2017
    Hi Bjrn!

    20 Apr 2017 20:06, from Bjrn Felten -> Richard Menedetter:

    So if you do not support IPv6 do not advertise an AAAA record.
    I can't find any setting in my AAAA record that limits the
    connectivity to certain IPv4 ports. I *do* support IPv6 on the ports
    that are opened in my router, is that not good enough?

    The AAAA record indicates working IPv6.
    You cannot limit its scope.

    So you can use different subdomains to signal different capabilities.

    Eg have ipv4.fqdn.com for v4 and ipv6.fqdn.com for ipv6.
    Or wwww.fqdn.com for IPv4 and fqdn.com for both.

    Whatever floats your boat.

    If you KNOW that the service you are offering does not support IPv6, make sure that the domain you tell people does not have an AAAA record.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: You can never have too much storage (2:310/31)