SixXS::Sunset 2017-06-06

FreeBSD aiccu package
[fr] Shadow Hawkins on Tuesday, 16 January 2007 22:47:55
Hi all, I am trying to install aiccu from the FreeBSD ports but unfortunetly the source file is not available anymore. Is there any way to get SixXS working on FreeBSD ? Thanks in advance, Regards, -- Alexis
FreeBSD aiccu package
[ch] Pim van Pelt SixXS Staff on Tuesday, 16 January 2007 23:05:23
in www.sixxs.net/tools/aiccu there's a link to the current version (20070115). It contains a freebsd dir. In that freebsd dir, there's a readme. That should help you figure it out. We are currently waiting for a freebsd ports committer to help us out. This might take some time.
FreeBSD aiccu package
[fr] Shadow Hawkins on Tuesday, 16 January 2007 23:29:23
Hi, thanks for your quick reply. I did download the latest source tarball. unfortunetly I cannot find any readme in the freebsd directory. this is what I have: [root@taro ~/aiccu/freebsd]# ls -l total 8 -rw-r--r-- 1 naota munin 1499 Jan 7 19:32 Makefile drwxr-xr-x 2 seb munin 512 Jan 7 22:09 files -rw-r--r-- 1 seb munin 999 Apr 10 2005 pkg-descr -rw-r--r-- 1 seb munin 127 Dec 21 15:25 pkg-plist [root@taro ~/aiccu/freebsd/files]# ls -l total 2 -rw-r--r-- 1 seb munin 646 Dec 21 15:23 sixxs-aiccu.in Did I download the wrong file ? ( aiccu_20070115.tar.gz ) Regards, - Alexis
FreeBSD aiccu package
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 January 2007 00:58:32
Nope, and there is no readme in that directory, there is one under doc though. But there is a little problem with the Makefile. Version numbers where not updated, thus download: Makefile Small FreeBSD build howto:
# cd /tmp/ # mkdir bla # cd bla # wget http://www.sixxs.net/archive/sixxs/unix/aiccu_current.tar.gz # tar -zxvf aiccu_current.tar.gz # cd aiccu/freebsd # wget -O Makefile /archive/sixxs/aiccu/unix/aiccu_20070115.freebsd.Makefile # make install
and you have an installed package ;) (That Makefile which is wgetted is to fix 20070115 :)
FreeBSD aiccu package
[it] Shadow Hawkins on Wednesday, 17 January 2007 10:28:54
Hello Guys, i have the same problem when replacing the old sixxs-aiccu package with this last one (AICCU 2007.01.15-console-kame by Jeroen Massar). Tunnel come up but no route to host and sixxs-aiccu test fail only on the last test (ptp ping6) ping6 2001:1418:100:154::1 PING6(56=40+8+8 bytes) 2001:1418:100:154::2 --> 2001:1418:100:154::1 ping6: sendmsg: No route to host Netstat output Internet6: Destination Gateway Flags Netif Expire default 2001:1418:100:154::1 UGS gif2 ::1 ::1 UHL lo0 2001:1418:100:154::2 link#5 UHL lo0 Does anybody suffer the same behaviour? thank simone
FreeBSD aiccu package
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 January 2007 11:41:54
Please read "Reporting Problems" and show more information. especially 'ifconfig -a' can be useful here, which is on that list.
FreeBSD aiccu package
[it] Shadow Hawkins on Wednesday, 17 January 2007 12:26:16
Jeroen, sorry reactive# ifconfig -a vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:40:63:c0:8b:53 media: Ethernet autoselect (100baseTX <full-duplex>) status: active lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 192.168.1.15 netmask 0xffffffff tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492 inet 151.48.71.28 --> 151.6.149.65 netmask 0xffffffff Opened by PID 34915 tun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet 172.16.1.1 --> 172.16.1.2 netmask 0xffffffff Opened by PID 13824 gif2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 tunnel inet 151.48.71.28 --> 213.254.12.34 inet6 2001:1418:100:154::2 --> 2001:1418:100:154::1 prefixlen 128 tun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet 172.16.1.17 --> 172.16.1.18 netmask 0xffffffff Opened by PID 68810 Hope this can help Best Regards, Simone
FreeBSD aiccu package
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 January 2007 12:46:34
There doesn't seem to be anything wrong with the configuration of gif2, though it doesn't show linklocal addresses, but the others don't do that either. Only assumption I can make is that, due to the other tunnels you have there is something odd happening, but those things are not easy to find. Try running a simpler configuration and read the "reporting problems" section and verify everything.
FreeBSD aiccu package
[it] Shadow Hawkins on Wednesday, 17 January 2007 13:33:46
Jeroen, thanks for the quick reply and for the support. I'm gonna check out the section you told me to read and try to find the solution. All i did is to upgrade the sixxs-aiccu client on my BSD box and this happened in the same day (today) i also performed upgrade from FreeBSD 6.1 to 6.2. Hope, checking around the net, to find someone that suffer the same problem. Thanks again. Simone
FreeBSD aiccu package
[it] Shadow Hawkins on Wednesday, 17 January 2007 13:36:14
Also, checking around this forum i found that other guys from Italy suffer the same strange behaviour when upgrading the sixxs-aiccu client as you can see in this thread. https://noc.sixxs.net/forum/?msg=setup-470198 I'm going to follow that thread and see if someone pinpoint the problem. Thanks simone
FreeBSD aiccu package
[fr] Shadow Hawkins on Wednesday, 17 January 2007 11:47:45
Hi Jeroen/all, thanks for the reply, this now works great. Unforntunetly, I still have an issue with my setup. Aiccu works great and sets up the gif0 interface correctly: # ifconfig gif0 gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 tunnel inet 88.191.39.224 --> 212.100.184.146 inet6 fe80::240:63ff:fee8:c8c%gif0 prefixlen 64 scopeid 0x3 inet6 2001:6f8:202:162::2 --> 2001:6f8:202:162::1 prefixlen 128 as well as the default router: # netstat -rn Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 => default 2001:6f8:202:162::1 UGS gif0 ::1 ::1 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRS lo0 2001:6f8:202:162::1 link#3 UHL gif0 2001:6f8:202:162::2 link#3 UHL lo0 Unfortunetly, I cannot ping my default router: # ping6 2001:6f8:202:162::1 PING6(56=40+8+8 bytes) 2001:6f8:202:162::2 --> 2001:6f8:202:162::1 ping6: sendmsg: Permission denied ping6: wrote 2001:6f8:202:162::1 16 chars, ret=-1 ping6: sendmsg: Permission denied ping6: wrote 2001:6f8:202:162::1 16 chars, ret=-1 and neither can I ping my own IPV6: [root@taro /usr/local/etc]# ping6 2001:6f8:202:162::2 PING6(56=40+8+8 bytes) 2001:6f8:202:162::2 --> 2001:6f8:202:162::2 ^C --- 2001:6f8:202:162::2 ping6 statistics --- 7 packets transmitted, 0 packets received, 100.0% packet loss my ip6fw is compeltly open (for now ;) ) so now worries here: # ip6fw l 00100 allow ipv6 from any to any I created a static IPv4 tunnel and this is my configuration: PoP Name bebru01 PoP Location Brussels, Belgium PoP IPv4 212.100.184.146 Your Location Paris, France Your IPv4 88.191.39.224 IPv6 Prefix 2001:6f8:202:162::1/64 PoP IPv6 2001:6f8:202:162::1 Your IPv6 2001:6f8:202:162::2 Last Dead 2007-01-16 22:47:46 State Enabled Any ideas on what could be wrong here ? Many thanks Regards, -- Alexis
FreeBSD aiccu package
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 January 2007 11:53:19
PING6(56=40+8+8 bytes) 2001:6f8:202:162::2 --> 2001:6f8:202:162::1
ping6: sendmsg: Permission denied
That clearly says permission denied, check your firewall settings. Both IPv6 and IPv4. I would not be surprised if you are blocking protocol 41.
FreeBSD aiccu package
[fr] Shadow Hawkins on Wednesday, 17 January 2007 11:56:41
Good one :) thanks for that. works perfect now! -- Alexis
FreeBSD aiccu package
[fr] Shadow Hawkins on Wednesday, 17 January 2007 12:59:12
Actually, I was looking more into that. What I did to make it work is to open both ipv4 and ipv6 firewalls. Which would be the rules to put in place for this to work on a closed firewall? Many thanks Regards, -- Alexis
FreeBSD aiccu package
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 January 2007 13:05:49
What about checking the FAQ: I have a firewall, what ports/protocols are used??
FreeBSD aiccu package
[fr] Shadow Hawkins on Wednesday, 17 January 2007 17:28:31
Hi Jeroen, many thanks for the help so far, I have setup my firewall to accept Protocol 41 (which I beleive is ipv6 under FreeBSD) and now I am able to ping my local address but not the pop address. Could you check my ipfw rule ? 01175 allow ip6 from any to any 01181 allow ipv6-route from any to any 01187 allow ipv6-frag from any to any and 40020 allow ipv6-icmp from any to any 03050 allow tcp from any to any out it seems my ipfw is still blocking the tunnel packets. A configuration example would be very much appreciated! Many thanks Regards, -- Alexis

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker