• IPv6 down?

    From Michiel van der Vlist@2:280/5555 to Joe Delahaye on Fri Dec 4 22:59:52 2015
    Hello Joe,

    - 22:57 [320] incoming from 69.165.170.121 (51198)
    + 22:57 [2068] incoming session with 69.165.170.121
    - 22:57 [2068] SYS The Lion's Den
    - 22:57 [2068] ZYZ Joe Delahaye
    - 22:57 [2068] LOC Trenton, Ont. Cdn
    - 22:57 [2068] NDL 115200,TCP,BINKP
    - 22:57 [2068] TIME Fri, 4 Dec 2015 16:57:43 -0500
    - 22:57 [2068] VER binkd/1.1a-73/Win32 binkp/1.1
    + 22:57 [2068] addr: 1:249/303@fidonet
    + 22:57 [2068] addr: 1:249/300@fidonet
    + 22:57 [2068] addr: 1:249/0@fidonet
    + 22:57 [2068] addr: 1:12/0@fidonet

    Your IPv6 has problems?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Benny Pedersen@1:261/38.20 to Michiel van der Vlist on Sat Dec 5 01:48:08 2015
    Hello Michiel!

    04 Dec 2015 22:59, Michiel van der Vlist wrote to Joe Delahaye:

    MvdV> Your IPv6 has problems?

    or ipv4 first ?


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.3.0-gentoo (i686))
    * Origin: openvpn on its way here (1:261/38.20)
  • From Joe Delahaye@1:249/303 to Michiel van der Vlist on Fri Dec 4 20:24:01 2015
    Re: IPv6 down?
    By: Michiel van der Vlist to Joe Delahaye on Fri Dec 04 2015 22:59:52

    Your IPv6 has problems?


    So it seems. I just did a test on IPV6 Test. I'll reset the router and see what happens.

    ... Winning isn't the end of the world.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Joe Delahaye@1:249/303 to Michiel van der Vlist on Fri Dec 4 21:45:16 2015
    Re: IPv6 down?
    By: Michiel van der Vlist to Joe Delahaye on Fri Dec 04 2015 22:59:52

    Your IPv6 has problems?


    I rebooted everything, including computer, router and modem. IPv6 test site reports no IPv6, yet, when I do a ping from that same site, I get the following. Another site tells my that my server (possibly my ISP) has IPv6 capabilities. I am logged into that server. I have not changed a thing, unless the latest MS Windows 10 update did something.


    IPv6 Ping

    IPv6 address
    2607:f2c0:f00e:4200:dcb0:3646:8fb5:71ba
    Ping latency ?
    107.5 ms
    Hop limit
    85
    Average packet loss
    1.00 %
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Sat Dec 5 08:38:04 2015
    On 4.12.2015 23:59, Michiel van der Vlist - Joe Delahaye wrote:

    Hello Joe,

    - 22:57 [320] incoming from 69.165.170.121 (51198)
    + 22:57 [2068] incoming session with 69.165.170.121
    - 22:57 [2068] SYS The Lion's Den
    - 22:57 [2068] ZYZ Joe Delahaye
    - 22:57 [2068] LOC Trenton, Ont. Cdn
    - 22:57 [2068] NDL 115200,TCP,BINKP
    - 22:57 [2068] TIME Fri, 4 Dec 2015 16:57:43 -0500
    - 22:57 [2068] VER binkd/1.1a-73/Win32 binkp/1.1
    + 22:57 [2068] addr: 1:249/303@fidonet
    + 22:57 [2068] addr: 1:249/300@fidonet
    + 22:57 [2068] addr: 1:249/0@fidonet
    + 22:57 [2068] addr: 1:12/0@fidonet

    Your IPv6 has problems?

    No AAAA's.

    host f0.n249.z1.binkp.net
    f0.n249.z1.binkp.net is an alias for lionsden.darktech.org. lionsden.darktech.org has address 69.165.170.121

    host f303.n249.z1.binkp.net
    f303.n249.z1.binkp.net is an alias for lionsden.darktech.org. lionsden.darktech.org has address 69.165.170.121

    host f300.n249.z1.binkp.net
    f300.n249.z1.binkp.net is an alias for lionsden.darktech.org. lionsden.darktech.org has address 69.165.170.121

    host f0.n12.z1.binkp.net
    f0.n12.z1.binkp.net is an alias for lionsden.darktech.org. lionsden.darktech.org has address 69.165.170.121

    --- JamNNTPd/Cygwin 1.2
    * Origin: ** nntp://fidonews.mine.nu ** Finland ** (2:221/6)
  • From Joe Delahaye@1:249/303 to Tommi Koivula on Sat Dec 5 09:56:27 2015
    Re: IPv6 down?
    By: Tommi Koivula to Michiel van der Vlist on Sat Dec 05 2015 08:38:04

    No AAAA's.


    No, there is no AAAA, because darktech.org is not set up for that as yet. That is why I could only transmit in IPV6. Now it seems that something has changed, and appears to be getting worse, while testing my IPv6 connection.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Nicholas Boel@2:280/464 to Joe Delahaye on Sat Dec 5 09:46:46 2015
    Hello Joe,

    On 05 Dec 15 09:56, Joe Delahaye wrote to Tommi Koivula:

    No AAAA's.

    No, there is no AAAA, because darktech.org is not set up for that as
    yet. That is why I could only transmit in IPV6. Now it seems that something has changed, and appears to be getting worse, while testing
    my IPv6 connection.

    Did your ISP actually email you to tell you IPv6 was available to you now? Or did it just *work* one day? I went through this at one point, where native IPv6 was working, but within a couple weeks it was shut off on me. I'm guessing my ISP was just testing it publicly at that time, but when I called to ask why it wasn't available any more, they said it wasn't "officially" supported yet, and that I would receive an email when it was. So I ended up going back to my he.net tunnel until that happens.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20151203
  • From Benny Pedersen@1:261/38.20 to Joe Delahaye on Sat Dec 5 17:14:14 2015
    Hello Joe!

    05 Dec 2015 09:56, Joe Delahaye wrote to Tommi Koivula:

    and appears to be getting worse, while testing my IPv6 connection.

    ping ipv4.google.com
    ping6 ipv6.google.com

    if both is pingelble it works, dont know what options on windows do the ipv6 ping, but on linux this is it


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.3.0-gentoo (i686))
    * Origin: openvpn on its way here (1:261/38.20)
  • From Joe Delahaye@1:249/303 to Nicholas Boel on Sat Dec 5 13:10:02 2015
    Re: Re: IPv6 down?
    By: Nicholas Boel to Joe Delahaye on Sat Dec 05 2015 09:46:46

    Did your ISP actually email you to tell you IPv6 was available to you now? Or did it just *work* one day? I went through this at one point, where native IPv6
    was working, but within a couple weeks it was shut off on me. I'm guessing my ISP was just testing it publicly at that time, but when I called to ask why it wasn't available any more, they said it wasn't "officially" supported yet, and that I would receive an email when it was. So I ended up going back to my he.net tunnel until that happens.

    IPv6 is considered a Beta project. However, I was given a native connection, complete with seperate login to the IPv6 server, and the numbers to use. I shot off an email to support today to ask if changes were made. I'm still logged into both servers, and rebooted both modem and router several times.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Joe Delahaye@1:249/303 to Benny Pedersen on Sat Dec 5 19:00:43 2015
    Re: IPv6 down?
    By: Benny Pedersen to Joe Delahaye on Sat Dec 05 2015 17:14:14

    ping ipv4.google.com
    ping6 ipv6.google.com

    if both is pingelble it works, dont know what options on windows do the ipv6 ping, but on linux this is it


    I got a ping result from an IPv6 server, so that part at least worked, but the testing showed no IPv6 for browser connection, and IPv4 as the default with no backup. I have an answer back from my ISP, but I will have to converse with them to figure out the problem, either on POTS, or email. Since it is now the weekend I will have to wait until next week I imagene
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Michiel van der Vlist@2:280/5555 to Joe Delahaye on Sun Dec 6 13:01:02 2015
    Hello Joe,

    On Friday December 04 2015 20:24, you wrote to me:


    Your IPv6 has problems?

    So it seems. I just did a test on IPV6 Test. I'll reset the router
    and see what happens.

    It seems to be up again, at least for outgoing:

    - 06 Dec 01:01:03 [320] incoming from 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35 (51634)
    + 06 Dec 01:01:03 [2916] incoming session with 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35
    - 06 Dec 01:01:03 [2916] SYS The Lion's Den
    - 06 Dec 01:01:03 [2916] ZYZ Joe Delahaye
    - 06 Dec 01:01:03 [2916] LOC Trenton, Ont. Cdn
    - 06 Dec 01:01:03 [2916] NDL 115200,TCP,BINKP
    - 06 Dec 01:01:03 [2916] TIME Sat, 5 Dec 2015 19:01:03 -0500


    Outgoing also works:


    + 13:04 [828] outgoing session with 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef:24554
    - 13:04 [828] OPT CRAM-MD5-0d5467028d9dda1769fc9eca88e330ee
    + 13:04 [828] Remote requests MD mode
    - 13:04 [828] SYS The Lion's Den
    - 13:04 [828] ZYZ Joe Delahaye
    - 13:04 [828] LOC Trenton, Ont. Cdn
    - 13:04 [828] NDL 115200,TCP,BINKP
    - 13:04 [828] TIME Sun, 6 Dec 2015 07:04:17 -0500

    But... for that to work I need to enter the literal IPv6 adress in my binkd.cfg.

    You apparently have not managed yet to create an AAAA record for lionsdem.darktech.org. What is te problem?



    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Nicholas Boel@2:280/464 to Joe Delahaye on Sun Dec 6 07:13:55 2015
    Hello Joe,

    On 05 Dec 15 13:10, Joe Delahaye wrote to Nicholas Boel:

    IPv6 is considered a Beta project. However, I was given a native

    Which means they're still very actively working to perfect it, which also means the connectivity could be shoddy at times.

    connection, complete with seperate login to the IPv6 server, and the numbers to use.

    That's nice. I haven't gotten anything of the sort yet, which is why I still hold off.

    I shot off an email to support today to ask if
    changes were made. I'm still logged into both servers, and rebooted
    both modem and router several times.

    They're probably just going to say that the IPv6 connection may be spotty at times as they work on it, but at least they're keeping it active for you. Mine was great for about 3 weeks and then *poof* it was just gone in an instant. I didn't notice it for a few days, and when I realized it hadn't come back in about a week, I just went back to my old setup.

    Until I get an email from them stating it's up full time, or however they're planning on announcing it to the public.. I'll stick with my stable and reliable tunnel.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20151203
  • From Michiel van der Vlist@2:280/5555 to Nicholas Boel on Sun Dec 6 15:37:35 2015
    Hello Nicholas,

    On Sunday December 06 2015 07:13, you wrote to Joe Delahaye:

    I shot off an email to support today to ask if
    changes were made. I'm still logged into both servers, and
    rebooted both modem and router several times.

    They're probably just going to say that the IPv6 connection may be
    spotty at times as they work on it, but at least they're keeping it
    active for you.

    Indeed, at least they are working on it.

    Mine was great for about 3 weeks and then *poof* it was just gone in
    an instant.

    Bummer, but your situation is still better than mine. My ISP has announced that they will roll out IPv6 "later this year". They have been announcing that for five years now and from my POV, there is little or no indication that anything is happening at all!

    Alledgedly theur have been some tests in other regions, but nothing is happening here.

    I didn't notice it for a few days, and when I realized it hadn't come
    back in about a week, I just went back to my old setup.

    Well, at least something visible is happening at your end...

    Until I get an email from them stating it's up full time, or however they're planning on announcing it to the public.. I'll stick with my stable and reliable tunnel.

    I would do the same. Don't cancel those tunnels yet...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Nicholas Boel@2:280/464 to Michiel van der Vlist on Sun Dec 6 09:25:47 2015
    Hello Michiel,

    On 06 Dec 15 15:37, Michiel van der Vlist wrote to Nicholas Boel:

    Mine was great for about 3 weeks and then *poof* it was just gone
    in an instant.

    Bummer, but your situation is still better than mine. My ISP has
    announced that they will roll out IPv6 "later this year". They have
    been announcing that for five years now and from my POV, there is
    little or no indication that anything is happening at all!

    Same with mine up until that point. They were huge advocates of World IPv6 day as my ISP is fairly big here in the states. After World IPv6 day, there was completely silence as far as IPv6 went up until I just noticed I had an address one day (after using my tunnel for well over a year). So I jumped on it, shut down the tunnel, and went native. Worked great for a couple weeks, and then started getting emails and netmails saying that there wasn't any connectivity. I had to setup a new tunnel and after calling and asking about it only to get a "IPv6 is not officially supported yet, you will receive an email when it is", have been with he.net ever since. That was probably 6+ months ago? So they're really rushing to get it out there. :(

    Alledgedly theur have been some tests in other regions, but nothing is
    happening here.

    I didn't notice it for a few days, and when I realized it hadn't
    come back in about a week, I just went back to my old setup.

    Well, at least something visible is happening at your end...

    I suppose. Although it was only a few week window 6+ months ago.

    Until I get an email from them stating it's up full time, or
    however they're planning on announcing it to the public.. I'll
    stick with my stable and reliable tunnel.

    I would do the same. Don't cancel those tunnels yet...

    I probably won't even cancel it the next time I try out native (obviously after I get some sort of information that it will be permanent from there on out). Just switch my router over and try it, and if it fails, at least all I have to do is change my router back to the tunnel, rather than having to set a whole new one up like I had to do last time.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20151203
  • From Joe Delahaye@1:249/303 to Michiel van der Vlist on Sun Dec 6 12:18:19 2015
    Re: IPv6 down?
    By: Michiel van der Vlist to Joe Delahaye on Sun Dec 06 2015 13:01:02

    It seems to be up again, at least for outgoing:

    - 06 Dec 01:01:03 [320] incoming from 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35 (51634)
    + 06 Dec 01:01:03 [2916] incoming session with 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35
    - 06 Dec 01:01:03 [2916] SYS The Lion's Den
    - 06 Dec 01:01:03 [2916] ZYZ Joe Delahaye
    - 06 Dec 01:01:03 [2916] LOC Trenton, Ont. Cdn
    - 06 Dec 01:01:03 [2916] NDL 115200,TCP,BINKP
    - 06 Dec 01:01:03 [2916] TIME Sat, 5 Dec 2015 19:01:03 -0500

    Perhaps a Sinterklaas present :)



    Outgoing also works:


    + 13:04 [828] outgoing session with 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef:24554
    - 13:04 [828] OPT CRAM-MD5-0d5467028d9dda1769fc9eca88e330ee
    + 13:04 [828] Remote requests MD mode
    - 13:04 [828] SYS The Lion's Den
    - 13:04 [828] ZYZ Joe Delahaye
    - 13:04 [828] LOC Trenton, Ont. Cdn
    - 13:04 [828] NDL 115200,TCP,BINKP
    - 13:04 [828] TIME Sun, 6 Dec 2015 07:04:17 -0500

    But... for that to work I need to enter the literal IPv6 adress in my binkd.cfg.

    You apparently have not managed yet to create an AAAA record for lionsdem.darktech.org. What is te problem?


    Darktech is not yet set up for that. I dont know if I regsitered another domain for Lionsden (if possible), if I can do that and have it go straight to my BBS server. I am unsure on how to do that. At the moment my delahaye.ca goes to the registrar, and I have a simple redirect page there that send it to my sytem here.

    ... Only dull people are brilliant at breakfast.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Joe Delahaye@1:249/303 to Nicholas Boel on Sun Dec 6 12:20:10 2015
    Re: Re: IPv6 down?
    By: Nicholas Boel to Joe Delahaye on Sun Dec 06 2015 07:13:55

    IPv6 is considered a Beta project. However, I was given a native

    Which means they're still very actively working to perfect it, which also means
    the connectivity could be shoddy at times.


    Its been in Beta for years now :) Perhaps waiting to see if any changes need to be made. I dont know.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Joe Delahaye@1:249/303 to Michiel van der Vlist on Sun Dec 6 16:44:53 2015
    Re: IPv6 down?
    By: Michiel van der Vlist to Joe Delahaye on Sun Dec 06 2015 13:01:02

    It seems to be up again, at least for outgoing:


    Here is the answer I got from tech support today

    Hi Joe,

    Looks like this happened when a core router was turned up and it was missing a specific IPv6 configuration which has now been fixed. It would've effected certain routes and depended on hitting the right LNS to make a connection.

    Sorry for the inconvenience this may have caused,
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Nicholas Boel@1:154/10 to Joe Delahaye on Sun Dec 6 18:42:20 2015
    Hello Joe,

    On 06 Dec 15 16:44, Joe Delahaye wrote to Michiel van der Vlist:

    Here is the answer I got from tech support today

    Hi Joe,

    Looks like this happened when a core router was turned up and it was missing a specific IPv6 configuration which has now been fixed. It would've effected certain routes and depended on hitting the right LNS
    to make a connection.

    Sorry for the inconvenience this may have caused,

    Wow. I'm actually quite impressed with that response. :)

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20151203
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Joe Delahaye@1:249/303 to Nicholas Boel on Sun Dec 6 23:01:46 2015
    Re: Re: IPv6 down?
    By: Nicholas Boel to Joe Delahaye on Sun Dec 06 2015 18:42:20

    Sorry for the inconvenience this may have caused,

    Wow. I'm actually quite impressed with that response. :)


    Me too, considering there is limited support for a beta program, but they had offered to talk me thru things as well if necessary.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Markus Reschke@2:240/1661 to Joe Delahaye on Mon Dec 7 11:49:04 2015
    Hello Joe!

    Dec 06 16:44 2015, Joe Delahaye wrote to Michiel van der Vlist:

    Here is the answer I got from tech support today

    Looks like this happened when a core router was turned up and it was missing a specific IPv6 configuration which has now been fixed. It would've effected certain routes and depended on hitting the right LNS
    to make a connection.

    A surprisingly straight response. And if you haven't noticed it yet, they are running a L2TP setup.

    Cheers,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Joe Delahaye@1:249/303 to Markus Reschke on Mon Dec 7 09:24:56 2015
    Re: IPv6 down?
    By: Markus Reschke to Joe Delahaye on Mon Dec 07 2015 11:49:04

    Looks like this happened when a core router was turned up and it was
    missing a specific IPv6 configuration which has now been fixed. It
    would've effected certain routes and depended on hitting the right
    LNS to make a connection.

    A surprisingly straight response. And if you haven't noticed it yet, they are running a L2TP setup.

    You could have fooled me :) I know very little about that side of the system.
    I don`t even know what an L2TP setup is.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Markus Reschke@2:240/1661 to Joe Delahaye on Mon Dec 7 15:29:50 2015
    Hi Joe!

    Dec 07 09:24 2015, Joe Delahaye wrote to Markus Reschke:

    You could have fooled me :) I know very little about that side of
    the system. I don`t even know what an L2TP setup is.

    There are two ways to get the PPPoE from the DSLAM to the access router. The old one is ATM and the newer one is L2TP. ATM requires an ATM network with ATM switches. L2TP is a tunnel protocol for OSI layer 2 and is IP based. The LNS ( L2TP Network Server) is the access router and endpoint of the L2TP tunnel with your PPPoE. It's just a virtual interface on that router.

    Regards,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Joe Delahaye@1:249/303 to Markus Reschke on Mon Dec 7 22:24:41 2015
    Re: IPv6 down?
    By: Markus Reschke to Joe Delahaye on Mon Dec 07 2015 15:29:50

    There are two ways to get the PPPoE from the DSLAM to the access router. The old one is ATM and the newer one is L2TP. ATM requires an ATM network with ATM switches. L2TP is a tunnel protocol for OSI layer 2 and is IP based. The LNS ( L2TP Network Server) is the access router and endpoint of the L2TP tunnel with your PPPoE. It's just a virtual interface on that router.

    Well, I learned something, but if it will stay in my head is another question :)
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Markus Reschke@2:240/1661 to Joe Delahaye on Tue Dec 8 19:13:00 2015
    Hi Joe!

    Dec 07 22:24 2015, Joe Delahaye wrote to Markus Reschke:

    Well, I learned something, but if it will stay in my head is another question :)

    Wait 'til I start talking BGP to you :)

    Cheers,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Benny Pedersen@1:261/38.20 to Joe Delahaye on Tue Dec 8 17:35:58 2015
    Hello Joe!

    07 Dec 2015 09:24, Joe Delahaye wrote to Markus Reschke:

    I don`t even know what an L2TP setup is.

    and i dont know what win64 is :=)

    possible santa is on way


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.3.0-gentoo (i686))
    * Origin: openvpn on its way here (1:261/38.20)
  • From Joe Delahaye@1:249/303 to Markus Reschke on Wed Dec 9 09:11:28 2015
    Re: IPv6 down?
    By: Markus Reschke to Joe Delahaye on Tue Dec 08 2015 19:13:00

    Well, I learned something, but if it will stay in my head is another
    question :)

    Wait 'til I start talking BGP to you :)


    It will likely go right over my head <G>

    ... I have a new philosophy. I'm only going to dread one day at a time.
    --- SBBSecho 2.30-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Benny Pedersen@1:261/38.20 to Joe Delahaye on Thu Dec 10 04:20:56 2015
    Hello Joe!

    09 Dec 2015 09:11, Joe Delahaye wrote to Markus Reschke:

    Wait 'til I start talking BGP to you :)
    It will likely go right over my head <G>

    Benny's Grand Parents ? :=)


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.3.0-gentoo (i686))
    * Origin: openvpn on its way here (1:261/38.20)
  • From Björn Felten@2:203/2 to Tommi Koivula on Wed Apr 5 15:27:46 2017
    Time for some IPv6 service again? 8-)

    ? 05 Apr 15:21:30 [1852] connection to 2:221/1@fidonet failed: {W32 API error 10060} Connection timed out
    05 Apr 15:21:30 [1852] trying rbb.ath.cx [88.114.128.113]:24554...
    05 Apr 15:21:30 [1852] connected




    ..

    --- 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 Tommi Koivula@2:221/360 to Bj”rn Felten on Wed Apr 5 17:00:17 2017

    Time for some IPv6 service again? 8-)

    There is always the old and reliable IPv4. 8-)

    ? 05 Apr 15:21:30 [1852] connection to 2:221/1@fidonet failed: {W32 API error 10060} Connection timed out
    05 Apr 15:21:30 [1852] trying rbb.ath.cx [88.114.128.113]:24554...
    05 Apr 15:21:30 [1852] connected

    But yes indeed, the linux box did the same thing than last time. Just rebooted it, please see what happens.

    You may also use the static addresses:

    [2001:470:27:a::2]
    [2001:41d0:401:3100::1030]

    as alternatives for my main system.

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 SeaMonkey/
    * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
  • From Björn Felten@2:203/2 to Tommi Koivula on Wed Apr 5 16:16:23 2017
    rebooted it, please see what happens.

    This happened:

    + 05 Apr 16:14:31 [3620] call to 2:221/1@fidonet
    05 Apr 16:14:31 [3620] trying rbb.ath.cx [2001:470:1f15:cb0:f1d0:2:221:1]...
    05 Apr 16:14:32 [3620] connected

    You may also use the static addresses:

    Nah, that's cheating! I rather stick to good old IPv4 if IPv6 fails. 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)