Your system switched to IPv6 after a IPv4 connect failed. Apparently
IPv4 connects have priority over IPv6. The norm is the otherway aroud.
Anyone feel like making a recap? I'm using netsh on an old WinXP.
What do you need to see/know about my system.
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.
A redundant connection was offered and a switch was made when one connection did not work.
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
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?
Negatory.
The XP machine *is* my router.
That's why I'm so reluctant to abandon it.
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. :(
The XP machine *is* my router. That's why I'm so reluctant to abandon
it.
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. :(
The XP machine *is* my router.
That's why I'm so reluctant to abandon it.
Node 2:230/5555 -6 - password
Node 2:230/5555 -6 - password
That's me! Albeit not Michiel... 8-)
But that did he trick it seems. Thanks!
Ouch! That's not good. Back to the old config.
LOL! I give up.
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
MvdV> Before you do, tell us what "ipconfig /all" shows.
Well, this is after (before shows that 6to4 with the IPv6 address you found):
I cannot connect by ipv6. Did you reboot?
I cannot connect by ipv6. Did you reboot?
I cannot connect by ipv6. Did you reboot?
Looks like it's working now, no?
No luck so far. I probably have to sleep on it... 9-)
I cannot connect by ipv6. Did you reboot?
No, I messed around. :(
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...
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.
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
He need to get rid of teredo and 6to4 and all that shit. And reboot.
:)
Bjrn Felten wrote to Michiel van der Vlist <=-
The XP machine *is* my router. That's why I'm so reluctant to
abandon it.
He need to get rid of teredo and 6to4 and all that shit. And reboot. :)
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?
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...?
Have I earned my brownie now...? 8-)
Only the points, not the whole girl. ;)
Have I earned my brownie now...? 8-)
And no, no need really to hatch a new file for the Snooze for that particular reason...
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?
I know you are. But where's the challenge in that? 8-)
My present XP based setup is almost 20 years old,
My present XP based setup is almost 20 years old,
Not quite...
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.
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?
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.
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.
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.
Oh boy. <sigh>
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-)
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 127:47:40 |
Calls: | 8,198 |
Files: | 15,443 |
Messages: | 913,674 |