|
world wide IPv6 not reachable from LAN clients
![[de]](/s/countries/de.gif) Shadow Hawkins on Friday, 17 June 2011 10:18:08
Hi there,
I set up aiccu and radvd on my Ubuntu 11.04 64 bit Server.
Tunnel is running fine on the machine itself (aiccu test succeeds completly), radvd is propagating adresses to other machines in the LAN and I can ping the Server Interface on IPv6 but no adress behind the tunnel (not even its endpoint). I guess something is wrong with the routing of the server?
Here are some outputs:
me@server:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 40:61:86:5e:1b:8b
inet addr:192.168.5.1 Bcast:192.168.7.255 Mask:255.255.248.0
inet6 addr: fe80::4261:86ff:fe5e:1b8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:289693 errors:0 dropped:0 overruns:0 frame:0
TX packets:264574 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:111882887 (111.8 MB) TX bytes:53146257 (53.1 MB)
Interrupt:41 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1118 errors:0 dropped:0 overruns:0 frame:0
TX packets:1118 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83195 (83.1 KB) TX bytes:83195 (83.1 KB)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: fe80::c0a8:501/64 Scope:Link
inet6 addr: 2001:4dd0:ff00:30e::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:1014 errors:0 dropped:0 overruns:0 frame:0
TX packets:1255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:130212 (130.2 KB) TX bytes:138560 (138.5 KB)
me@server:~$ route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
2001:4dd0:ff00:30e::/64 :: Un 256 0 1 sixxs
2000::/3 :: U 1024 0 0 sixxs
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: Un 256 0 0 sixxs
::/0 2001:4dd0:ff00:30e::1 UG 1024 0 0 sixxs
::/0 :: !n -1 1 4577 lo
::1/128 :: Un 0 1 99 lo
2001:4dd0:ff00:30e::/128 :: Un 0 1 0 lo
2001:4dd0:ff00:30e::2/128 :: Un 0 1 32 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::c0a8:501/128 :: Un 0 1 196 lo
fe80::4261:86ff:fe5e:1b8b/128 :: Un 0 1 141 lo
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 sixxs
::/0 :: !n -1 1 4577 lo
radvd.conf
interface eth0 {
AdvSendAdvert on;
prefix 2001:4dd0:fead::/64
{
};
};
Thanks for any help, Levino
world wide IPv6 not reachable from LAN clients
Did you enable forwarding?
Is radvd actually running?
What do the logs (/var/log/*) say?
What is the configuration of the client, eg what are it's routing tables?
Where is a traceroute showing what it is trying to do?
etc etc...
aka please provide more details :)
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 15:59:25
Thanks for the answer, here we go:
radvd is running. As for /var/log/*: Sorry I am no pro in linux. What logs and what kind of messages are important? Syslogd? search for 'radvd'?
Client running windows 7 has the following settings:
PS C:\Users\Levin> ipconfig
Windows-IP-Konfiguration
Ethernet-Adapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix: e19
IPv6-Adresse. . . . . . . . . . . : 2001:4dd0:fead:0:8c29:5d89:1fd:7d1
Temporre IPv6-Adresse. . . . . . : 2001:4dd0:fead:0:5032:c057:de3d:caf0
Verbindungslokale IPv6-Adresse . : fe80::8c29:5d89:1fd:7d1%26
IPv4-Adresse . . . . . . . . . . : 192.168.3.2
Subnetzmaske . . . . . . . . . . : 255.255.248.0
Standardgateway . . . . . . . . . : fe80::4261:86ff:fe5e:1b8b%26
192.168.0.1
Ethernet-Adapter LAN-Verbindung* 19:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Tunneladapter isatap.e19:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix: e19
Tunneladapter LAN-Verbindung*:
Verbindungsspezifisches DNS-Suffix:
IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fb:2cad:287a:3f57:fcfd
Verbindungslokale IPv6-Adresse . : fe80::2cad:287a:3f57:fcfd%12
Standardgateway . . . . . . . . . :
Tunneladapter isatap.{4D16012F-9924-4192-8E56-20874E153A82}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
netsh int ipv6 show route
Verff. Typ Met Prfix Idx Gateway/Schnittstelle
------- -------- ---- ------------------------ --- ---------------------
Nein Manuell 256 ::/0 26 fe80::4261:86ff:fe5e:1b8b
Nein Manuell 256 ::1/128 1 Loopback Pseudo-Interface 1
Nein Manuell 8 2001::/32 12 LAN-Verbindung*
Nein Manuell 256 2001:0:5ef5:79fb:2cad:287a:3f57:fcfd/128 12 LAN-Verbindung*
Nein Manuell 8 2001:4dd0:fead::/64 26 LAN-Verbindung
Nein Manuell 256 2001:4dd0:fead:0:5032:c057:de3d:caf0/128 26 LAN-Verbindung
Nein Manuell 256 2001:4dd0:fead:0:8c29:5d89:1fd:7d1/128 26 LAN-Verbindung
Nein Manuell 256 fe80::/64 26 LAN-Verbindung
Nein Manuell 256 fe80::/64 20 LAN-Verbindung* 19
Nein Manuell 256 fe80::/64 12 LAN-Verbindung*
Nein Manuell 256 fe80::5efe:192.168.3.2/128 11 isatap.e19
Nein Manuell 256 fe80::2cad:287a:3f57:fcfd/128 12 LAN-Verbindung*
Nein Manuell 256 fe80::649f:6621:b09b:9506/128 20 LAN-Verbindung* 19
Nein Manuell 256 fe80::8c29:5d89:1fd:7d1/128 26 LAN-Verbindung
Nein Manuell 256 ff00::/8 1 Loopback Pseudo-Interface 1
Nein Manuell 256 ff00::/8 12 LAN-Verbindung*
Nein Manuell 256 ff00::/8 26 LAN-Verbindung
Nein Manuell 256 ff00::/8 20 LAN-Verbindung* 19
tracert -6 www.sixxs.net
Routenverfolgung zu nginx.sixxs.net [2001:838:2:1:2a0:24ff:feab:3b53] ber maximal 30 Abschnitte:
1 * * * Zeitberschreitung der Anforderung.
2 * * * Zeitberschreitung der Anforderung.
(complete fail).
Happy to give further details.
BTW: Added IPv6 Adress of my subnet (at least that is so) for eht0:
ifconfig
eth0 Link encap:Ethernet HWaddr 40:61:86:5e:1b:8b
inet addr:192.168.5.1 Bcast:192.168.7.255 Mask:255.255.248.0
inet6 addr: fe80::4261:86ff:fe5e:1b8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25669717 errors:0 dropped:0 overruns:0 frame:0
TX packets:28081558 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29509445585 (29.5 GB) TX bytes:34612522209 (34.6 GB)
Interrupt:41 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7905 errors:0 dropped:0 overruns:0 frame:0
TX packets:7905 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:713866 (713.8 KB) TX bytes:713866 (713.8 KB)
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::4cd0:ff00:30e:2/64 Scope:Link
inet6 addr: 2001:4dd0:ff00:30e::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:19541 errors:0 dropped:0 overruns:0 frame:0
TX packets:20401 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1346887 (1.3 MB) TX bytes:1391910 (1.3 MB)
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 16:12:07
Oops. Thought I did. Maybe I removed it. Now its there (everything else still the same):
ifconfig
eth0 Link encap:Ethernet HWaddr 40:61:86:5e:1b:8b
inet addr:192.168.5.1 Bcast:192.168.7.255 Mask:255.255.248.0
inet6 addr: fe80::4261:86ff:fe5e:1b8b/64 Scope:Link
inet6 addr: 2001:4dd0:ff01:30e::1/128 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25674238 errors:0 dropped:0 overruns:0 frame:0
TX packets:28086828 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29510381095 (29.5 GB) TX bytes:34618084104 (34.6 GB)
Interrupt:41 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7921 errors:0 dropped:0 overruns:0 frame:0
TX packets:7921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:714826 (714.8 KB) TX bytes:714826 (714.8 KB)
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::4cd0:ff00:30e:2/64 Scope:Link
inet6 addr: 2001:4dd0:ff00:30e::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:19636 errors:0 dropped:0 overruns:0 frame:0
TX packets:20555 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1356515 (1.3 MB) TX bytes:1408394 (1.4 MB)
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 16:58:14
Found something in syslog
Jun 23 16:13:56 eifel radvd[13670]: version 1.7 started
Jun 23 16:14:48 eifel kernel: [409227.477117] icmpv6_send: no reply to icmp error
Jun 23 16:17:01 eifel CRON[13677]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 23 16:23:29 eifel kernel: [409748.508130] icmpv6_send: no reply to icmp error
Jun 23 16:23:33 eifel kernel: [409752.105362] icmpv6_send: no reply to icmp error
Jun 23 16:23:37 eifel kernel: [409756.252367] icmpv6_send: no reply to icmp error
Jun 23 16:23:59 eifel kernel: [409778.224752] icmpv6_send: no reply to icmp error
Jun 23 16:37:18 eifel kernel: [410577.009835] icmpv6_send: no reply to icmp error
Jun 23 16:37:18 eifel kernel: [410577.013778] icmpv6_send: no reply to icmp error
Jun 23 16:37:18 eifel kernel: [410577.026599] icmpv6_send: no reply to icmp error
world wide IPv6 not reachable from LAN clients
ifconfig
You might be interested in the 'ip' tool:
ip link show
ip -6 addr show (or ip -6 addr sho)
ip -6 route show (or ip -6 ro sho)
eth0 Link encap:Ethernet HWaddr 40:61:86:5e:1b:8b > inet addr:192.168.5.1 Bcast:192.168.7.255 Mask:255.255.248.0
> inet6 addr: fe80::4261:86ff:fe5e:1b8b/64 Scope:Link
> inet6 addr: 2001:4dd0:ff01:30e::1/128 Scope:Global
You added the PoP-side of the tunnel to eth0, you need to add an address out of your /64 here, that is a /64 out of the /48 aka the same /64 you use in RADVD...
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 17:10:11
I thought changing 0 to 1 at the correct position would do the trick:
PoP: 2001:4dd0:ff00:30e::1
eth0: 2001:4dd0:ff01:30e::1
Please check above, but if it's really a bad choice could you please provide a better one?
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 40:61:86:5e:1b:8b brd ff:ff:ff:ff:ff:ff
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
5: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:4dd0:ff01:30e::1/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4261:86ff:fe5e:1b8b/64 scope link
valid_lft forever preferred_lft forever
5: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
inet6 2001:4dd0:ff00:30e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4cd0:ff00:30e:2/64 scope link
valid_lft forever preferred_lft forever
ip -6 route show
2001:4dd0:ff00:30e::/64 dev sixxs proto kernel metric 256
2001:4dd0:ff01:30e::1 dev eth0 proto kernel metric 256
fe80::/64 dev sixxs proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
default via 2001:4dd0:ff00:30e::1 dev sixxs metric 1024
No "ip" available in Win7. Does the tool also exist there?
world wide IPv6 not reachable from LAN clients
I thought changing 0 to 1 at the correct position would do the trick:
PoP: 2001:4dd0:ff00:30e::1 eth0: 2001:4dd0:ff01:30e::1
Please check above, but if it's really a bad choice could you please provide a better one?
Why are you trying to guess random addresses? The Internet really does not work that way
You have two prefixes:
tunnel 2001:4dd0:ff00:30e::2/64 this is your side of the tunnel (2001:4dd0:ff00:30e::1 is the PoP)
subnet 2001:4dd0:fead::/48
For your eth0, you need to take a /64 out of the 'subnet' prefix, which is a /48 thus consisting of 65536 /64's. This /64 you have in radvd.conf and you also need to put an address out of that /64 on eth0.
eg, you could use in radvd.conf: 2001:4dd0:fead::/64 and configure on eth0: 2001:4dd0:fead::1
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 17:31:02
Yes you are right, sorry for this pretty dumb error.
The need to add the IPv6 Adress for eth0 seems to be new, did not find it in any guide but pulled the info from some forum thread. In addition I keep confusing subnet and tunnel adresses. My apologies.
So I changed the adress:
ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:4dd0:fead::1/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4261:86ff:fe5e:1b8b/64 scope link
valid_lft forever preferred_lft forever
5: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
inet6 2001:4dd0:ff00:30e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4cd0:ff00:30e:2/64 scope link
valid_lft forever preferred_lft forever
route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
2001:4dd0:fead::1/128 :: U 256 0 0 eth0
2001:4dd0:ff00:30e::/64 :: U 256 0 1 sixxs
fe80::/64 :: U 256 0 0 sixxs
fe80::/64 :: U 256 0 0 eth0
::/0 2001:4dd0:ff00:30e::1 UG 1024 0 0 sixxs
::/0 :: !n -1 1 41018 lo
::1/128 :: Un 0 1 2102 lo
2001:4dd0:fead::1/128 :: Un 0 1 0 lo
2001:4dd0:ff00:30e::/128 :: Un 0 1 0 lo
2001:4dd0:ff00:30e::2/128 :: Un 0 1 3997 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::4261:86ff:fe5e:1b8b/128 :: Un 0 1 4845 lo
fe80::4cd0:ff00:30e:2/128 :: Un 0 1 0 lo
ff00::/8 :: U 256 0 0 sixxs
ff00::/8 :: U 256 0 0 eth0
::/0 :: !n -1 1 41018 lo
(Both above on the server of course.)
The windows machine still has the servers local adress: fe80::4261:86ff:fe5e:1b8b%26 as gateway. Should it not have the adress of eth0 2001:4dd0:fead::1 now as gateway or am I mistaken? I restarted radvd and resetted the IPv6 part of my windows lan adapter. Maybe I just have to wait?
Thx, Levino
world wide IPv6 not reachable from LAN clients
inet6 2001:4dd0:fead::1/128 scope global
That really has to be a /64 as you are going to have a /64 on that interface. A /128 is only 1 address...
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Thursday, 23 June 2011 17:44:22
Thx again Jeroen, especially for your patience.
Ping and tracert working now from client. Still not able to open IPv6 webpages though. Trying to figure that issue out by myself for the moment.
world wide IPv6 not reachable from LAN clients
Paste your routing tables, traceroutes and if available, from a Linux machine, a tracepath6 to the target host. Possibly you have MTU issues. And of course check your firewall rules.
world wide IPv6 not reachable from LAN clients
Shadow Hawkins on Friday, 24 June 2011 11:12:01
I misconfigured ip6tables (wrong subnet again :D ). Fixed them settings now and everything works just fine! Great. One small issue is, that pings seem to be blocked from the wan to the lan, although I thought I allowed them (see below). Pinging LAN clients from the server or other LAN clients works fine.
#!/bin/sh
# simple-ipv6-firewall
# Reiko Kaps 2011 <rek@ct.de>
#
# kann ber /etc/network/interfaces oder /etc/rc.local
# automatisch gestartet werden
LO=lo
WAN=sixxs # fr gogo6 in 'tun' ndern
LAN=eth0 # unter Debian meist nur eth0
PREFIX="2001:4dd0:fead::/64"
[ -z $PREFIX ] && {
logger -s -t IPv6firewall "Kein Prefix gesetzt, Firewall nicht aktiv."
logger -s -t IPv6firewall "Bitte bearbeiten Sie die Datei $0."
exit 1
}
# zuerst alles lschen
ip6tables -F
ip6tables -X
# Allow anything on the local link
ip6tables -A INPUT -i $LO -j ACCEPT
ip6tables -A OUTPUT -o $LO -j ACCEPT
# Allow anything out on the internet
ip6tables -A OUTPUT -o $WAN -j ACCEPT
# Allow the localnet access us:
ip6tables -A INPUT -i $LAN -j ACCEPT
ip6tables -A OUTPUT -o $LAN -j ACCEPT
# Filter all packets that have RH0 headers:
ip6tables -A INPUT -m rt --rt-type 0 -j DROP
ip6tables -A FORWARD -m rt --rt-type 0 -j DROP
ip6tables -A OUTPUT -m rt --rt-type 0 -j DROP
# Allow Link-Local addresses
ip6tables -A INPUT -s fe80::/10 -j ACCEPT
ip6tables -A OUTPUT -s fe80::/10 -j ACCEPT
# Allow multicast
ip6tables -A INPUT -s ff00::/8 -j ACCEPT
ip6tables -A OUTPUT -s ff00::/8 -j ACCEPT
# Allow ICMPv6 everywhere
ip6tables -I INPUT -p icmpv6 -j ACCEPT
ip6tables -I OUTPUT -p icmpv6 -j ACCEPT
ip6tables -I FORWARD -p icmpv6 -j ACCEPT
# Allow forwarding
ip6tables -A FORWARD -m state --state NEW -i $LAN -o $WAN -s $PREFIX -j ACCEPT
ip6tables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
## SSH auf LAN-Rechner erlauben
# ip6tables -A FORWARD -i $WAN -p tcp -d 2001:db8::21c:c0ff:fec2:790f --dport 22 -j ACCEPT
# alles mitschreiben
#ip6tables -A INPUT -j LOG --log-prefix "IPv6-INPUT:"
#ip6tables -A FORWARD -j LOG --log-prefix "IPv6-FORWARD:"
#ip6tables -A OUTPUT -j LOG --log-prefix "IPv6-OUTPUT:"
# Per Vorgabe alles verwerfen
ip6tables -P INPUT DROP
ip6tables -P FORWARD DROP
ip6tables -P OUTPUT DROP
world wide IPv6 not reachable from LAN clients
![[nl]](/s/countries/nl.gif) Carmen Sandiego on Thursday, 23 June 2011 14:45:12
And as addition to Jeroen I don't see a Global address on the eth0 interface as described in the FAQ :
You will also need to add a single IP out of the above block to the interface itself, this as the machine won't accept the RA from itself due to when forwarding is enabled, RA gets disabled.
world wide IPv6 not reachable from LAN clients
Good catch, the route is then also not present on eth0.
The problem with the above btw is that on some setups it does properly work, on others it does not.
world wide IPv6 not reachable from LAN clients
Carmen Sandiego on Thursday, 23 June 2011 15:16:53
And why wouldn't it work? The routing is always pointing to the link local address and not the global address...so if you wouldn't use radvd and use static routes it might just work without the global address....didn't try that one yet though
world wide IPv6 not reachable from LAN clients
Not what I meant, let me rephrase:
in some cases when using RADVD one does not have to add an address to the local interface as the RA is used by that interface to configure itself....
Long time ago that I saw that happen though, maybe at one point radvd started disabling the accept_ra flag on the interface.
world wide IPv6 not reachable from LAN clients
Carmen Sandiego on Friday, 24 June 2011 08:53:46
Yes i understand, but why does the interface need a global IPv6 address at all while the machine behind the router uses the link local address of the router to route the packets? The global address isn't used for the routing isn't it?
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 22 June 2011 16:40:49
Posting is only allowed when you are