|
My first ipv6 network with troubles
![[es]](/s/countries/es.gif) Shadow Hawkins on Saturday, 03 December 2011 09:34:07
I have finally been able to get it working AICCU on my WRT54G with DD-WRT (dd-wrt.v24-10070_crushedhat_4MB) but i have some troubles i could not locate how to resolve.
I have radv and all seems to be fine on muy network.
I could ping tunnel from my Windows, Mac laptops.
But i could not ping outside so it seems thereis a problem routing rest of networks:?
Y could ping from router, so it seems the problem could be from LAN to br0 network via sixxs tunnel.
Here is my config:
br0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8
inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:17ff:fe49:d4b8/64 Scope:Link
inet6 addr: 2001:b18:406a::/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6418 errors:0 dropped:0 overruns:0 frame:0
TX packets:2643 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:619367 (604.8 KiB) TX bytes:1238521 (1.1 MiB)
br0:0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8
inet6 addr: fe80::212:17ff:fe49:d4b8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8285 errors:0 dropped:0 overruns:0 frame:0
TX packets:3042 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1116232 (1.0 MiB) TX bytes:1318655 (1.2 MiB)
Interrupt:5
eth1 Link encap:Ethernet HWaddr 00:12:17:49:D4:BA
inet6 addr: fe80::212:17ff:fe49:d4ba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:19799
TX packets:4109 errors:31 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:505136 (493.2 KiB)
Interrupt:4 Base address:0x1000
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 MULTICAST MTU:16436 Metric:1
RX packets:142 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10364 (10.1 KiB) TX bytes:10364 (10.1 KiB)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: fe80::a00:b/64 Scope:Link
inet6 addr: fe80::a9fe:ff01/64 Scope:Link
inet6 addr: 2001:b18:2000:124::2/64 Scope:Global
inet6 addr: fe80::a00:105/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:172 errors:0 dropped:0 overruns:0 frame:0
TX packets:185 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:63262 (61.7 KiB) TX bytes:34778 (33.9 KiB)
vlan0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8
inet6 addr: fe80::212:17ff:fe49:d4b8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6469 errors:0 dropped:0 overruns:0 frame:0
TX packets:2644 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:648448 (633.2 KiB) TX bytes:1249187 (1.1 MiB)
vlan1 Link encap:Ethernet HWaddr 00:12:17:49:D4:B9
inet addr:10.0.0.11 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::212:17ff:fe49:d4b9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1792 errors:0 dropped:0 overruns:0 frame:0
TX packets:402 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:317168 (309.7 KiB) TX bytes:55366 (54.0 KiB)
root@DD-WRT:~# ip -6 route ls
2001:b18:2000:124::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2001:b18:406a::/64 dev br0 metric 256 mtu 1500 advmss 1440
2001:b18:406a::/64 dev br0 metric 1024 mtu 1500 advmss 1440
unreachable 2001:b18:406a::/48 dev lo metric 1024 error -128 mtu 16436 advmss 16376
2000::/3 via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1280 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1440
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev br0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440
default via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1280 advmss 1220
root@DD-WRT:~#
root@DD-WRT:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
DROP udp -- anywhere anywhere udp dpt:route
DROP udp -- anywhere anywhere udp dpt:route
ACCEPT udp -- anywhere anywhere udp dpt:route
ACCEPT ipv6 -- anywhere anywhere
logaccept tcp -- anywhere DD-WRT tcp dpt:www
ACCEPT icmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state NEW
logaccept 0 -- anywhere anywhere state NEW
DROP 0 -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT gre -- 10.0.1.0/24 anywhere
ACCEPT tcp -- 10.0.1.0/24 anywhere tcp dpt:1723
ACCEPT 0 -- anywhere anywhere
DROP 0 -- anywhere anywhere state INVALID
TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN tcpmss match 1461:65535 TCPMSS set 1460
lan2wan 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
TRIGGER 0 -- anywhere anywhere TRIGGER type:in match:0 relate:0
trigger_out 0 -- anywhere anywhere
ACCEPT 0 -- anywhere anywhere state NEW
DROP 0 -- anywhere anywhere
root@DD-WRT:~# ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT tcp anywhere anywhere tcp flags:SYN,RST,ACK/SYN multiport dports ftp-data,ftp,ssh,smtp,www,https,ntp,domain
REJECT tcp anywhere anywhere tcp flags:SYN,RST,ACK/SYN reject-with icmp6-adm-prohibited
ACCEPT udp anywhere anywhere multiport dports ntp,domain
REJECT udp anywhere anywhere reject-with icmp6-adm-prohibited
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
root@DD-WRT:~#
root@DD-WRT:~# cat /proc/sys/net/ipv6/conf/all/forwarding
1
root@DD-WRT:~#
On my windows laptop
Adaptador de LAN inalmbrica Conexin de red inalmbrica:
Sufijo DNS especfico para la conexin. . :
Direccin IPv6 . . . . . . . . . . : 2001:b18:406a:0:a1d6:6e35:ceaa:7249
Direccin IPv6 . . . . . . . . . . : fd80:d198:6ed0:0:a1d6:6e35:ceaa:7249
Direccin IPv6 temporal. . . . . . : 2001:b18:406a:0:d0b1:c555:5937:2807
Direccin IPv6 temporal. . . . . . : fd80:d198:6ed0:0:d0b1:c555:5937:2807
Vnculo: direccin IPv6 local. . . : fe80::a1d6:6e35:ceaa:7249%11
Direccin IPv4. . . . . . . . . . . . . . : 10.0.1.104
Mscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : fe80::1eaa:7ff:feec:c8a3%11
fe80::212:17ff:fe49:d4b8%11
10.0.1.1
IPv6 Tabla de enrutamiento
===========================================================================
Rutas activas:
Cuando destino de red mtrica Puerta de enlace
11 281 ::/0 fe80::1eaa:7ff:feec:c8a3
11 281 ::/0 fe80::212:17ff:fe49:d4b8
1 306 ::1/128 En vnculo
11 33 2001:b18:406a::/64 En vnculo
11 281 2001:b18:406a:0:a1d6:6e35:ceaa:7249/128
En vnculo
11 281 2001:b18:406a:0:d0b1:c555:5937:2807/128
En vnculo
11 33 fd80:d198:6ed0::/64 En vnculo
11 281 fd80:d198:6ed0:0:a1d6:6e35:ceaa:7249/128
En vnculo
11 281 fd80:d198:6ed0:0:d0b1:c555:5937:2807/128
En vnculo
21 276 fe80::/64 En vnculo
22 276 fe80::/64 En vnculo
11 281 fe80::/64 En vnculo
21 276 fe80::3580:f1de:f889:7f00/128
En vnculo
22 276 fe80::4195:a6b8:f02b:100/128
En vnculo
11 281 fe80::a1d6:6e35:ceaa:7249/128
En vnculo
1 306 ff00::/8 En vnculo
21 276 ff00::/8 En vnculo
22 276 ff00::/8 En vnculo
11 281 ff00::/8 En vnculo
===========================================================================
Rutas persistentes:
Cuando destino de red mtrica Puerta de enlace
0 4294967295 ::/0 2001:b18:2000:124::1
0 4294967295 2001:b18:2000:124::/64 En vnculo
0 4294967295 ::/0 2001:b18:2000:124::1
0 4294967295 2001:b18:2000:124::/64 En vnculo
0 4294967295 ::/0 2001:b18:2000:124::1
0 4294967295 2001:b18:2000:124::/64 En vnculo
0 4294967295 ::/0 2001:b18:2000:124::1
0 4294967295 2001:b18:2000:124::/64 En vnculo
0 4294967295 ::/0 2001:b18:2000:124::1
===========================================================================
C:\Users\Alberto>
Pinging route from windows
C:\Users\Alberto>ping fe80::212:17ff:fe49:d4b8
Haciendo ping a fe80::212:17ff:fe49:d4b8 con 32 bytes de datos:
Host de destino inaccesible.
Host de destino inaccesible.
Respuesta desde fe80::212:17ff:fe49:d4b8: tiempo=7ms
Respuesta desde fe80::212:17ff:fe49:d4b8: tiempo=7ms
Estadsticas de ping para fe80::212:17ff:fe49:d4b8:
Paquetes: enviados = 4, recibidos = 2, perdidos = 2
(50% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mnimo = 7ms, Mximo = 7ms, Media = 7ms
C:\Users\Alberto>
I could not ping wan ipv6 address but i could get access to ipv4
C:\Users\Alberto>ping fe80::212:17ff:fe49:d4b9
Haciendo ping a fe80::212:17ff:fe49:d4b9 con 32 bytes de datos:
Host de destino inaccesible.
Estadsticas de ping para fe80::212:17ff:fe49:d4b9:
Paquetes: enviados = 1, recibidos = 0, perdidos = 1
(100% perdidos),
Control-C
^C
C:\Users\Alberto>ping 10.0.0.11
Haciendo ping a 10.0.0.11 con 32 bytes de datos:
Respuesta desde 10.0.0.11: bytes=32 tiempo=9ms TTL=63
Respuesta desde 10.0.0.11: bytes=32 tiempo=7ms TTL=63
Estadsticas de ping para 10.0.0.11:
Paquetes: enviados = 2, recibidos = 2, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mnimo = 7ms, Mximo = 9ms, Media = 8ms
Control-C
^C
C:\Users\Alberto>
Pinging tunnel and pinging my ipv6 address. (I think here could be the problem but not know how to solve)
C:\Users\Alberto>ping 2001:b18:2000:124::1
Haciendo ping a 2001:b18:2000:124::1 con 32 bytes de datos:
Respuesta desde 2001:b18:2000:124::1: tiempo=152ms
Respuesta desde 2001:b18:2000:124::1: tiempo=66ms
Respuesta desde 2001:b18:2000:124::1: tiempo=69ms
Estadsticas de ping para 2001:b18:2000:124::1:
Paquetes: enviados = 3, recibidos = 3, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mnimo = 66ms, Mximo = 152ms, Media = 95ms
Control-C
^C
C:\Users\Alberto>ping 2001:b18:2000:124::2
Haciendo ping a 2001:b18:2000:124::2 con 32 bytes de datos:
Host de destino inaccesible.
Estadsticas de ping para 2001:b18:2000:124::2:
Paquetes: enviados = 1, recibidos = 0, perdidos = 1
(100% perdidos),
Control-C
^C
C:\Users\Alberto>
Thanks in advance
Hope to give you enought info
My first ipv6 network with troubles
br0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8 inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::212:17ff:fe49:d4b8/64 Scope:Link inet6 addr: 2001:b18:406a::/64 Scope:Global
You configured the lowest address in a subnet, which is also called the 'subnet anycast address'.
While that sometimes works (only if you use a /128) in general it won't.
You need to use something like 2001:b18:406a::1/64 or generally better use the EUI-64 variant which for you is 2001:b18:406a:0:212:17ff:fe49:d4b8:/64
root@DD-WRT:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT 0 -- anywhere anywhere state RELATED,ESTABLISHED
Please note the FAQ about connection trackers and apply the correct raw iptables rule to avoid any problems with that.
Direccin IPv6 temporal. . . . . . : fd80:d198:6ed0:0:d0b1:c555:5937:2807
You might want to do a disconnect of the network adapter, a reboot, or a "netsh interface ipv6 reset" to get rid of that one. Looks like a ULA-C address which are not even out there yet....
Rutas persistentes: Cuando destino de red mtrica Puerta de enlace 0 4294967295 ::/0 2001:b18:2000:124::1
As 2001:b18:2000:124::1 is the tunnel address on the PoP you won't be able to reach it from your laptop which is behind your DD-WRT. This has to be the 2001:b18:406a::1/64 address mentioned above.
Which RA should autoconfigure.
Likely it is failing because of your use of the <prefix>::0 address aka the subnet anycast address, thus fix that first, then do a "netsh interface ipv6 reset" and all should clear up.
My first ipv6 network with troubles
Shadow Hawkins on Saturday, 03 December 2011 13:49:57
Thanks Joren:
I have fixed some things
I have assigned ipv6 fixed ip as follows
Adaptador de LAN inalmbrica Conexin de red inalmbrica:
Sufijo DNS especfico para la conexin. . :
Direccin IPv6 . . . . . . . . . . : 2001:b18:406a::2
Direccin IPv6 . . . . . . . . . . : 2001:b18:406a:0:a1d6:6e35:ceaa:7249
Direccin IPv6 . . . . . . . . . . : fd80:d198:6ed0:0:a1d6:6e35:ceaa:7249
Direccin IPv6 temporal. . . . . . : 2001:b18:406a:0:20f9:122a:9739:27ed
Direccin IPv6 temporal. . . . . . : fd80:d198:6ed0:0:20f9:122a:9739:27ed
Vnculo: direccin IPv6 local. . . : fe80::a1d6:6e35:ceaa:7249%11
Direccin IPv4. . . . . . . . . . . . . . : 10.0.1.104
Mscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : fe80::1eaa:7ff:feec:c8a3%11
fe80::212:17ff:fe49:d4b8%11
2001:b18:406a::1
10.0.1.1
Now br0 has correct config
root@DD-WRT:~# ifconfig
br0 Link encap:Ethernet HWaddr 00:12:17:49:D4:B8
inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:17ff:fe49:d4b8/64 Scope:Link
inet6 addr: 2001:b18:406a::1/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13123 errors:0 dropped:0 overruns:0 frame:0
TX packets:4580 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1355938 (1.2 MiB) TX bytes:3014405 (2.8 MiB)
root@DD-WRT:~# ip -6 route ls
2001:b18:2000:124::/64 via :: dev sixxs metric 256 mtu 1480 advmss 1420
2001:b18:406a::/64 dev br0 metric 256 mtu 1500 advmss 1440
2001:b18:406a::/64 dev br0 metric 1024 mtu 1500 advmss 1440
unreachable 2001:b18:406a::/48 dev lo metric 1024 error -128 mtu 16436 advmss 16376
2000::/3 via 2001:b18:2000:124::1 dev sixxs metric 1 mtu 1480 advmss 1420
2000::/3 via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1480 advmss 1420
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1420
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1420
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1420
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1420
fe80::/64 via :: dev sixxs metric 256 mtu 1480 advmss 1420
fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1440
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1420
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1420
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1420
ff00::/8 dev br0 metric 256 mtu 1500 advmss 1420
ff00::/8 dev sixxs metric 256 mtu 1480 advmss 1420
ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440
default via 2001:b18:2000:124::1 dev sixxs metric 1 mtu 1480 advmss 1420
default via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1480 advmss 1420
Will read FAQ in order to check Iptables
C:\Users\Alberto>ping 2001:b18:406a::1
Haciendo ping a 2001:b18:406a::1 con 32 bytes de datos:
Respuesta desde 2001:b18:406a::1: tiempo=5ms
Respuesta desde 2001:b18:406a::1: tiempo=4ms
Estadsticas de ping para 2001:b18:406a::1:
Paquetes: enviados = 2, recibidos = 2, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mnimo = 4ms, Mximo = 5ms, Media = 4ms
Control-C
^C
C:\Users\Alberto>ping chico.rediris.es
Haciendo ping a chico.rediris.es [2001:720:418:caf1::3] con 32 bytes de datos:
Control-C
^C
C:\Users\Alberto>
Now i can ping br0 , but no outside.
Will se and let you know
Thanks!
My first ipv6 network with troubles
Something is causing you to get a ULA-C address (fd80:...) you will want to get rid of those.
Direccin IPv6 . . . . . . . . . . : fd80:d198:6ed0:0:a1d6:6e35:ceaa:7249 Direccin IPv6 temporal. . . . . . : fd80:d198:6ed0:0:20f9:122a:9739:27ed
You still have two similar routes on your br0, check if you have added one manually and maybe one through an address.
2001:b18:406a::/64 dev br0 metric 256 mtu 1500 advmss 1440 2001:b18:406a::/64 dev br0 metric 1024 mtu 1500 advmss 1440
You have FOUR 'defaults' that are the same, you might want to get rid of three of them:
2000::/3 via 2001:b18:2000:124::1 dev sixxs metric 1 mtu 1480 advmss 1420 2000::/3 via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1480 advmss 1420 default via 2001:b18:2000:124::1 dev sixxs metric 1 mtu 1480 advmss 1420 default via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1480 advmss 1420
That MTU of 1480 is not good as there is at least one hop which makes it 1492 when tracing to your current IPv4 address:
8: 135.Red-80-58-67.staticIP.rima-tde.net 32.184ms pmtu 1492
From that (the rest of the routers do not answer at all thus it is to wonder if they lower it further) it should be at least 1492 - 20 = 1472.
Your best bet is 1280 (the default) though as that always works.
C:\Users\Alberto>ping chico.rediris.es
Instead of ping try 'tracert' because traceroute shows you what path packets take and thus where a problem starts to occur (though the packets might not come back because the route back is broken too)
My first ipv6 network with troubles
Shadow Hawkins on Saturday, 03 December 2011 15:03:05
FIxed :)
root@DD-WRT:~# ip -6 route ls
2001:b18:2000:124::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2001:b18:406a::/64 dev br0 metric 256 mtu 1280 advmss 1220
unreachable 2001:b18:406a::/48 dev lo metric 1024 error -128 mtu 16436 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev br0 metric 256 mtu 1280 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
fe80::/64 dev vlan1 metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev br0 metric 256 mtu 1280 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev vlan1 metric 256 mtu 1280 advmss 1220
default via 2001:b18:2000:124::1 dev sixxs metric 1024 mtu 1280 advmss 1220
root@DD-WRT:~#
MPRO-Despacho:~ albersag$ ping6 chico.rediris.es
PING6(56=40+8+8 bytes) 2001:b18:406a::3 --> 2001:720:418:caf1::3
16 bytes from 2001:720:418:caf1::3, icmp_seq=0 hlim=50 time=108.746 ms
16 bytes from 2001:720:418:caf1::3, icmp_seq=1 hlim=50 time=108.834 ms
^C
--- chico.rediris.es ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 108.746/108.790/108.834/0.044 ms
mac is working. But windows is impossible. I could see how to deactivce UAL address as you reported me.
Disabled components on ipv6, disabled vmware network interface to see if it causes it, but no way. Will investigate.
Thanks Jeroen for your help
Step by step im learning.
My first ipv6 network with troubles
Shadow Hawkins on Saturday, 03 December 2011 16:32:24
Hi again
I have tested disable 6to4 , taredo , itap , privacy disabled
but always appears fd80: ip addres if i remove with netsh command
it appears again?
Do you know how to fix that?
I have been reading for a while, but no solution
Two different windows machines and same problem
Adaptador de LAN inalmbrica Conexin de red inalmbrica:
Sufijo DNS especfico para la conexin. . :
Direccin IPv6 . . . . . . . . . . : 2001:b18:406a:0:2dcd:211a:a695:5c3c
Direccin IPv6 . . . . . . . . . . : fd80:d198:6ed0:0:2dcd:211a:a695:5c3c
Direccin IPv6 temporal. . . . . . : 2001:b18:406a:0:9db3:2464:ff63:a86a
Direccin IPv6 temporal. . . . . . : fd80:d198:6ed0:0:9db3:2464:ff63:a86a
Vnculo: direccin IPv6 local. . . : fe80::2dcd:211a:a695:5c3c%12
Direccin IPv4. . . . . . . . . . . . . . : 10.0.1.108
Mscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : fe80::1eaa:7ff:feec:c8a3%12
fe80::212:17ff:fe49:d4b8%12
10.0.1.1
Thanks
My first ipv6 network with troubles
Puerta de enlace predeterminada . . . . . : fe80::1eaa:7ff:feec:c8a3%12 fe80::212:17ff:fe49:d4b8%12
I guess that means "Gateway addresses", this shows you have two of them (and an IPv4 one).
The latter (ending in d4b8) is obviously the correct one as that matches the addresses seen in the ifconfigs you pasted. Thus now you have to find the device which acts as an IPv6 gateway which has the IPv6 Link-Local address fe80::1eaa:7ff:feec:c8a3 and thus MAC address 1c:aa:07:ec:c8:a3 which according to that is a Cisco device but that could also be a Linksys device.
That one is configured to announce a ULA address and that might be causing some issues for you as routing becomes nondeterministic.
My first ipv6 network with troubles
Shadow Hawkins on Saturday, 03 December 2011 17:14:38
Hi Jeroen
You are fine my friend
It seems new router i have, is a new model where im in betatesting it, is making that stuff
Will report to cisco, as its a problem if you have other router on network.
It was making me crazy
Lets see how i could disable and let you know back
REally Thanks!
My first ipv6 network with troubles
Shadow Hawkins on Saturday, 03 December 2011 17:24:41
I have disabled IPV6 /IPV4 mode on router and voila!
C:\Users\Alberto>ping chico.rediris.es
Haciendo ping a chico.rediris.es [2001:720:418:caf1::3] con 32 bytes de datos:
Respuesta desde 2001:720:418:caf1::3: tiempo=114ms
Respuesta desde 2001:720:418:caf1::3: tiempo=113ms
Respuesta desde 2001:720:418:caf1::3: tiempo=121ms
Respuesta desde 2001:720:418:caf1::3: tiempo=123ms
Estadsticas de ping para 2001:720:418:caf1::3:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mnimo = 113ms, Mximo = 123ms, Media = 117ms
Adaptador de LAN inalmbrica Conexin de red inalmbrica:
Sufijo DNS especfico para la conexin. . :
Direccin IPv6 . . . . . . . . . . : 2001:b18:406a:0:a1d6:6e35:ceaa:7249
Direccin IPv6 temporal. . . . . . : 2001:b18:406a:0:c444:d216:f326:8f1f
Vnculo: direccin IPv6 local. . . : fe80::a1d6:6e35:ceaa:7249%11
Direccin IPv4. . . . . . . . . . . . . . : 10.0.1.104
Mscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : fe80::212:17ff:fe49:d4b8%11
10.0.1.1
Adaptador de Ethernet Conexin de rea local:
Lets see what cisco tell me.. that was the cause.. amazing!
Jeroen you are great!
|
![[ch]](/s/countries/ch.gif)
on Saturday, 03 December 2011 12:50:37
Posting is only allowed when you are