Re: little bit off topic CLAT-Daemon for 464xlat for "Linux" (not android)
- From: Thomas Schäfer <tschaefer t-online de>
- To: Tore Anderson <tore fud no>
- Cc: networkmanager-list gnome org
- Subject: Re: little bit off topic CLAT-Daemon for 464xlat for "Linux" (not android)
- Date: Sun, 23 Feb 2014 13:46:42 +0100
Tanks a lot again!
Printing and framing emails is not enough. Today I found the time to read your
answer carefully. Yes, it works for me too! Special thanks for the hint with
the nd-proxy.
echo 1 > /proc/sys/net/ipv6/conf/eth0/proxy_ndp
ip -6 neigh add proxy 2001:6f8:120c::c1a7 dev eth0
My configuration was unfortunately no real UMTS/LTE-connection. Instead of
this I used ethernet without IPv4.
tun-device clat
ipv4-addr 192.168.255.1
prefix 2001:67c:2b0:db32:0:1::/96
map 192.0.0.4 2001:6f8:120c:0::c1a7
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 3c:d9:2b:1a:c9:9a brd ff:ff:ff:ff:ff:ff
inet6 fd00::3ed9:2bff:fe1a:c99a/64 scope global dynamic
valid_lft 6844sec preferred_lft 3244sec
inet6 2001:6f8:120c:0:3ed9:2bff:fe1a:c99a/64 scope global dynamic
valid_lft 6844sec preferred_lft 3244sec
inet6 fe80::3ed9:2bff:fe1a:c99a/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d0:df:9a:93:67:90 brd ff:ff:ff:ff:ff:ff
5: clat: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 500
link/none
inet 192.0.0.4/32 scope global clat
valid_lft forever preferred_lft forever
Back to the original intention. Is it useful to integrate this in the
NetworkManager on "normal" Linux-Desktops?
After the native IPv6-only-connection is established the NetworkManager or a
other tool has to check if DNS is DNS64/NAT64, if so it has to guess/read the
/96-NAT64-prefix and to configure the clat/tayga-Interface.
Regards,
Thomas
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]