• Making IPv6 prio number one

    From Björn Felten@2:203/2 to Kees van Eeten on Fri Feb 10 00:57:09 2017
    Your system switched to IPv6 after a IPv4 connect failed. Apparently
    IPv4 connects have priority over IPv6. The norm is the otherway aroud.

    You are correct (as usual), I was just about to write about it.

    So now I'm at shame for not paying attention when you guys helped out another sysop with the same priority problem.

    Anyone feel like making a recap? I'm using netsh on an old WinXP. What do you need to see/know about my system.



    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 11:37:30 2017
    Hello Bjrn,

    On Friday February 10 2017 00:57, you wrote to Kees van Eeten:

    Anyone feel like making a recap? I'm using netsh on an old WinXP.
    What do you need to see/know about my system.


    netsh int ipv6 show prefixpol

    What does it say?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 12:40:59 2017
    MvdV> netsh int ipv6 show prefixpol

    MvdV> What does it say?

    Aktivt tillstnd lses...

    Prioritet Etikt Prefix
    ---------- ----- --------------------------------
    5 5 2001::/32
    10 4 ::ffff:0:0/96
    20 3 ::/96
    30 2 2002::/16
    40 1 ::/0
    50 0 ::1/128





    ..

    --- 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 Kees van Eeten@2:280/5003.4 to Bj÷rn Felten on Fri Feb 10 13:02:46 2017
    Hello Bjrn!

    10 Feb 17 00:57, you wrote to me:

    You are correct (as usual),

    Blush.

    I was just about to write about it.

    It took me some time to realize, what was wrong, as well.

    So now I'm at shame for not paying attention when you guys helped
    out
    another sysop with the same priority problem.

    Anyone feel like making a recap? I'm using netsh on an old WinXP. What do you need to see/know about my system.

    I only looked at what could be done under Linux. I only use WinXp to update
    gadgets

    But as for what happened in your situation, I would care less. It worked
    as it should, even if it does not gives priority to IPv6.

    A redundant connection was offered and a switch was made when one connection
    did not work.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Björn Felten@2:203/2 to Kees van Eeten on Fri Feb 10 14:09:58 2017
    A redundant connection was offered and a switch was made when one connection did not work.

    True! I'm rather happy about it. Previously I was under the impression that my system couldn't make any outgoing IPv6 connections at all, but now we know that it can when needed.






    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 15:05:46 2017
    Hello Bjrn,

    On Friday February 10 2017 12:40, you wrote to me:

    Aktivt tillstnd lses...

    Prioritet Etikt Prefix
    ---------- ----- --------------------------------
    5 5 2001::/32
    10 4 ::ffff:0:0/96
    20 3 ::/96
    30 2 2002::/16
    40 1 ::/0
    50 0 ::1/128

    Same here:

    Der aktive Status wird abgefragt...

    Vorgnger Label Prfix
    ---------- ----- ---------------------
    5 5 2001::/32
    10 4 ::ffff:0:0/96
    20 3 ::/96
    30 2 2002::/16
    40 1 ::/0
    50 0 ::1/128

    So we can eliminate that.

    How about the interface priorities. It is my understandung that yiu gave configured the tunnel on your XP machine, not on your router. In that case, it is a seperate interface.

    There is way to prioritize the interfaces.

    http://www.geekingatschool.com/2010/09/windows-xp-network-adapter-priority/


    Did that help?

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 15:16:06 2017
    Hello Bjrn,

    On Friday February 10 2017 14:09, you wrote to Kees van Eeten:

    A redundant connection was offered and a switch was made when
    one connection did not work.

    True! I'm rather happy about it. Previously I was under the
    impression that my system couldn't make any outgoing IPv6 connections
    at all, but now we know that it can when needed.

    What happens if you add the '-6' option for my node in your binkd configuration?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 16:00:50 2017
    Hello Bjrn,

    Friday February 10 2017 15:16, I wrote to you:

    What happens if you add the '-6' option for my node in your binkd configuration?

    BTW, I have changed your status in the list of IPv6 nodes from "IO" to "PO4"


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 16:29:00 2017
    MvdV> Did that help?

    Negatory.





    ..

    --- 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 Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 16:30:26 2017
    MvdV> It is my understandung that yiu gave configured the tunnel on your XP
    MvdV> machine, not on your router.

    The XP machine *is* my router. That's why I'm so reluctant to abandon it.




    ..

    --- 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 Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 16:33:19 2017
    MvdV> What happens if you add the '-6' option for my node in your binkd
    MvdV> configuration?

    Where and how do I do that? I guess I should look into my password file, but I can't really see where in there I can add options.

    Sorry, but I'm still a n00b when binkd is concerned. :(



    ..

    --- 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 Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 16:34:28 2017
    MvdV> BTW, I have changed your status in the list of IPv6 nodes from "IO" to
    MvdV> "PO4"

    Thanks. That sounds like a correct flag for now.



    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 17:20:15 2017
    Hello Bjrn,

    On Friday February 10 2017 16:29, you wrote to me:

    MvdV>> Did that help?

    Negatory.

    In the same menu where you can change the proirity of the interfaces, you cab also change the priority for the protocols. Per interface.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 17:21:34 2017
    Hello Bjrn,

    On Friday February 10 2017 16:30, you wrote to me:

    MvdV>> It is my understandung that yiu gave configured the tunnel on
    MvdV>> your XP machine, not on your router.

    The XP machine *is* my router.

    Ah yes, I had forgotten that.

    I am afraid you are on your own then. Windows machines make lousy routers and XP's implementation of IPv6 is incomplete.

    That's why I'm so reluctant to abandon it.

    Perhaps you should consider getting a real router nontheless...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 17:26:00 2017
    Hello Bjrn,

    On Friday February 10 2017 16:33, you wrote to me:

    MvdV>> What happens if you add the '-6' option for my node in your
    MvdV>> binkd configuration?

    Where and how do I do that? I guess I should look into my password file, but I can't really see where in there I can add options.

    I do not use a separate password file, in my config file it is something like this:

    node 2:5020/9696 -6 skovpen.org -

    Sorry, but I'm still a n00b when binkd is concerned. :(

    There is the BINKD echo for that. There are some guys hanging out there that know a lot about it. And you may want to second my proposal for the -64 and -46 options... :-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Markus Reschke@2:240/1661 to Bj÷rn Felten on Fri Feb 10 17:02:20 2017
    Hi Bjrn!

    Feb 10 16:30 2017, Bjrn Felten wrote to Michiel van der Vlist:

    The XP machine *is* my router. That's why I'm so reluctant to abandon
    it.

    Ouch! Please do yourself a favour and get a cheap router supported by OpenWrt or go for pf/opnSense.

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Kees van Eeten@2:280/5003.4 to Bj÷rn Felten on Fri Feb 10 17:47:36 2017
    Hello Bjrn!

    10 Feb 17 16:33, you wrote to Michiel van der Vlist:


    MvdV>> What happens if you add the '-6' option for my node in your binkd
    MvdV>> configuration?

    Where and how do I do that? I guess I should look into my password file, but I can't really see where in there I can add options.

    Sorry, but I'm still a n00b when binkd is concerned. :(

    Node 2:280/5555 -6 hostname.tld password

    or when you rely on binkp.net DNSserver

    Node 2:280/5555 -6 * password

    or if you derive if you rely on a binkp.txt nodelist

    Node 2:230/5555 -6 - password


    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Tommi Koivula@2:221/1.1 to Björn Felten on Fri Feb 10 19:38:36 2017

    10 Feb 17 16:30:26, you wrote to Michiel van der Vlist:

    MvdV>> It is my understandung that yiu gave configured the tunnel on your
    MvdV>> XP machine, not on your router.

    The XP machine *is* my router.

    Ouch!

    That's why I'm so reluctant to abandon it.

    That's why it should be abandoned asap.

    'Tommi

    ... he.net certified sage
    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)
  • From Björn Felten@2:203/2 to Kees van Eeten on Fri Feb 10 19:10:15 2017
    Node 2:230/5555 -6 - password

    That's me! Albeit not Michiel... 8-)

    But that did he trick it seems. Thanks!




    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Fri Feb 10 19:22:47 2017
    Hello Bjrn,

    On Friday February 10 2017 19:10, you wrote to Kees van Eeten:

    Node 2:230/5555 -6 - password

    That's me! Albeit not Michiel... 8-)

    But that did he trick it seems. Thanks!

    Check!

    - 10 Feb 19:11:20 [624] incoming from 2002:5ae7:9e93::5ae7:9e93 (1115)
    + 10 Feb 19:11:20 [2444] incoming session with 2002:5ae7:9e93::5ae7:9e93
    - 10 Feb 19:11:21 [2444] SYS Felten's Sharp System
    - 10 Feb 19:11:21 [2444] ZYZ Bjrn Felten
    - 10 Feb 19:11:21 [2444] LOC Sve, Sweden
    - 10 Feb 19:11:21 [2444] NDL 115200,TCP,BINKP
    - 10 Feb 19:11:21 [2444] TIME Fri, 10 Feb 2017 19:11:18 +0100


    The problem with this "solution" is that it is IPv6 ONLY. No fall back to IPv4 if IPv5 fails.

    That is why I proposed the -64 and -46 options in the binkd echo.

    Eh...

    - 10 Feb 19:11:20 [624] incoming from 2002:5ae7:9e93::5ae7:9e93 (1115)

    Hey wait... That is not a he.net tunnel address, it is a 6to4 address! There is something rotten in the state of Sweden....


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Fri Feb 10 22:41:23 2017
    MvdV> The problem with this "solution" is that it is IPv6 ONLY. No fall back
    MvdV> to IPv4 if IPv5 fails.

    Ouch! That's not good. Back to the old config.

    MvdV> Hey wait... That is not a he.net tunnel address, it is a 6to4 address!
    MvdV> There is something rotten in the state of Sweden....

    LOL! I give up.


    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sat Feb 11 01:21:43 2017
    Hello Bjrn,

    On Friday February 10 2017 22:41, you wrote to me:

    MvdV>> The problem with this "solution" is that it is IPv6 ONLY. No
    MvdV>> fall back to IPv4 if IPv6 fails.

    Ouch! That's not good. Back to the old config.

    That is why I propesed the -64 and -46 options...

    MvdV>> Hey wait... That is not a he.net tunnel address, it is a 6to4
    MvdV>> address! There is something rotten in the state of Sweden....

    Apparently your Winxp has automatically configured a 6to4 tunnel. And it has priority over the he.net tunnel.

    LOL! I give up.

    Don't.

    netsh interface ipv6 6to4 set state disabled


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Sat Feb 11 16:53:23 2017
    Hello Bjrn,

    On Saturday February 11 2017 01:21, I wrote to you:

    Apparently your Winxp has automatically configured a 6to4 tunnel. And
    it has priority over the he.net tunnel.

    And it still seems to be up:

    D:\FIDO\logs>ping 2002:5ae7:9e93::5ae7:9e93

    Ping wird ausgefhrt fr 2002:5ae7:9e93::5ae7:9e93 mit 32 Bytes Daten:

    Antwort von 2002:5ae7:9e93::5ae7:9e93: Zeit=76ms
    Antwort von 2002:5ae7:9e93::5ae7:9e93: Zeit=77ms
    Antwort von 2002:5ae7:9e93::5ae7:9e93: Zeit=75ms
    Antwort von 2002:5ae7:9e93::5ae7:9e93: Zeit=75ms

    Ping-Statistik fr 2002:5ae7:9e93::5ae7:9e93:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
    Ca. Zeitangaben in Millisek.:
    Minimum = 75ms, Maximum = 77ms, Mittelwert = 75ms

    LOL! I give up.

    Don't.

    netsh interface ipv6 6to4 set state disabled

    Before you do, tell us what "ipconfig /all" shows.

    C'mon, don't give up so quickly.

    Cheers, Michiel


    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sat Feb 11 17:55:24 2017
    MvdV> Before you do, tell us what "ipconfig /all" shows.

    Well, this is after (before shows that 6to4 with the IPv6 address you found):

    IP-konfiguration fr Windows



    Vrddatornamn . . . . . . . . . . : dell

    Primrt DNS-suffix . . . . . . . :

    Nodtyp . . . . . . . . . . . . . : Blandad

    IP-routning aktiverat . . . . . . : Ja

    WINS-proxy aktiverat . . . . . . : Nej



    Ethernet-kort Kllaren:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Netelligent 10/100TX PCI UTP Controller

    Fysisk adress . . . . . . . . . . : 00-08-C7-0D-D2-AE

    DHCP aktiverat . . . . . . . . . : Nej

    IP-adress . . . . . . . . . . . . : 192.168.0.1

    Ntmask . . . . . . . . . . . . . : 255.255.255.0

    IP-adress . . . . . . . . . . . . : fe80::208:c7ff:fe0d:d2ae%4

    Standard-gateway . . . . . . . . :

    DNS-servrar . . . . . . . . . . . : 192.168.0.1

    fec0:0:0:ffff::1%1

    fec0:0:0:ffff::2%1

    fec0:0:0:ffff::3%1



    Ethernet-kort ADSL:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC

    Fysisk adress . . . . . . . . . . : 00-50-FC-A9-81-03

    DHCP aktiverat . . . . . . . . . : Ja

    Autokonfiguration aktiverat . . . : Ja

    IP-adress . . . . . . . . . . . . : 90.231.158.147

    Ntmask . . . . . . . . . . . . . : 255.255.255.0

    IP-adress . . . . . . . . . . . . : fe80::250:fcff:fea9:8103%5

    Standard-gateway . . . . . . . . : 90.231.158.1

    DHCP-server . . . . . . . . . . . : 217.209.153.65

    DNS-servrar . . . . . . . . . . . : 8.8.8.8

    208.67.220.220

    fec0:0:0:ffff::1%1

    fec0:0:0:ffff::2%1

    fec0:0:0:ffff::3%1

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat

    Lnet erhlls . . . . . . . . . . : den 11 februari 2017 16:53:35

    Lnet upphr . . . . . . . . . . : den 11 februari 2017 17:13:35



    Tunnel-kort he.net:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Configured Tunnel Interface

    Fysisk adress . . . . . . . . . . : 5A-E7-9E-93

    DHCP aktiverat . . . . . . . . . : Nej

    IP-adress . . . . . . . . . . . . : 2001:470:27:302::2

    IP-adress . . . . . . . . . . . . : fe80::7:5ae7:9e93%7

    Standard-gateway . . . . . . . . :

    DNS-servrar . . . . . . . . . . . : fec0:0:0:ffff::1%3

    fec0:0:0:ffff::2%3

    fec0:0:0:ffff::3%3

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat



    Tunnel-kort Teredo Tunneling Pseudo-Interface:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

    Fysisk adress . . . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

    DHCP aktiverat . . . . . . . . . : Nej

    IP-adress . . . . . . . . . . . . : fe80::ffff:ffff:fffd%6

    Standard-gateway . . . . . . . . :

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat



    Tunnel-kort 6to4 Tunneling Pseudo-Interface:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface

    Fysisk adress . . . . . . . . . . : 5A-E7-9E-93

    DHCP aktiverat . . . . . . . . . : Nej

    Standard-gateway . . . . . . . . :

    DNS-servrar . . . . . . . . . . . : fec0:0:0:ffff::1%1

    fec0:0:0:ffff::2%1

    fec0:0:0:ffff::3%1

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat



    Tunnel-kort Automatic Tunneling Pseudo-Interface:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

    Fysisk adress . . . . . . . . . . : 5A-E7-9E-93

    DHCP aktiverat . . . . . . . . . : Nej

    IP-adress . . . . . . . . . . . . : fe80::5efe:90.231.158.147%2

    Standard-gateway . . . . . . . . : ::216.66.80.90

    DNS-servrar . . . . . . . . . . . : fec0:0:0:ffff::1%1

    fec0:0:0:ffff::2%1

    fec0:0:0:ffff::3%1

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat



    Tunnel-kort Automatic Tunneling Pseudo-Interface:



    Anslutningsspecifika DNS-suffix . :

    Beskrivning . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

    Fysisk adress . . . . . . . . . . : C0-A8-00-01

    DHCP aktiverat . . . . . . . . . : Nej

    IP-adress . . . . . . . . . . . . : fe80::5efe:192.168.0.1%2

    Standard-gateway . . . . . . . . : ::216.66.80.90

    DNS-servrar . . . . . . . . . . . : fec0:0:0:ffff::1%1

    fec0:0:0:ffff::2%1

    fec0:0:0:ffff::3%1

    NetBIOS ver TCPIP. . . . . . . . : Inaktiverat





    ..

    --- 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/6 to Bj÷rn Felten on Sat Feb 11 21:27:44 2017
    Bjrn Felten : Michiel van der Vlist :

    MvdV> Before you do, tell us what "ipconfig /all" shows.

    Well, this is after (before shows that 6to4 with the IPv6 address you found):

    21:22 [3164] BEGIN, binkd/1.1a-95/CYGWIN_NT-5.2 -pP 203/2 binkd.cfg
    21:22 [3164] creating a poll for 2:203/2@fidonet (`d' flavour)
    21:22 [3164] clientmgr started
    21:22 [3864] call to 2:203/2@fidonet
    21:22 [3864] trying eljaco.se [2001:470:27:302::2]:24555...
    21:22 [3864] connection to 2:203/2@fidonet failed: Connection timed out
    21:22 [3864] trying eljaco.se [90.231.158.147]:24555...
    21:22 [3864] connected
    21:22 [3864] outgoing session with eljaco.se:24555 [90.231.158.147]
    21:23 [3864] OPT CRAM-MD5-f3fe4c97024a326d5ca57b0a5d822dee
    21:23 [3864] Remote requests MD mode
    21:23 [3864] SYS Felten's Sharp System

    I cannot connect by ipv6. Did you reboot?

    'Tommi

    ---
    * Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)
  • From Björn Felten@2:203/2 to Tommi Koivula on Sat Feb 11 22:13:34 2017
    I cannot connect by ipv6. Did you reboot?

    No, I messed around. :(



    ..

    --- 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 Björn Felten@2:203/2 to Tommi Koivula on Sat Feb 11 22:53:40 2017
    I cannot connect by ipv6. Did you reboot?

    Looks like it's working now, no?

    PING eljaco.se(bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net) 56 data bytes
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=1 ttl=126 time=55.2 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=2 ttl=126 time=53.0 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=3 ttl=126 time=51.0 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=4 ttl=126 time=51.0 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=5 ttl=126 time=50.7 ms

    --- eljaco.se ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4006ms
    rtt min/avg/max/mdev = 50.740/52.246/55.275/1.724 ms




    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sat Feb 11 23:34:43 2017
    Hello Bjrn,

    On Saturday February 11 2017 22:53, you wrote to Tommi Koivula:

    I cannot connect by ipv6. Did you reboot?

    Looks like it's working now, no?

    Yep!

    + 23:31 [2132] call to 2:203/0@fidonet
    23:31 [2132] trying eljaco.se [2001:470:27:302::2]:24555...
    23:31 [2132] connected
    + 23:31 [2132] outgoing session with eljaco.se:24555 [2001:470:27:302::2]
    - 23:31 [2132] OPT CRAM-MD5-c47e26c028d5ee0f8a6b390d24ebf1ee
    + 23:31 [2132] Remote requests MD mode
    - 23:31 [2132] SYS Felten's Sharp System
    - 23:31 [2132] ZYZ Bjrn Felten
    - 23:31 [2132] LOC Sve, Sweden
    - 23:31 [2132] NDL 115200,TCP,BINKP
    - 23:31 [2132] TIME Sat, 11 Feb 2017 23:31:58 +0100
    - 23:31 [2132] VER binkd/1.1a-65/Win32 binkp/1.1

    So how anout outgoing?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sat Feb 11 23:59:13 2017
    MvdV> So how about outgoing?

    No luck so far. I probably have to sleep on it... 9-)



    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 00:06:55 2017
    Hello Bjrn,

    On Saturday February 11 2017 23:59, you wrote to me:

    MvdV>> So how about outgoing?

    No luck so far. I probably have to sleep on it... 9-)

    What happens if you use the -6 option? Does it use the he.net tunnel?

    ( Just to test if this os a priority issue or if ougoing via he.net does not work at all)

    Can you connect to 2:280/5006? IPv6 only node. Can you ping fido6.ddutch.nl?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 00:32:51 2017
    MvdV> What happens if you use the -6 option? Does it use the he.net tunnel?

    + 12 Feb 00:21:28 [752] call to 2:280/5555@fidonet
    12 Feb 00:21:28 [752] trying fido.vlist.eu [2001:1c02:1100:fd00:215:60ff:fe52:213d]...
    ? 12 Feb 00:21:49 [752] connection to 2:280/5555@fidonet failed: {W32 API error 10065} A socket operation was attempted to an unreachable host

    MvdV> ( Just to test if this os a priority issue or if ougoing via he.net does
    MvdV> not work at all)

    It seems like it's not working at all, now that I've disabled the 6to4 adapter.

    MvdV> Can you connect to 2:280/5006?

    No.

    MvdV> Can you ping fido6.ddutch.nl?

    Now *that* was interesting. I can ping it successfully from one of my other computers (still running a SixXS tunnel):

    Pinging fido6.ddutch.nl [2001:980:42ea:1:f1d0:2:280:5006]
    from 2001:16d8:ff00:2f8::2 with 32 bytes of data:

    Reply from 2001:980:42ea:1:f1d0:2:280:5006: bytes=32 time=95ms
    Reply from 2001:980:42ea:1:f1d0:2:280:5006: bytes=32 time=93ms
    Reply from 2001:980:42ea:1:f1d0:2:280:5006: bytes=32 time=94ms
    Reply from 2001:980:42ea:1:f1d0:2:280:5006: bytes=32 time=96ms

    But from my main machine, running the he.net tunnel, I get this:

    Skickar ping till fido6.ddutch.nl [2001:980:42ea:1:f1d0:2:280:5006]
    frn fe80::250:fcff:fea9:8103%5 med 32 byte data:

    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.

    So now I at least know what's wrong...




    ..

    --- 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 Bjrn Felten on Sun Feb 12 09:07:15 2017
    On 11.2.2017 23:13, Björn Felten : Tommi Koivula :

    I cannot connect by ipv6. Did you reboot?

    No, I messed around. :(

    Cool! :)

    tommi@rpi:~$ ping6 -c 5 eljaco.se
    PING eljaco.se(bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net) 56 data bytes
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=1
    ttl=125 time=70.3 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=2
    ttl=125 time=75.5 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=3
    ttl=125 time=71.3 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=4
    ttl=125 time=73.0 ms
    64 bytes from bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net: icmp_seq=5
    ttl=125 time=70.0 ms

    --- eljaco.se ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    rtt min/avg/max/mdev = 70.041/72.054/75.538/2.025 ms

    --- Mozilla/5.0 (OS/2; Warp 4.5; rv:31.0) Gecko/20100101 SeaMonkey/2.28
    * Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 11:13:32 2017
    Hello Bjrn,

    On Sunday February 12 2017 00:32, you wrote to me:

    But from my main machine, running the he.net tunnel, I get this:

    Skickar ping till fido6.ddutch.nl [2001:980:42ea:1:f1d0:2:280:5006]
    frn fe80::250:fcff:fea9:8103%5 med 32 byte data:

    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.

    So now I at least know what's wrong...

    Something wrong with the he.net tunnel. Odd, most people having IPv6 problems, have problems with incoming, but are the exception, your problem is outgoing.

    So... for the moment your are back to "IO"?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 11:57:24 2017
    MvdV> So... for the moment your are back to "IO"?

    Unless I ant to enable the 6to4, yes, unfortunately it seems so.



    ..

    --- 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/6 to Michiel van der Vlist on Sun Feb 12 13:08:02 2017
    Michiel van der Vlist : Bjrn Felten :

    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.
    Svar frn fe80::250:fcff:fea9:8103%5: Mladressen kan inte ns.

    So now I at least know what's wrong...

    Something wrong with the he.net tunnel.

    Nope. His tunnel is working fine:

    tommi@one:~$ ping6 -c4 2001:470:27:302::1
    PING 2001:470:27:302::1(2001:470:27:302::1) 56 data bytes
    64 bytes from 2001:470:27:302::1: icmp_seq=1 ttl=60 time=59.3 ms
    64 bytes from 2001:470:27:302::1: icmp_seq=2 ttl=60 time=62.7 ms
    64 bytes from 2001:470:27:302::1: icmp_seq=3 ttl=60 time=56.1 ms
    64 bytes from 2001:470:27:302::1: icmp_seq=4 ttl=60 time=55.7 ms

    tommi@one:~$ ping6 -c4 2001:470:27:302::2
    PING 2001:470:27:302::2(2001:470:27:302::2) 56 data bytes
    64 bytes from 2001:470:27:302::2: icmp_seq=1 ttl=123 time=106 ms
    64 bytes from 2001:470:27:302::2: icmp_seq=2 ttl=123 time=105 ms
    64 bytes from 2001:470:27:302::2: icmp_seq=3 ttl=123 time=104 ms
    64 bytes from 2001:470:27:302::2: icmp_seq=4 ttl=123 time=107 ms

    He need to get rid of teredo and 6to4 and all that shit. And reboot. :)

    'Tommi

    ---
    * Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sun Feb 12 13:05:00 2017
    Hello Tommi,

    On Sunday February 12 2017 13:08, you wrote to me:

    Something wrong with the he.net tunnel.

    Nope. His tunnel is working fine:

    tommi@one:~$ ping6 -c4 2001:470:27:302::1
    PING 2001:470:27:302::1(2001:470:27:302::1) 56 data bytes
    64 bytes from 2001:470:27:302::1: icmp_seq=1 ttl=60 time=59.3 ms

    For incoming. But why can't he make outgoing IPv6 via the tunnel?

    He need to get rid of teredo and 6to4 and all that shit. And reboot.
    :)

    Perhaps.

    I think the best way is to stop using XP as a router and get a decent dedicated piece of hardware to do the routing.

    We will see...

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Tony Langdon@3:633/410 to Björn Felten on Sun Feb 12 23:49:00 2017
    Bjrn Felten wrote to Michiel van der Vlist <=-

    The XP machine *is* my router. That's why I'm so reluctant to
    abandon it.

    One role I won't put Windows in. I'll setup a Linux box first, these days, something like an embedded style PC that runs on stray electrons. :-) Note, I didn't say a R-Pi, its I/O performance is no good for that role. :)


    ... Almost everything in life is easier to get into than out of.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Björn Felten@2:203/2 to Tommi Koivula on Sun Feb 12 14:21:59 2017
    He need to get rid of teredo and 6to4 and all that shit. And reboot. :)

    So here's what I just did:

    netsh int ipv6 6to4 set state disabled
    netsh int ipv6 set teredo disable
    netsh int ipv6 isatap set state state=disabled
    netsh int ipv6 add address "he.net" 2001:470:27:302::2
    netsh int ipv6 add route 2001:470:27:302::2/64 he.net
    netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes

    And now it seems like I actually made an IPv6 call to your system, or did I misread the log in the DOS window as it scrolled by?




    ..

    --- 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 Björn Felten@2:203/2 to Tommi Koivula on Sun Feb 12 14:28:41 2017
    He need to get rid of teredo and 6to4 and all that shit. And reboot. :)

    Oh yes! Now we're talking!

    Skickar ping till fido6.ddutch.nl [2001:980:42ea:1:f1d0:2:280:5006]
    frn 2001:470:27:302::2 med 32 byte data:

    Svar frn 2001:980:42ea:1:f1d0:2:280:5006: byte=32 tid=90ms
    Svar frn 2001:980:42ea:1:f1d0:2:280:5006: byte=32 tid=89ms
    Svar frn 2001:980:42ea:1:f1d0:2:280:5006: byte=32 tid=90ms
    Svar frn 2001:980:42ea:1:f1d0:2:280:5006: byte=32 tid=91ms

    Ping-statistik fr 2001:980:42ea:1:f1d0:2:280:5006:
    Paket: skickade = 4, mottagna = 4, frlorade = 0 (0 % frlust),

    Ungefrlig frfluten tid i millisekunder:
    Minsta = 89ms, hgsta = 91ms, medel = 90ms


    You are my hero, Tommi! <3



    ..

    --- 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 Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 14:31:06 2017
    MvdV> I think the best way is to stop using XP as a router and get a decent
    MvdV> dedicated piece of hardware to

    I know you are. But where's the challenge in that? 8-)

    My present XP based setup is almost 20 years old, surely you don't think I'll abandon that challenge just because I stumble upon some hurdles on the way...?



    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 14:27:27 2017
    Hello Bjrn,

    On Sunday February 12 2017 14:21, you wrote to Tommi Koivula:

    So here's what I just did:

    netsh int ipv6 6to4 set state disabled
    netsh int ipv6 set teredo disable
    netsh int ipv6 isatap set state state=disabled
    netsh int ipv6 add address "he.net" 2001:470:27:302::2
    netsh int ipv6 add route 2001:470:27:302::2/64 he.net
    netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes

    OK...

    And now it seems like I actually made an IPv6 call to your system,
    or did I misread the log in the DOS window as it scrolled by?

    I went through my binkd logs hunting for incoming from your he.net address. This is whatI found:

    D:\FIDO\logs>grep "incoming from 2001:470:27:302::2" binkd.l??
    File BINKD.L19:
    - 28 Nov 09:16:18 [2420] incoming from 2001:470:27:302::2 (1030)
    File BINKD.LOG:
    - 11 Feb 16:49:52 [3828] incoming from 2001:470:27:302::2 (1156)
    - 11 Feb 17:16:26 [3828] incoming from 2001:470:27:302::2 (1169)
    - 11 Feb 17:33:03 [3828] incoming from 2001:470:27:302::2 (1178)
    - 11 Feb 17:57:17 [3828] incoming from 2001:470:27:302::2 (1201)
    - 11 Feb 18:30:49 [3828] incoming from 2001:470:27:302::2 (1221)
    - 11 Feb 20:24:44 [3828] incoming from 2001:470:27:302::2 (1259)
    - 11 Feb 20:29:25 [3828] incoming from 2001:470:27:302::2 (1263)
    - 11 Feb 21:40:38 [3828] incoming from 2001:470:27:302::2 (1283)
    - 11 Feb 21:42:54 [3828] incoming from 2001:470:27:302::2 (1287)
    - 11 Feb 21:48:44 [3828] incoming from 2001:470:27:302::2 (1294)
    - 11 Feb 22:03:24 [3828] incoming from 2001:470:27:302::2 (1308)

    And a few minutes ago:

    - 12 Feb 14:23:29 [876] incoming from 2001:470:27:302::2 (1032)
    + 12 Feb 14:23:29 [4060] incoming session with 2001:470:27:302::2
    - 12 Feb 14:23:30 [4060] SYS Felten's Sharp System
    - 12 Feb 14:23:30 [4060] ZYZ Bjrn Felten
    - 12 Feb 14:23:30 [4060] LOC Sve, Sweden
    - 12 Feb 14:23:30 [4060] NDL 115200,TCP,BINKP
    - 12 Feb 14:23:30 [4060] TIME Sun, 12 Feb 2017 14:23:24 +0100

    Yep, that seems to have done it. But it seemed to have worked occasionally before. My guess is that you do not remember what you did on 28 of November... :-)

    OK, don't change anything for now and we will see if it ios stable...

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 14:47:46 2017
    MvdV> My guess is that you do not remember what you did on 28 of November... :-)

    I know perfectly well what I did that day. That's when I tried to change my Dell (the XP router) from using the SixXS tunnel to the he.net tunnel. Using the totally wrong suggestion they had on their web site for XP SP3 systems was a big mistake.

    Now, thanks to Tommi, Kees and you and examining the SixXS AICCU tunnel commands, it seems like I'm finally managed to get it working.

    Don't you think it's worth while to demonstrate that you can get full IPv6 capability even with a 15yo XP setup?

    We all know how reluctant fido sysops are to totally abandon their decades old setups (hard- as well as software) just to get IPv6 capability -- now here's living proof that it can be done without scrapping the working system. No?



    ..

    --- 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 Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 15:00:58 2017
    MvdV> So... for the moment your are back to "IO"?

    Have I earned my brownie now...? 8-)

    And no, no need really to hatch a new file for the Snooze for that particular reason...



    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 14:40:00 2017
    Hello Bjrn,

    On Sunday February 12 2017 14:31, you wrote to me:

    My present XP based setup is almost 20 years old, surely you don't think I'll abandon that challenge just because I stumble upon some
    hurdles on the way...?

    Ah, thst's the spirit! ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Kees van Eeten@2:280/5003.4 to Bj÷rn Felten on Sun Feb 12 15:18:30 2017
    Hello Bjrn!

    12 Feb 17 15:00, you wrote to Michiel van der Vlist:

    MvdV>> So... for the moment your are back to "IO"?

    Have I earned my brownie now...? 8-)

    Only the points, not the whole girl. ;)

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Björn Felten@2:203/2 to Kees van Eeten on Sun Feb 12 15:29:21 2017
    Only the points, not the whole girl. ;)

    Darn! 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 15:20:05 2017
    Hello Bjrn,

    On Sunday February 12 2017 15:00, you wrote to me:

    MvdV>> So... for the moment your are back to "IO"?

    Have I earned my brownie now...? 8-)

    Yep!

    And no, no need really to hatch a new file for the Snooze for that particular reason...

    It is automatic. It would be an effort to intercept it...

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sun Feb 12 15:42:11 2017
    MvdV> Ah, that's the spirit! ;-)

    Thanks!

    Now, considering that a vast amount of FTN systems still probably runs on an XP setup(?), can we perhaps help those willing to try a tunnel through all the hoops they'll encounter?

    I know that you are probably one of the most knowledgeable netsh experts amongst us; what if we analyse all the netsh commands needed to get an XP system from scratch and create a generic one that lacks the mistakes SixXS as well as he.net has made?

    As a basis I would use this:

    netsh int ipv6 install

    That's obvious.

    netsh int ipv6 6to4 set state disabled
    netsh int ipv6 set teredo disable
    netsh int ipv6 isatap set state state=disabled

    I would really want a total delete function here, if nothing else but to clean up the ipconfig /all response.

    netsh int ipv6 add address "he.net" 2001:470:27:302::2
    netsh int ipv6 add route 2001:470:27:302::2/64 he.net
    netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes

    And here is probably where we need to put a lot of comments. For starters, there's no IPv4 addresses here, so I guess it's working for me because I added it somewhere else along the line.

    RFC

    ..

    --- 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/1.1 to Bj÷rn Felten on Sun Feb 12 18:52:34 2017
    Hi Bjrn.

    12 Feb 17 14:21:58, you wrote to me:

    He need to get rid of teredo and 6to4 and all that shit. And reboot.
    :)

    So here's what I just did:

    netsh int ipv6 6to4 set state disabled
    netsh int ipv6 set teredo disable
    netsh int ipv6 isatap set state state=disabled
    netsh int ipv6 add address "he.net" 2001:470:27:302::2
    netsh int ipv6 add route 2001:470:27:302::2/64 he.net
    netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes

    And now it seems like I actually made an IPv6 call to your system, or did I misread the log in the DOS window as it scrolled by?

    Connected by IPv6 at 2:221/1. :)

    'Tommi

    ... he.net certified sage
    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)
  • From Tommi Koivula@2:221/6 to Björn Felten on Sun Feb 12 20:16:28 2017
    Hi Bjrn.

    12 Feb 17 14:31:06, you wrote to Michiel van der Vlist:

    MvdV>> I think the best way is to stop using XP as a router and get a decent
    MvdV>> dedicated piece of hardware to

    I know you are. But where's the challenge in that? 8-)
    My present XP based setup is almost 20 years old,

    Not quite...

    https://en.wikipedia.org/wiki/Windows_XP

    I barely works as a router but it sure isn't doing it very good. How about firewall? Do you have any other firewall than the XP internal thing?

    It is not very wise to connect XP directly to the Big Bad Internet.

    'Tommi

    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
  • From Björn Felten@2:203/2 to Tommi Koivula on Sun Feb 12 21:15:27 2017
    My present XP based setup is almost 20 years old,

    Not quite...

    Well, it started as an NT system, but you are right, it's more like 15 years as an XP system.

    I barely works as a router but it sure isn't doing it very good.

    I've never had any problems with it -- on the contrary.

    How about firewall? Do you have any other firewall than the XP internal thing?

    No, it's the old firewall from the NT system I inherited from Gteborg city (the first owner of this computer). It's nothing like the XP ditto.

    It is not very wise to connect XP directly to the Big Bad Internet.

    That depends entirely on the system operator. If you don't know your way around it's not wise to connect directly to the Big Bad Internet, period.


    ..

    --- 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 Michiel van der Vlist@2:280/5555 to Björn Felten on Sun Feb 12 23:55:43 2017
    Hello Bjrn,

    On Sunday February 12 2017 14:47, you wrote to me:

    Don't you think it's worth while to demonstrate that you can get
    full IPv6 capability even with a 15yo XP setup?

    We all know how reluctant fido sysops are to totally abandon their decades old setups (hard- as well as software) just to get IPv6
    capability -- now here's living proof that it can be done without scrapping the working system. No?

    Well.. yes and no... Yes, you do have a fully functional Fidonet IPv6 connectable node. It can accept incoming binkp connects over IPv6 and it can also make outgoing IPv6 connects. Yes, you earned your place in the list of Fidonet IPv6 capable nodes.

    But... full IPv6 capability? Eh.. no I would not say so. The world of IPv6 is bigger than just connecting one Fidonet node via IPv6. Full IPv6 connectivity implies having IPv6 for your entire local network. Correct me if I am wrong, but I do not think you have that.

    When I got my SixXs account, what was it, seven, eight? years ago, my plan was to use my Fido XP machine that is on 24/7 anyway as the tunnel endpoint and router for the IPv6 subnet that I could get from SixXs. Well, I got the tunnel part working quicky enough, but routing the subnet to my other devices on the LAN, that I never got to work. After some not so nice interchanges with the SixXs' Head Honcho, I learned that routing a tunneled IPv6 subnet just doesn't work with windows XP as a router.

    So I abandonned that idea and went for installing a he.net tunnel on a Linksys WRT54GL flashed with OpenWrt. And with THAT ssetup, I managed to route a /64 subnet to my LAN.
    In the meantime, I have moved on. I now have native IPv6 from my ISP and a modem/router that routes a subnet to my LAN. I have not cancelled my tunnel aacounts, but the tunnels are sleeping.

    Once again, correct me if I am wrong, but I think you are still stuck where I was seven years ago with a tunnel that could just provide IPv6 for ONE machine on my LAN.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Joacim Melin@2:203/242 to Markus Reschke on Mon Feb 13 12:33:41 2017
    Hi Bjrn!

    Feb 10 16:30 2017, Bjrn Felten wrote to Michiel van der Vlist:

    The XP machine *is* my router. That's why I'm so reluctant to abandon
    it.

    Ouch! Please do yourself a favour and get a cheap router supported by OpenWrt or go for pf/opnSense.

    I'll second that. pfSense is awesome and you can do pretty much whatever the hell you want with it. Very flexible and powerful and runs fine even a older Atom-based PC with ~2GB RAM.


    --- NiKom v2.2.0
    * Origin: Delta City BBS (deltacity.se, +46-8-6058800) (2:203/242.0)
  • From Tommi Koivula@2:221/360.8110 to Björn Felten on Mon Feb 13 15:15:46 2017

    Hello Bjrn!

    12 Feb 17 21:15, you wrote to me:

    No, it's the old firewall from the NT system I inherited from
    Gteborg city (the first owner of this computer). It's nothing like
    the XP ditto.

    It is not very wise to connect XP directly to the Big Bad
    Internet.

    That depends entirely on the system operator. If you don't know
    your way around it's not wise to connect directly to the Big Bad
    Internet, period.

    Oh boy. <sigh>

    'Tommi

    ---
    * Origin: A point of news://rbb.bbs.fi (2:221/360.8110)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Mon Feb 13 16:12:00 2017
    Hello Bjrn,

    On Sunday February 12 2017 15:42, you wrote to me:

    Thanks!

    You'r welcome. ;-)

    Now, considering that a vast amount of FTN systems still probably
    runs on an XP setup(?), can we perhaps help those willing to try a
    tunnel through all the hoops they'll encounter?

    "Vast amount"? Now that we have come down from 30000+ nodes and half a million points to an estimated 1000+ nodes and maybe even less points?

    OK, that still leaves an estimated couple of hundred XP systems running FTN software. Only those running IPv6 capable mailers will be interested. And of those some already have IPv6. And then there are the IPv6 denyers. They believe it is all just a scheme from the providers to let us pay more for our internet connection and if we just refuse to go along, it will blow over...

    But... I think the killer filter is that very few that run an XP system have it directly connected to the InterNet. The normal setup is to have it behind a router. You may be the only Fidonet sysop haveing an XP system directly connected to the internet, using it as a router and host your tunnel end point.

    I know that you are probably one of the most knowledgeable netsh experts amongst us;

    Me? That's too much honour.

    what if we analyse all the netsh commands needed
    to get an XP system from scratch and create a generic one that lacks
    the mistakes SixXS as well as he.net has made?

    What mistakes? I did not have much trouble installing my SixXs tunnel on my XP system. In fact, I seem to have taken the same steps as you. Look here:

    D:\FIDO\R28>netsh int ipv6 show routes
    Der aktive Status wird abgefragt...

    Verff. Typ Met Prfix Idx Gateway/Schnittstelle ------- -------- ---- ------------------------ --- --------------------- no Autokonf 256 2001:1c02:1100:fd00::/56 4 fe80::7277:81ff:fe72:a4bb
    no Autokonf 8 2001:1c02:1100:fd00::/64 4 LAN-Verbindung
    no Autokonf 256 ::/0 4 fe80::7277:81ff:fe72:a4bb
    no Manuell 0 2001:7b8:2ff:3a9::/64 5 aiccu
    yes Manuell 0 ::/0 5 2001:7b8:2ff:3a9::1

    The last two are relics from my SixXs (AYIYA) tunnel.

    What I could never get to work was routing a sunbnet that way. Tha was the main reason I abondonned that plan and installed a he.net tunnel on WRT54GL running OpenWrt. The instructions on the he.net website were quite clear. But OpenWrt is Linux, not XP..

    As a basis I would use this:

    netsh int ipv6 install

    That's obvious.

    Obvious.

    netsh int ipv6 6to4 set state disabled
    netsh int ipv6 set teredo disable
    netsh int ipv6 isatap set state state=disabled

    I would really want a total delete function here, if nothing else
    but to clean up the ipconfig /all response.

    I would like that too, at least I would like to make those three totally invisible. But I have not yet found a way to do that. I am not the netsh guru you seem to think I am...

    netsh int ipv6 add address "he.net" 2001:470:27:302::2
    netsh int ipv6 add route 2001:470:27:302::2/64 he.net
    netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes

    Probably what I did to install my SixXs tunnel. Almost a decade ago...

    And here is probably where we need to put a lot of comments. For starters, there's no IPv4 addresses here, so I guess it's working for
    me because I added it somewhere else along the line.

    Must be... I don't recall how I did it. Too long ago...

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Tommi Koivula on Sat Feb 18 13:54:40 2017
    Oh boy. <sigh>

    Oh boy OK. Have you figured out what's happened to your IPv6 system lately?

    ? 18 Feb 13:37:20 [3760] connection to 2:221/1@fidonet failed: {W32 API error 10065} A socket operation was attempted to an unreachable host
    18 Feb 13:37:20 [3760] trying rbb.ath.cx [88.112.105.222]:24554...
    18 Feb 13:37:21 [3760] connected
    + 18 Feb 13:37:21 [3760] outgoing session with rbb.ath.cx:24554 [88.112.105.222]

    Maybe you should consider using my XP setup? 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 Tommi Koivula@2:221/1.1 to Bj÷rn Felten on Sun Feb 19 08:19:14 2017

    18 Feb 17 13:54:40, you wrote to me:

    Have you figured out what's happened to your IPv6 system
    lately?

    Been out since last sunday.

    It seems that my ubuntu box had lost the additional addresses

    2001:470:1f15:cb0:f1d0:2:221:1
    2001:470:1f15:cb0:f1d0:2:221:0
    2001:470:1f15:cb0:f1d0:2:221:360

    where the xinetd is forwarding port 24554 to OS/2.

    I dont know why it happened, but it is up now.

    ? 18 Feb 13:37:20 [3760] connection to 2:221/1@fidonet failed: {W32
    API
    error 10065} A socket operation was attempted to an unreachable host
    18 Feb 13:37:20 [3760] trying rbb.ath.cx [88.112.105.222]:24554...
    18 Feb 13:37:21 [3760] connected
    + 18 Feb 13:37:21 [3760] outgoing session with rbb.ath.cx:24554 [88.112.105.222]

    You can also use the other he.net tunnel at 2:221/0. It is terminated in Sweden.

    Maybe you should consider using my XP setup? 8-)

    Maybe I don't.

    'Tommi

    ... he.net certified sage
    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)