News: This forum is now permanently frozen.
Pages: [1]
Topic: 1.3b15, IPv6, aiccu  (Read 4376 times)
« on: November 04, 2008, 12:22:04 »
WalterH *
Posts: 1

Hi all,

i have some issues running IPv6 (aiccu tunnel) with 1.3b15. A few days ago i switched from my (working!) Debian ipv6router to M0n0wall as an AICCU router.

Oh, i use old WRAP hardware, in case it matters.

- i enabled v6 in "advanced" setup

- i set "aiccu mode" in the WAN config (static v4) and entered my tunnel parameters

- i set "static" in the LAN interface, entered a v6 address out of my assigned network and assigned a /64 subnet.

- i entered v6 rules in the WAN and LAN rules to let everything pass for testing!

Ok, here's the weird thing: "ifconfig -a" (via exec.php) gives me:

tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
inet6 fe80::20d:b9ff:fe01:92b4%tun0 prefixlen 64 scopeid 0x6
inet6 fe80::860:f000:78:2%tun0 prefixlen 64 scopeid 0x6
inet6 <local v6 tunnel end> --> <remote v6 tunnel end> prefixlen 128
Opened by PID 117

ID 117 is:

root     117  0.0  1.1  1964  1252  ??  Ss   11:01AM   0:00.91 /usr/local/sbin/sixxs-aiccu start /var/etc/aiccu.conf

Fine so far. Tunnel seems to be up! I seem to have connectivity:

desktop$ ping6
PING 56 data bytes
64 bytes from 2001:4860:0:1001::68: icmp_seq=1 ttl=59 time=25.1 ms
64 bytes from 2001:4860:0:1001::68: icmp_seq=2 ttl=59 time=30.4 ms

But when i open my profile, i see the tunnel as "up", too, but the tunnel stats (delay, ...) are all completely empty! Not 0, but no line at all.

/var/etc/aiccu.conf contains:

username <my username>
password <my password>
tunnel_id <my tunnel id>
ipv6_interface gif0
daemonize true
automatic true
requiretls false
pidfile /var/run/
defaultroute true

So what's the deal with "gif0"? I don't have a "gif0" interface, only a "tun0".

Similarily, the "ipfstat -6i" output contains only "gif0" rules, no "tun0".

Naturally, M0n0wall now blocks valid v6 traffic:

11:53:01.161981 tun0 @0:18 b fe80::860:f000:78:1 -> ff02::d PR pim len 40 (88) IN low-ttl
11:52:31.160675 tun0 @0:18 b fe80::860:f000:78:1 -> ff02::d PR pim len 40 (88) IN low-ttl
11:52:01.166904 tun0 @0:18 b fe80::860:f000:78:1 -> ff02::d PR pim len 40 (88) IN low-ttl
11:51:47.422069 tun0 @0:18 b fe80::860:f000:78:1 -> ff02::1 PR icmpv6 len 48 76 icmpv6 groupmemberquery/ipv6 IN

Link-local multicasts should at least reach the local tunnel endpoint. That could explain why my Sixxs tunnel stats are empty...

Routing on the M0n0wall (netstat -rn) seems ok: I have the correct default gateway at interface "tun0" and all subnets (global, link-local, multicast, etc) are at their respective interfaces, just as you would expect.

I'm kind of stuck now, but i begin to think that the "tun0" vs "gif0" issue is a bug. I'm quite unsure, though, because i seem to be the only one to have this issue. Let's hope, the "bug" is not between my ears. Wink

« Last Edit: November 04, 2008, 13:29:38 by WalterH »
« Reply #1 on: November 19, 2008, 02:19:49 »
Manuel Kasper
Posts: 364

You've probably got your SixXS tunnel set to AYIYA mode. This is not supported at this time; you need to set it to heartbeat mode (this is explained on the WAN interface setup page, IIRC).
Pages: [1]
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines