|
Ticket ID: SIXXS #473635 Ticket Status: Resolved PoP: nlede01 - BIT BV (Ede)
User ticket: Tunnel (ayiya) not working
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Monday, 22 January 2007 15:27:23
# /etc/init.d/aiccu start
Starting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)....
# tcpdump -ni ppp0 host 193.109.122.244
tcpdump: listening on ppp0
15:09:45.676250 84.87.123.125.1069 > 193.109.122.244.5072: udp 92 (DF)
15:09:45.707709 84.87.123.125.1069 > 193.109.122.244.5072: udp 44 (DF)
15:09:45.708306 84.87.123.125.1069 > 193.109.122.244.5072: udp 44 (DF)
15:09:45.708393 84.87.123.125.1069 > 193.109.122.244.5072: udp 44 (DF)
15:09:49.677113 84.87.123.125.1069 > 193.109.122.244.5072: udp 92 (DF)
15:09:53.677392 84.87.123.125.1069 > 193.109.122.244.5072: udp 92 (DF)
aiccu test succeeds, until test 6, can't reach the tunnel endpoint within ipv6.
NAT masquerades all, sniff was on the external interface on the NAT box. No firewall for UDP traffic.
Relevant snip from syslog:
Jan 22 14:52:09 server aiccu: Succesfully retrieved tunnel information for T10685
Jan 22 14:52:09 server aiccu: AICCU running as PID 9938
Jan 22 14:52:09 server aiccu: [AYIYA-start] : Anything in Anything (draft-02)
Jan 22 14:52:09 server kernel: sixxs: Disabled Privacy Extensions
Jan 22 14:52:09 server aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started
Jan 22 14:52:18 server kernel: sixxs: no IPv6 routers present
In verbose mode it shows nothing else that's relevant, other than protocol log of tic, which works as the settings are correct.
type = ayiya, which is correct. 2001:7b8:2ff:158::1 and ::2, which is correct, MTU 1280, also correct. POP 193.109.122.244, resolves to nlede01.sixxs.net, also correct.
Please advise.
Regards,
Wilco
[Admin subject change, prefixed with "User ticket"]
Tunnel (ayiya) not working
The PoP sees those AYIYA packets coming in from the IP you mention.
It even configured the interface to be up:
64 bytes from 2001:7b8:2ff:158::1: icmp_seq=1 ttl=60 time=3.57 ms
As such on the PoP side everything is fine. It is also sending out packets.
And here is your answer:
15:24:13.716394 IP 193.109.122.243.5072 > 84.87.123.125.1074: UDP, length 148
15:24:13.732281 IP 84.87.123.125 > 193.109.122.243: ICMP 84.87.123.125 udp port 1074 unreachable, length 184
Check the configuration of your firewall, it is rejecting packets.
As you can sniff packets on the machine with pp0, why don't you terminate the IPv6 tunnel on that machine?
Tunnel (ayiya) not working
Shadow Hawkins on Tuesday, 23 January 2007 15:26:03
Because IPv6 doesn't work on that machine, and compiling a new kernel takes years.. (will replace that machine once my D-Link Horstbox arrives)
Good point though. I had not seen these packets in my tcpdump (not even a reply from nlede01), but strangely, now I do see them very continuously.
Guess I'll end it on the other box, because the UDP (source) port seems to be incremental and forwarding 1024:65536 is not a good idea (as there's DNS and NAT on the other box).
Thanks for your help,
Wilco
State change: confirmed
The state of this ticket has been changed to confirmed
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Monday, 22 January 2007 15:26:13
Posting is only allowed when you are