gmane.network.ipv6.miredo.devel

problem pinging teredo address over switch (bug report?)

Eric Anopolsky — 2008-10-10T20:33:32

Hi, I'm having a problem involving two hosts using miredo. The first is a home server that is connected via ethernet to a wireless/wired router, which is connected to the Internet via DSL. The second host is a laptop that is sometimes connected to the same wireless/wired router and is sometimes connected to a similar setup at work (laptop---wireless/wired router---cable modem). Both wireless/wired routers do NAT for IPv4. When at work, the laptop can ping6 the server's teredo IP. However, at home, I get the following result when I try to ping6 the server from the laptop: eric< at >telesto:~$ ping6 SERVER_IP PING SERVER_IP(SERVER_IP) 56 data bytes From LAPTOP_IP icmp_seq=11 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=12 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=13 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=14 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=15 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=16 Destination unreachable: Address unreachable From LAPTOP_IP icmp_seq=17 Destination unreachable: Address unreachable --- SERVER_IP ping statistics --- 17 packets transmitted, 0 received, +7 errors, 100% packet loss, time 16009ms ...where SERVER_IP is the server's teredo address and LAPTOP_IP is the laptop's teredo address. My understanding of teredo is that this should work. What could be going wrong? Cheers, Eric

Questions and implementation advice about Miredo

Mark van Herpen — 2008-10-13T12:41:45

