Hi Marc, *,
On Tue, Oct 2, 2012 at 9:41 PM, Marc Paré<marc@marcpare.com> wrote:
Le 2012-10-01 06:43, Florian Effenberger a écrit :
[some TDF hosted services (test installations) might only be accessible using ipv6 in future]
I just checked with my ISP and there is no support for IPV6, I was told that
they have spoken about it, but there is not enough demand for it yet.
Native ipv6 by ISP is indeed not very common, although this has begun
already, and you should indeed ask your ISP for ipv6 addresses, to
show that there /is/ demand.
That being said: native ipv6 connectivity is not needed.
Not sure about the SixXS and 6to4 tunnelling you mention.
I personally don't like SixxS, I have my tunnel from hurricane
electric AKA tunnelbroker.net - their terms are much more sane.
tunneling works similar to a proxy. I.e. it is using an additional
server between you and the desired endpoint. Your computer and the
additional server are communicating using ipv4, wile the additional
server and the desired endpoint are using ipv6
Their are different ways to use it, not 100% the same, but
functionality wise equivalent. One of that is the explicit tunnel. You
set it up on your computer, and need to register at one of the
tunnel-providers (SixxS and Hurricane Electric being two of them) to
have a IPv6 address-space allocated for you.
Pro: You have static IPv6 address. You know your ipv6 address and can
use that to build a small network yourself, you can use that same ipv6
address even when connecting from a completely different network (e.g.
when travelling)
Contra: You need to register, and to set it up, you need to run a few
commands in a terminal. But its not rocket science. Some buggy
router's firewall might make problems though.
For example on linux:
modprobe ipv6
ip tunnel add he-ipv6 mode sit remote<ipv4-of-tunnelserver> local
<your ipv4 IP> ttl 255
ip link set he-ipv6 up
ip addr add<your-ipv6-address> dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr
Example for windows (vista/7/2008):
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel<your ipv4> <ipv4 of tunnel>
netsh interface ipv6 add address IP6Tunnel<your ipv6>
netsh interface ipv6 add route ::/0 IP6Tunnel<your ipv6 routing-address>
(the routing address is usually just using 1 as the last part instead
of whatever else you're using for your endpoint)
When you're using dynamic IP, you also have to update your endpoint
each time it changes/when you want to use ipv6. Either by visiting a
URL, or by running a small program that watches the connection.
If you look at the Windows commands, there is also another method
indicated, namely teredo. It is basically an automated way to setup a
tunnel.
teredo protocol looks for tunnels
Pros: works behind any router (well, more, but still not all)
Cons: encapsulates the requests in UDP, has more overhead, requires
properly setup relays, otherwise performance is bad, only one address
possible, not possible to connect a network. ipv6 address always
depends on ipv4 address.
teredo works by first contacting a Teredo server (basically a index of
known relays), then traffic is sent to the relay using udp& ipv4, the
relay turns udp back into tcp and ipv6 and talks to the endpoint. Way
back is similar, except that the client must open a port first, for
that the relay sends a request to the teredo server to notify/ping the
client and then sends the data to the client.
It may be good to
have links pointing to some solutions for those of us who are still stuck in
the dark ages of IPV4. :-)
Check whether you can already use ipv6 - go visit
http://ds.testmyipv6.com/ - that page is reachable with both ipv6 as
well as ipv4 -so it should load no matter what. Either you get a green
box, or a red box. Green is used when your computer can use ipv6 and
actually prefers it over ipv4.
If the page is read, try the ipv6-only page:
http://v6.testmyipv6.com/
If that then loads, you can use ipv6, but your computer is only using
it as fallback. If that page doesn't load at all, then you need to do
something to change it:
Get a tunnelbroker of your choice :-)
http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers
(your choice should be based primarily on location, as all ipv6
traffic will be routed over the broker's server. So sending traffic
across from Europe to China and back just for the tunnel is not a good
idea :-))
While teredo is also available for linux
(http://www.remlab.net/miredo/), I'd prefer a direct tunnel.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.