It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877
bbs.ncc.org.ua AAAA record updated.
It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877
bbs.ncc.org.ua AAAA record updated.
It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877
bbs.ncc.org.ua AAAA record updated.
Another ipv6-capable Radius. Nice. :)
It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877Another ipv6-capable Radius. Nice. :)
bbs.ncc.org.ua AAAA record updated.
MvdV> He is Incoming only, so I suspect he is using a 6 to 4 proxy.It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877
bbs.ncc.org.ua AAAA record updated.
Another ipv6-capable Radius. Nice. :)
x) Friday Jan 19, 2018, 21:01. Tommi Koivula ── Alex Shuman.
It is reachable now via 2a01:d0:5:4050:f1d0:2:463:877
bbs.ncc.org.ua AAAA record updated.
Another ipv6-capable Radius. Nice. :)
Indeed. It uses port forwarding via "netsh int portproxy" though...
Listen on ipv6: Connect to ipv4:
Address Port Address Port
--------------- ---------- --------------- ----------
* 24554 10.10.5.2 24554
* 60179 10.10.5.2 60179
* 60177 10.10.5.2 60177
Using Win7 internal portproxy on same machine because Radius does not have native IPv6 capability.
And outbound ipv6 from Radius is possible with ipv6 capable proxy, like privoxy or squid. :)
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
Using Win7 internal portproxy on same machine because Radius does notAnd outbound ipv6 from Radius is possible with ipv6 capable proxy, like privoxy or squid. :)
have native IPv6 capability.
And outbound ipv6 from Radius is possible with ipv6 capable proxy,
like privoxy or squid. :)
How? Like portproxy, by adding each node manually with a port to forward?
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked
only with actual ipv4 address, assigned to network card interface.
x) Saturday Jan 20, 2018, 09:00. Tommi Koivula -- Alex Shuman.
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked only with actual ipv4 address, assigned to network card interface.
Oh? Well, please don't tell that to my Win2003server, because that one really works here. :)2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked
only with actual ipv4 address, assigned to network card interface.
Using Win7 internal portproxy on same machine because Radius does not
have native IPv6 capability.
relay6 80 127.0.0.1 80 /b::: /c:32
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked
only with actual ipv4 address, assigned to network card interface.
Michiel van der Vlist wrote to Alex Shuman <=-
From the log it seems some IPv6 is coming in, but it would be nice of someone would see if they can reach www.vlist.eu via IPv6
Well, remembering my XP days, IPv6 stuff was in alpha/beta state
there. And network stack was pretty buggy. Got "No buffer space
available" after couple of days uptime and forced to reboot too.
Win7 will definitely work better with this.
It works.
I see you have native IPv6, too:
ipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]
but your ISP does not seem to assign proper reverse DNS for customers.
From the log it seems some IPv6 is coming in, but it would be
nice of someone would see if they can reach www.vlist.eu via
IPv6
Yep, comes up on IPv6 here. I saw the "You are connected via IPv6"
banner here.
Michiel van der Vlist wrote to Tony Langdon <=-
Ouch... That thingy is a bit misleading. It just means that you are connecting to http://v4v6.ipv6-test.com/imgtest.php via IPv6. So YOU
have IPv6. It does not mean that you actually connect to my web server via IPv6.
I am now experimenting with relay6 to provide IPv6 access to my web server.
This is what I have presently runnig:
relay6 80 127.0.0.1 80 /b::: /c:32
From the log it seems some IPv6 is coming in, but it would be nice of someone would see if they can reach www.vlist.eu via IPv6
Cheers, Michiel
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked
only with actual ipv4 address, assigned to network card interface.
The XP version accepts both 127.0.0.1 and "localhost". It also accepts symbolic names for the port. Like "http" and "ftp".
But... after a reboot it stops after some time. :(
Ouch... That thingy is a bit misleading. It just means that you
are connecting to http://v4v6.ipv6-test.com/imgtest.php via
IPv6. So YOU have IPv6. It does not mean that you actually
connect to my web server via IPv6.
I see, well, without my add-ons working, it's hard to be certain.
Michiel van der Vlist wrote to Tony Langdon <=-
Indeed. That's why I want that add-on to work...
But... after a reboot it stops after some time. :(
Maybe it is the "microsoft feature" of not-a-server-os.
Have you tried to delete and add the portproxy setting every hour?
netsh int portproxy delete v6tov4 listenport=24554 ..
netsh int portproxy add v6tov4 listenport=24554 ..
MvdV> Perhaps it is time to say goodbye to XP?Win7 will definitely work better with this.
MvdV> Indeed, that is a bit of a joke. Every IPv6 addres (2001:1c02::/32)ipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]
but your ISP does not seem to assign proper reverse DNS for
customers.
Ouch... That thingy is a bit misleading. It just means that you areI see, well, without my add-ons working, it's hard to be certain.
connecting to http://v4v6.ipv6-test.com/imgtest.php via IPv6. So YOU
have IPv6. It does not mean that you actually connect to my web
server via IPv6.
You can check it with netstat -an for example, if there's a connection from your ipv6 ip to his at port 80, it works.
No, it's the default "prefer IPv4 over IPv6" in your system or browser settings.
For Firefox based browsers, check the following about:config settings:
network.dns.disableIPv6 = false
network.http.fast-fallback-to-IPv4 = false (Pale Moon with works for
me with true though)
In case of WinXP, it's forced default behavior of "prefer IPv4" and
there is a way to fix it by modifying netsh prefixpolicy as shown
here: https://sites.google.com/site/jrey42/Home/ipv6/prefixpolicies
netshnetsh>prefixpolicy
MvdV>> Indeed, that is a bit of a joke. Every IPv6 addresipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]
but your ISP does not seem to assign proper reverse DNS for
customers.
Is it dynamic or static?
And if it's static, why your ISP can't provide a proper backresolve
by customer request?
MvdV> Odd. Because this only happens when I use the RELAY6 method when locallyNo, it's the default "prefer IPv4 over IPv6" in your system or browser
settings.
MvdV>>> Indeed, that is a bit of a joke. Every IPv6 addresipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]
but your ISP does not seem to assign proper reverse DNS for
customers.
MvdV> Dynamic.Is it dynamic or static?
So it is set automatically by ISP and changes every time you reconnect? Then how did you set it to f1d0-style?
MvdV>>>> Indeed, that is a bit of a joke. Every IPv6 addresipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]
but your ISP does not seem to assign proper reverse DNS for
customers.
MvdV>> Dynamic.Is it dynamic or static?
So it is set automatically by ISP and changes every time you
reconnect? Then how did you set it to f1d0-style?
MvdV> No, they call it dynamic, because they do not guarantee that the /56So it is set automatically by ISP and changes every time you
reconnect? Then how did you set it to f1d0-style?
Indeed. Win7 is the best choice for now.
Indeed. Win7 is the best choice for now.This very, very much depends on the side conditions of your evaluation.
I would very much refute your statement ;)
I would prefer most Linux flavors to Windows 7.
Some people would even prefer Mac OS X ;)
 MvdV>> Perhaps it is time to say goodbye to XP?and BSD to MacOSX...
 AS> Indeed. Win7 is the best choice for now.