Hallo, Last week I found Miredo for implementing the Toredo protocol. And I find it very interesting, but I still have some questions. I'm working for a small internet provider based in the Netherlands. We mostly have DSL costumers. We want to implement a IPv6 solutions for those customers, but we aren't able to deliver them native IPv6 due to our DSL-network suppliers. Because most of the DSL modem/routers don't understand tunneling with ipv6, we would like to implement a solution which works with NAT. I've tested your Miredo software, and it works great :). But, now I've got some implementation questions. We want to have our customers a IPv6 address of ours, and not an address from the Toredo pool. I've read in the mailing list archive that this is possible, but there is no answer given on how this is done, except that it's not a standard solution. We want to use a /64 or /48 subnet for this. But when I use a /48 prefix in the configuration, the miredo software keeps assigning an address which isn't in that subnet, only the 'start part' is. So I guess I must change the source code, but I don't know exactly which parts I have to change. Could you tell me how we should do this? Also, I've set up a relay server. Because I understand that all the traffic must go through this relay host if we use a subnet of our own. I understand that this server must announce this subnet via bgp to our border network in order to work. But the relay server I've set up, doesn't relay :( I used the normal Toredo prefix for client,server and relay, but the relay server isn't used. Everything is working fine, but traffic is not send through the relay server. Can you explain to me how the client knows to send it's traffic through the relay server? Because this isn't used in the server or client configuration. Thanks in advance, I look forward to your reply. Grtz, Mark van Herpen

Intermittent connectivity

Adam MacBeth — 2008-09-26T01:12:38

I'm running the Miredo client 1.1.5-2 on Debian (installed the .deb) and I'm seeing regular connectivity problems. Every so often (somewhere between 2 and 20 minutes, usually about 5) I see "Lost Teredo connectivity" in the logs. After a minute or two connectivity is regained. If I restart miredo, it immediately regains connectivity. This is wreaking havoc on my ability to connect to this machine. IPv4 connectivity does not appear to be affected. The client is configured to use Microsoft's servers right now, but I see the same problems with remlab.net. These servers appear to be responsive at all times. Any thoughts on what might be going on here? Are there any timeout parameters I can tune to improve this situation? Thanks, Adam

difficulty with XP SP2 and Vista SP0

Carlos Rendon — 2008-09-10T21:46:00

Greetings- I'm running miredo-server 1.1.5 on Fedora 9. I haven't been able to get XP SP2 or Vista SP1 to work. However Vista SP0 works perfectly fine and the miredo client running on a separate Fedora 9 machine also works fine. The network setup is the same in all scenarios. The clients are behind a Linksys router and get addresses in 192.168.1.x, the server is 193.168.1.1 and 193.168.1.2. For the Windows firewall setups UDP ports 3544 and 11111 are opened and I've forced Windows to use 11111 for teredo. I've included packet captures of both scenarios below (just ICMPv6 packets). Please let me know if additional information would be useful in diagnosing the problem. Thanks, Carlos Here is the XP SP2 capture: No. Time Source Destination Protocol Info 10 5.018549 fe80::8000:5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 a2 00 00 80 11 b4 2b c0 a8 01 65 c1 a8 .i.......+...e.. 0020 01 01 2b 67 0d d8 00 55 34 24 00 01 00 00 5e 18 ..+g...U4$....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 80 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 11 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 11 5.019042 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::8000:5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b ab 00 00 40 11 b9 f9 c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 80 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 4c 17 00 00 00 00 00 .TEREDO..L...... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 17 20.023018 fe80::8000:5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 a8 00 00 80 11 b4 25 c0 a8 01 65 c1 a8 .i.......%...e.. 0020 01 01 2b 67 0d d8 00 55 34 24 00 01 00 00 5e 18 ..+g...U4$....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 80 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 11 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 18 20.023076 fe80::8000:5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 a9 00 00 80 11 b4 24 c0 a8 01 65 c1 a8 .i.......$...e.. 0020 01 01 2b 67 0d d8 00 55 34 24 00 01 00 00 5e 18 ..+g...U4$....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 80 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 11 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 19 20.023120 fe80::8000:5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 aa 00 00 80 11 b4 23 c0 a8 01 65 c1 a8 .i.......#...e.. 0020 01 01 2b 67 0d d8 00 55 34 24 00 01 00 00 5e 18 ..+g...U4$....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 80 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 11 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 20 20.023537 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::8000:5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b1 00 00 40 11 b9 f3 c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 80 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 4c 17 00 00 00 00 00 .TEREDO..L...... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 21 20.023577 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::8000:5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b2 00 00 40 11 b9 f2 c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 80 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 4c 17 00 00 00 00 00 .TEREDO..L...... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 22 20.023608 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::8000:5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b3 00 00 40 11 b9 f1 c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 80 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 4c 17 00 00 00 00 00 .TEREDO..L...... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 27 20.065579 fe80::5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 ad 00 00 80 11 b4 1f c0 a8 01 65 c1 a8 .i...........e.. 0020 01 02 2b 67 0d d8 00 55 34 23 00 01 00 00 5e 18 ..+g...U4#....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 00 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 91 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 28 20.065984 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b4 00 00 40 11 b9 f0 c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 cc 17 00 00 00 00 00 .TEREDO......... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 29 24.065668 fe80::5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 ae 00 00 80 11 b4 1e c0 a8 01 65 c1 a8 .i...........e.. 0020 01 02 2b 67 0d d8 00 55 34 23 00 01 00 00 5e 18 ..+g...U4#....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 00 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 91 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 30 24.066128 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b5 00 00 40 11 b9 ef c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 cc 17 00 00 00 00 00 .TEREDO......... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 31 28.065773 fe80::5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 af 00 00 80 11 b4 1d c0 a8 01 65 c1 a8 .i...........e.. 0020 01 02 2b 67 0d d8 00 55 34 23 00 01 00 00 5e 18 ..+g...U4#....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 00 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 91 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 32 28.066225 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b6 00 00 40 11 b9 ee c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 cc 17 00 00 00 00 00 .TEREDO......... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 33 32.065837 fe80::5445:5245:444f ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 14 22 53 42 93 08 00 45 00 ..f.d..."SB...E. 0010 00 69 01 b0 00 00 80 11 b4 1c c0 a8 01 65 c1 a8 .i...........e.. 0020 01 02 2b 67 0d d8 00 55 34 23 00 01 00 00 5e 18 ..+g...U4#....^. 0030 0b 15 83 3c 5b 24 00 60 00 00 00 00 18 3a ff fe ...<[$.`.....:.. 0040 80 00 00 00 00 00 00 00 00 54 45 52 45 44 4f ff .........TEREDO. 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 91 4b 00 00 00 00 01 02 00 00 00 00 00 00 00 ..K............. 0070 00 00 00 00 00 00 00 ....... No. Time Source Destination Protocol Info 34 32.066288 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::5445:5245:444f ICMPv6 Router advertisement 0000 00 14 22 53 42 93 00 0f 66 08 64 9b 08 00 45 00 .."SB...f.d...E. 0010 00 91 3b b7 00 00 40 11 b9 ed c1 a8 01 02 c0 a8 ..;...< at >......... 0020 01 65 0d d8 2b 67 00 7d 61 c1 00 01 00 00 5e 18 .e..+g.}a.....^. 0030 0b 15 83 3c 5b 24 00 00 00 d4 98 3e 57 fe e1 60 ...<[$.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 54 45 52 45 44 4f 86 00 cc 17 00 00 00 00 00 .TEREDO......... 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... ------------------------------------------------------------------------------------- Here is the Vista SP1 capture: No. Time Source Destination Protocol Info 84 44.304749 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 37 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.7.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 86 44.307488 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 37 00 00 40 11 b9 6f c1 a8 01 01 c0 a8 ..<7..< at >..o...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 89 45.318137 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 3a 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.:.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 90 45.318661 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 39 00 00 40 11 b9 6d c1 a8 01 01 c0 a8 ..<9..< at >..m...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 91 47.330522 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 3b 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.;.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 92 47.331052 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 3a 00 00 40 11 b9 6c c1 a8 01 01 c0 a8 ..<:..< at >..l...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 96 51.339677 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 3f 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.?.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 97 51.340206 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 3c 00 00 40 11 b9 6a c1 a8 01 01 c0 a8 ..<<..< at >..j...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 101 59.342589 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 43 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.C.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 102 59.343122 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 3d 00 00 40 11 b9 69 c1 a8 01 01 c0 a8 ..<=..< at >..i...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ............... No. Time Source Destination Protocol Info 107 75.348333 fe80::ffff:ffff:fffe ff02::2 ICMPv6 Router solicitation 0000 00 0f 66 08 64 9b 00 18 8b 29 8d e8 08 00 45 00 ..f.d....)....E. 0010 00 59 01 46 00 00 80 11 00 00 c0 a8 01 64 c1 a8 .Y.F.........d.. 0020 01 01 2b 67 0d d8 00 45 85 0c 00 01 00 00 5e ec ..+g...E......^. 0030 04 fa 2c 78 84 4b 00 60 00 00 00 00 08 3a ff fe ..,x.K.`.....:.. 0040 80 00 00 00 00 00 00 00 00 ff ff ff ff ff fe ff ................ 0050 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 ................ 0060 00 7d 38 00 00 00 00 .}8.... No. Time Source Destination Protocol Info 108 75.348872 fe80:0:c1a8:102:8000:dd8:3e57:fefe fe80::ffff:ffff:fffe ICMPv6 Router advertisement 0000 00 18 8b 29 8d e8 00 0f 66 08 64 9b 08 00 45 00 ...)....f.d...E. 0010 00 91 3c 3e 00 00 40 11 b9 68 c1 a8 01 01 c0 a8 ..<>..< at >..h...... 0020 01 64 0d d8 2b 67 00 7d a4 ce 00 01 00 00 5e ec .d..+g.}......^. 0030 04 fa 2c 78 84 4b 00 00 00 ad 88 3e 57 fe e1 60 ..,x.K.....>W..` 0040 00 00 00 00 38 3a ff fe 80 00 00 c1 a8 01 02 80 ....8:.......... 0050 00 0d d8 3e 57 fe fe fe 80 00 00 00 00 00 00 00 ...>W........... 0060 00 ff ff ff ff ff fe 86 00 b6 f2 00 00 00 00 00 ................ 0070 00 00 00 00 00 07 d0 03 04 40 40 ff ff ff ff ff .........< at >< at >..... 0080 ff ff ff 00 00 00 00 20 01 00 00 c1 a8 01 01 00 ....... ........ 0090 00 00 00 00 00 00 00 05 01 00 00 00 00 05 00 ...............

miredo-server on FreeBSD and vista teredo

Jason DiCioccio — 2008-08-23T11:22:15

Greetings all, I'm running miredo-server from ports on FreeBSD 7.0 and having a bit of an issue when trying to connect with a vista client. The Vista client works fine when using microsoft's teredo server(s), however when I try to use miredo I get the error: "Primary teredo server unreachable over UDP." Analyzing the traffic with wireshark on the Vista side shows the router solicitation being sent out, as well as the advertisement being sent back, however I'm not sure what happens with it afterwards. The client keeps sending solicitations as if the advertisement didn't exist. Any help would be appreciated. I've been unable to find any suitable information on google thus far. Thanks! Jason DiCioccio

Need for a computer security contact (FIRST REQUEST) - miredo VEND#144414

CERT Coordination Center — 2008-08-01T19:10:18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Folks: We are aware of a problem with one of your products. We are interested in establishing a formal contact with you to facilitate the coordination of vulnerability remediation. Given the sensitive nature of the information typically exchanged during the vulnerability remediation process, we are interested in exchanging PGP or GnuPG keys with you to ensure secure communication. Please follow the steps listed below to begin the key exchange process: 1. You generate a PGP or GnuPG key pair if you do not already have one. 2. You then send the public key to public.gmane.org> via email signed with that key. Please include "VEND#144414" in the subject line of your email message. 3. We will then contact you out-of-band via a trusted telephone number to verify your key fingerprint. This will involve your reading the key fingerprint back to us in hexidecimal format. 4. We will then use your public key to send mail to you encrypted with your key. This mail will also contain information on obtaining the CERT/CC's public key. 5. You then decrypt the mail, and follow the brief instruction within that mail. If you have any questions or concerns pertaining to this request, please do not hesitate to contact me via the CERT Hotline: 412.268.7090. Thank you in advance for your cooperation. Regards, Tony LeDonne CERT Coordination Center | Internet E-mail: cert-etTNj8cnB6w< at >public.gmane.org Software Engineering Institute | Telephone: +1-412-268-7090 24-hour hotline Carnegie Mellon University | - phone answered by CERT personnel Pittsburgh PA 15213-3890 | during business days (Monday - Friday), | from 08:00-20:00 EST/EDT (GMT-5/GMT-4); http://www.cert.org/ | on call for emergencies during other hours * CERT is a registered service mark of Carnegie Mellon University. Registered in U.S. Patent and Trademark Office. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iQEVAwUBSJNfcxBA4qoUwz9XAQIA0Af+O5eoFfoAlOo1yojg9dDbfGtr/C/lmdvL Nj3RnX59eSsj5iLZxa1lXTR+GiwDB2m2eYfOeg5jYhUpbhn2K3LEpbA+v5AFvTrW krlx/88lV+wreTGzNLoXU52T42ni0XJx/Zfiio4pLs5MTNK+VslTlnqFn4H0Parx 6jdig7eJIA04oFDs7NezTwSBWNFzkUUwVYwsYtFuaV9Le8ilGCp2S216SXDAhrPe 4HzFqHgefHUmcaH3M9YRghYmGpnI22bKu0TR3KpF+VSFZl63jp+1GbnNiuQPLMHC Kkkj2+RXT3TlQVfdv5VmqOou/LHCXi6FCdp1L3AnZvbwmRUp/+Iriw== =kWVa -----END PGP SIGNATURE-----

ping6 sending to miredo server, not relay

Robert Moskowitz — 2008-07-16T20:15:14

I am running Miredo 1.0.6-1 on Centos 5.2 from the rpmforge repo. I am running a Miredo Server and Relay on a system on my home net (with native IPv6). The server is on port 3544 with two consecutive IPv4 addresses. The relay is on port 3545. I can at times get my Miredo client to connect to the server and get an address. And at times the default v6 route (0::/0) is to the Teredo interface (if I start and stop things enough, either get no response from the server, or I get a response, but my default address is to eth1!). Anyway, right now things all look right. So I do a ping6 -n. I get a proper public v6 address from DNS. The ping6 does out, but to port 3544, not to 3545. I cannot see anything in the miredo.conf man to tell me how to set up the client to what port the relay is on. On the server, I cannot find anything in the miredo-server.conf about connecting to the relay and providing that information to the client. Can someone PLEASE help me out?

Getting relaying working

Robert Moskowitz — 2008-07-16T14:13:02

I am running Miredo 1.0.6-1 on Centos 5.2 from the rpmforge repo. I have edited the /etc/miredo.conf file to use the Microsoft Teredo server: ServerAddress teredo.ipv6.microsoft.com I get an address: Jul 16 07:34:27 nc2400 miredo[6141]: Starting... Jul 16 07:34:27 nc2400 kernel: ADDRCONF(NETDEV_CHANGE): teredo: link becomes ready Jul 16 07:34:35 nc2400 miredo[6145]: Qualified (NAT type: restricted) Jul 16 07:34:35 nc2400 miredo[6145]: New Teredo address/MTU Jul 16 07:34:35 nc2400 miredo[6145]: Teredo pseudo-tunnel started Jul 16 07:34:35 nc2400 miredo[6145]: (address: 2001:0:4137:9e50:0:7fea:b75b:47b9, MTU: 1280) Jul 16 07:34:35 nc2400 kernel: teredo: Disabled Privacy Extensions And I have a default route: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface 2001::/32 :: U 256 0 0 teredo fe80::/64 :: U 256 0 0 eth1 fe80::/64 :: U 256 0 0 teredo ::/0 :: U 1029 0 0 teredo But a PING6 fails: ping6 www.verilan.com PING www.verilan.com(2607:f0d8:201:1::3) 56 data bytes From 2001:0:4137:9e50:0:7fea:b75b:47b9 icmp_seq=10 Destination unreachable: Address unreachable From 2001:0:4137:9e50:0:7fea:b75b:47b9 icmp_seq=11 Destination unreachable: Address unreachable From 2001:0:4137:9e50:0:7fea:b75b:47b9 icmp_seq=12 Destination unreachable: Address unreachable From 2001:0:4137:9e50:0:7fea:b75b:47b9 icmp_seq=13 Destination unreachable: Address unreachable What have I missed? (BTW, from a system I have on native IPv6, I can ping6 www.verilan.com with no problem).

[MS-TERE]: Teredo Extensions

Bartley, M. James — 2008-05-06T19:04:40

Re: http://www.remlab.net/miredo/faq.shtml.en#symmnat ... How about an anonymously-/publicly-accessible page? http://msdn.microsoft.com/en-us/library/cc247482.aspx http://msdn.microsoft.com/en-us/library/cc247488.aspx - mjamesb

Is there a ISATAP client?

George — 2008-04-12T19:42:30

I know that Miredo can be a ISATAP server, but how abort ISATAP client? Could Miredo work as a ISATAP client? If not, anybody know to make ISATAP works on Linux? THANKS!

Subnet with Teredo?

Andre-John Mas — 2008-04-05T20:30:08

Hi, Is it possible to create a subnet with the Miredo/Teredo? If it is, how do I know which prefix I should be using? Andre

Miredo at Soft5000 ?

Nadina — 2008-03-27T12:58:23

Hello there, My name is Nadina and I work for Soft5000. We just added to our database. You can see the software details here: http://linux.soft5000.com/download1582.html We ask you if you can, please add our link http://linux.soft5000.com to your references page. Thank you and hope to see more of your products launched soon, Nadina

Why my question is not answered?

Edwin Sanjoto — 2008-03-12T07:35:28

routing all traffic through a relay

Amir Malik — 2008-02-21T08:57:41

Hi, I have set up both a Miredo server and relay on a machine with IPv6 connectivity. From all my Teredo clients, I can access the outside IPv6 world by specifying this server in their Miredo configuration files. The server machine has been assigned a /48 chunk of address space. Clients connecting to any site in this space work properly as a direct/least-hops route. However, when I try to access IPv6 sites outside of this /48, the traffic does not go to the relay I have set up, rather it goes through *.consulintel.es relays, even though my relay/server has (BGP-announced) routes to sites outside of my own /48. I suppose miredo-server is ignoring local routes... Is there a way to let miredo-server know to only use the local relay? Or is route selection happening on the client? All my clients are Miredo... From Teredo client: traceroute to www.isc.org (2001:4f8:0:2::d) from 2001:0:d820:54dd:8c8:f227:b381:5c63, 30 hops max, 16 byte packets 1 2a01:48:1:1:2e0:81ff:fe05:4657 (2a01:48:1:1:2e0:81ff:fe05:4657) 216.85 ms 191.882 ms 205.001 ms 2 gr2000.consulintel.es (2a01:48:1::ff0) 382.064 ms 198.317 ms 186.224 ms ... From Miredo relay/server: traceroute to www.isc.org (2001:4f8:0:2::d) from 2001:4830:e4:a::2, 30 hops max, 16 byte packets 1 15.ip-0-1-0.cr1.dfw1.us.occaid.net (2001:4830:e4:a::1) 1.884 ms 2.037 ms 1.85 ms 2 dcr01-p1-5.lsan01.occaid.net (2001:4830:ff:e101::1) 35.432 ms 35.338 ms 35.538 ms ... Why is it taking a longer route, whereas it could use the relay's default route to reach the destination? Thanks. - Amir

Miredo 1.1.4 building failing on MacOS X 10.4.11

Andre-John Mas — 2008-01-04T22:27:39

Hi, I seem to have run into a few problems compiling Miredo 1.1.4 on MacOS X 10.4.11 (PowerPC G4). ./configure --without-Judy make I get the following error: powerpc-apple-darwin8-gcc-4.0.1: -framework: linker input file unused because linking not done powerpc-apple-darwin8-gcc-4.0.1: SystemConfiguration: linker input file unused because linking not done powerpc-apple-darwin8-gcc-4.0.1: -framework: linker input file unused because linking not done powerpc-apple-darwin8-gcc-4.0.1: CoreFoundation: linker input file unused because linking not done gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I.. -D_REENTRANT -DLOCALEDIR=\"/usr/local/share/locale\" -O2 -I/opt/local/include -I/usr/include/ -I/usr/local/include/ -I/usr/local/include -g -O2 -framework SystemConfiguration -framework CoreFoundation -Wall -Wextra -Wundef -Wpointer-arith -Wbad-function-cast -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-noreturn -Wpacked -Wnested-externs -Wredundant-decls -MT packets.lo -MD -MP -MF .deps/packets.Tpo -c packets.c -o packets.o mv -f .deps/packets.Tpo .deps/packets.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I.. -D_REENTRANT -DLOCALEDIR=\"/usr/local/share/locale\" -O2 -I/opt/local/include -I/usr/include/ -I/usr/local/include/ -I/usr/local/include -g -O2 -framework SystemConfiguration -framework CoreFoundation -Wall -Wextra -Wundef -Wpointer-arith -Wbad-function-cast -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-noreturn -Wpacked -Wnested-externs -Wredundant-decls -MT peerlist.lo -MD -MP -MF .deps/peerlist.Tpo -c -o peerlist.lo peerlist.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I.. -D_REENTRANT -DLOCALEDIR=\"/usr/local/share/locale\" -O2 -I/opt/local/include -I/usr/include/ -I/usr/local/include/ -I/usr/local/include -g -O2 -framework SystemConfiguration -framework CoreFoundation -Wall -Wextra -Wundef -Wpointer-arith -Wbad-function-cast -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-noreturn -Wpacked -Wnested-externs -Wredundant-decls -MT peerlist.lo -MD -MP -MF .deps/peerlist.Tpo -c peerlist.c -fno-common -DPIC -o .libs/peerlist.o peerlist.c: In function 'teredo_list_lookup': peerlist.c:365: error: 'union teredo_addr' has no member named '__u6_addr' peerlist.c:370: error: 'union teredo_addr' has no member named '__u6_addr' make[3]: *** [peerlist.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Any ideas? I will see if I installing Judy makes a difference. Andre

installing miredo in freeBSD 6.2

danank a a — 2007-12-24T08:33:05

Dear sir, My name danang, I'm college student Would You mind helping me about miredo installation, I have a problem when installing them I use freeBSD 6.2 when I compiled the source code as usual, it say "you need to install Judy library..... etc" and then I installed Judy-1.0.4 but when I use command "make" an eror occured in my attachment I include the eror, please help me.... thanks before ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

isatapd stops working

Glen Eustace — 2007-12-20T03:31:05

Hi, I have isatapd running on a Fedora 7 platform. When one first starts it it works great. Provided one continues generating traffic, the tunnel works. However, if thing go quiet for a while, I haven't managed to determine how long yet, but in the order of 5 - 10 minutes, one gets a network unreachable the next time any IPv6 activity occurs. If there is anything I can do to assts with debugging please let me know. The remote end is a Cisco 6500 Sup 720 running IOS 122-18.SXF6

optional "fixed" teredo address

Frans van Dorsselaer — 2007-11-18T09:59:08

Got an address, but can't use it

2007-11-07T16:11:50

Hi, I've got miredo 1.1.3 installed on Fedora Core 7 and am running in client mode. To get things running I had to edit client-hook to hardcode IP="/sbin/ip" as "$(which ip)" was returning an error for some reason probably to do with my environment. I also defined TABLE=252 in client-hook and edited /etc/iproute2/rt_tables to include the line 252teredo Running miredo -f gets me an address and I can see Router Solicitations and Advertisements on the wire. Things fail when I try ping6 www.kame.net which returns connect: Network is unreachable Any ideas? Mat Ford Principal Researcher BT Group Chief Technology Office office:(+44)(0)1875 341678 mobile:(+44)(0)7917 021303 fax:(+44)(0)1908 860131 meetme:(+44)(0)870 2412996 code: 81010840# (0)800 0321609 pp HWP276, PO Box 234 (HOM-EH), Edinburgh EH12 9UR, UK ________________________________________________ British Telecommunications plc Registered office: 81 Newgate Street London EC1A 7AJ. Registered in England no. 1800000 This electronic message contains information from British Telecommunications plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address above) immediately.

Teredo Relay overloaded?

Miguel A. Diaz — 2007-10-04T16:08:31

Hi, I've noticed that my Teredo Relay (miredo-1.1.2 on linux 2.4.20-8) is working not so well. I can see it is relaying a lot of Teredo traffic, around 100 Kbps (which means around 90 packets per second) for outgoing traffic (native IPv6 --> Teredo Client) and around 50 Kbps (around 40 packets per second) for incoming traffic (Teredo Client --> native IPv6), average data. The network link is not overloaded because I have bandwidth enough. Those data seems to indicate that the Teredo Relay is working well. However when I try to ping6 from one native IPv6 node (PC1 below) using my Teredo Relay to one specific Teredo client (PC2 below), I have no ping6 replies. +------+ ~ ---------------- ~ | PC1 | ( Internet IPv6 )<------>+------+ ~ ---------------- ~ / / / \ +------+ / \ +----------+ +--------+ | Teredo | | Teredo | |==>| Server 1 | | Relay | | +----------+ +--------+ | \ / | \ / | \ / | \ / | ~ ---------------- ~ | ( Internet IPv4 ) | ~ ---------------- ~ | / | / | / | / | +------+ | | PC2 | (Teredo Client) | +------+ (qualifed in Teredo Server 1) |======>/ / (Behind restricted NAT) +------+ In that figure, the PC2 is a Teredo Client qualified at Microsoft Teredo Server (other teredo servers also tested with the same result). The PC2 is behind a restricted NAT. PC1 is a native IPv6 host (several hosts tested with the same result) which tries to ping6 to PC2. I can see the icmp6 echo request packets coming to my Teredo Relay (tcpdump) so I'm sure the Teredo Relay used for communicating with PC2 is my Relay. In this scenario (restricted NAT), the Teredo Relay MUST send one Teredo Bubble to the Teredo Server where the client has been qualified. However I've checked with tcpdump that such a packet is never sent. The ping6 request is no forwarded neither to PC2. I've noticed a similar behavior when pinging6 from PC2 to PC1. Teredo Bubbles are not sent from the Relay to the Teredo Server and so PC2 doesn't know what Relay to use. Consequently IPv6 communication between PC2 and PC1 is not possible. As I said before, I can check that the Relay is relaying lot of Teredo traffic, so I wonder why some IPv6/Teredo packets are not forwarded. Has anyone noticed a similar behavior? Is there any limit on the kernel, the miredo implementation or whatever about the maximum number of UDP packets to be processed? If so, can I modify such a limit to increase the processed packet rate? Is the Relay overloaded and consequently it can't proccess all the Teredo traffic? Any clue? Best Regards Miguel ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

Size of IPv6 routing table

Miguel A. Diaz — 2007-09-10T11:15:56

Hi, We have recently checked that the Teredo traffic has increased notably since middle of august in our public Teredo relay. As consequence of such huge relay traffic I've realized that a thousands of IPv6 /128 prefixes belonging to the Teredo Prefix are included into the IPv6 routing table: [root< at >ns1]# route --inet6 Kernel IPv6 routing table Destination Flags Metric Ref Use Iface ::1/128 U 0 18182 3 lo 2001:0:4136:e388:0:f1e0:b951:a3a3/128 UC 0 1 0 teredo 2001:0:4136:e388:0:f4f5:ab86:a82f/128 UC 0 1 0 teredo 2001:0:4136:e388:0:f685:ac63:c890/128 UC 0 1 0 teredo 2001:0:4136:e388:0:f812:e7be:a292/128 UC 0 1 0 teredo 2001:0:4136:e388:0:fb25:ab66:ac3c/128 UC 0 1 0 teredo .............. I wonder why the Miredo implementation adds a new entry into the routing table per each Teredo packet received. This makes me to modify some values of sysctls on /proc/sys/net/ipv6/route/* in order to increase the IPv6 routing table and the garbage collection behavior in order to avoid that other IPv6 routes in the routing table be lost. In my view adding one entry into the routing table per Teredo packet received is clearly not scalable because the resources (memory, etc.) on the server are limited and we foresee that Teredo traffic continues increasing over the time as more and more Microsoft Vista OS is deployed. Would it be possible that Miredo adds only one route (2001::/32) into the routing table, rather than hundreds or even thousands of them? Regards Miguel ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.