[..]-64 Binkd ignores the OS preference and tries to first make an
IPv6 connect. If that fails, it tries an IPv4 connect.
That could be useful in some scenarios. In my case, my IPv6
connectivity (native) is better than IPv4 (tunneled), so it's better
for me to try IPv6 first in most cases, then fall back to IPv4 if necessary.
*** Answering a msg posted in area BINKD (Binkd mailer).
Hello Tony,
On Wednesday February 01 2017 09:34, you wrote to me:
[..]-64 Binkd ignores the OS preference and tries to first make an
IPv6 connect. If that fails, it tries an IPv4 connect.
That could be useful in some scenarios. In my case, my IPv6 connectivity (native) is better than IPv4 (tunneled), so it's better
for me to try IPv6 first in most cases, then fall back to IPv4 if necessary.
Native IPv6 and IPv4 via a tunnel is the opposite of what many of us
have. Quite exceptional. For now. It may not be so exceptional in the
future.
But is IPv6 not the default on your system? Is is different from my
situation (Windows, native dual stack) where IPv6 is the default
connectiom method, except when the destination has a 6to4 IPv6 address? (2002::/16)
I wonder if "default connection method" might be "default resolving method" on some OSes, if given a hostname. There is a difference in
which protocol OSes will try first if given both v4 and v6, so having
a button to make binkd make a specific choice might be a good idea.
Feb 01 16:44 2017, Janne Johansson wrote to Michiel van der Vlist:
I wonder if "default connection method" might be "default
resolving method" on some OSes, if given a hostname. There is a
difference in which protocol OSes will try first if given both v4
and v6, so having a button to make binkd make a specific choice
might be a good idea.
On linux you can configure how IPv4 and IPv6 are prioritized via /etc/gai.conf. To prefer 6to4 tunnels over IPv4 comment out the line starting with "label 2002::/16" and restart binkd. Yes, it's that
simple ;)
In my ubuntu vps box all the lines in /etc/gai.conf are commented out. Like this:
#label ::1/128 0
#label ::/0 1
#label 2002::/16 2
#label ::/96 3
#label ::ffff:0:0/96 4
#label fec0::/10 5
#label fc00::/7 6
#label 2001:0::/32 7
#label 2002::/16 2
label ::/96 3
label ::ffff:0:0/96 4
label fec0::/10 5
label fc00::/7 6
label 2001:0::/32 7
Confirmed:
+ 18:29 [4917] call to 2:5023/24@fidonet
18:29 [4917] trying f24.n5023.z2.binkp.net [2002:3e94:91ed::2]...
18:29 [4917] connected
#label 2002::/16 2
label ::/96 3
label ::ffff:0:0/96 4
label fec0::/10 5
label fc00::/7 6
label 2001:0::/32 7
Confirmed:
+ 18:29 [4917] call to 2:5023/24@fidonet
18:29 [4917] trying f24.n5023.z2.binkp.net [2002:3e94:91ed::2]...
18:29 [4917] connected
OK, so that way one can make an IPv6 connect to a 6to4 tunneled node. But that does not nullify my feature request for -64 and -46 options. What you did is changing the OS preference. So that will affect /all/ connections. Not just binkp. What I proposed was an override on the OS preference for a specific connection. I.e a binkp connect to a specific node.
OK, so that way one can make an IPv6 connect to a 6to4 tunneled
node. But that does not nullify my feature request for -64 and
-46 options. What you did is changing the OS preference. So that
will affect /all/ connections. Not just binkp. What I proposed
was an override on the OS preference for a specific connection.
I.e a binkp connect to a specific node.
Of course. But this is ipv6 echo, not binkd echo. :)
OK, so that way one can make an IPv6 connect to a 6to4 tunneled
node. But that does not nullify my feature request for -64 and
-46 options. What you did is changing the OS preference. So that
will affect /all/ connections. Not just binkp. What I proposed
was an override on the OS preference for a specific connection.
I.e a binkp connect to a specific node.
Of course. But this is ipv6 echo, not binkd echo. :)
Indeed. Is there an equivalent setting for Windows?
You can start with^^^
netsh interface ipv6 show prefixpolicies
and continue with
netsh interface ipv6 set prefixpolicy
and then you may do some googling. ;)
MvdV> ^^^netsh interface ipv6 show prefixpolicies
netsh interface ipv6 show prefixpoliciesQuerying active state...
MvdV>> ^^^netsh interface ipv6 show prefixpolicies
D:\FIDO\FMAIL>> netsh int ipv6 show prefixpolicyMvdV>> Der aktive Status wird abgefragt...
So you still have win XP.
I have number seven:
netsh interface ipv6 show prefixpoliciesQuerying active state...
Precedence Label Prefix
---------- ----- --------------------------------
50 0 ::1/128
40 1 ::/0
30 2 2002::/16
20 3 ::/96
10 4 ::ffff:0:0/96
5 5 2001::/32
I cannot understand why these netsh commands had to be changed between
win versions.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495942:22:58 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 287,020 |