This very, very much depends on the side conditions of your evaluation.
I would very much refute your statement ;)
I would prefer most Linux flavors to Windows 7.
Some people would even prefer Mac OS X ;)
MvdV>> Odd. Because this only happens when I use the RELAY6 methodNo, it's the default "prefer IPv4 over IPv6" in your system or
browser settings.
Then it's something with RELAY6 altering IPv6 default route priority.
MvdV>>> Odd. Because this only happens when I use the RELAY6 methodNo, it's the default "prefer IPv4 over IPv6" in your system or
browser settings.
MvdV>>> Hmmm...Then it's something with RELAY6 altering IPv6 default route priority.
I am now experimenting with relay6 to provide IPv6 access to my webserver.
This is what I have presently runnig:
relay6 80 127.0.0.1 80 /b::: /c:32
From the log it seems some IPv6 is coming in, but it would be nice of someone would see if they can reach www.vlist.eu via IPv6
Cheers, Michiel
2001:470:1f15:cb0:f1d0:2:221:6 119 127.0.0.1 119
BTW, I have tried portproxy to 127.0.0.1 and it does not work. Worked
only with actual ipv4 address, assigned to network card interface.
The XP version accepts both 127.0.0.1 and "localhost". It also accepts symbolic names for the port. Like "http" and "ftp".
But... after a reboot it stops after some time. :(
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 513 |
Nodes: | 10 (1 / 9) |
Uptime: | 00:18:22 |
Calls: | 8,291 |
Calls today: | 4 |
Files: | 15,520 |
Messages: | 928,848 |