Forum - Problems with AICCU on Raspbian 3.12.25+ :: SixXS

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Wednesday, 17 September 2014 10:11:17

When installing AICCU (apt-get install aiccu) on my Raspberry Pi (B model) running Raspbian 3.12.25+, my WLAN stops working. The external IP address is taken over by the SIT0 interface and the IPv6 interface never comes up -- obviously because AICCU cannot get in contact with the TIC server. /etc/network/interfaces contains the following lines:

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet static
        address 192.168.1.99
        netmask 255.255.255.0
        gateway 192.168.1.1

/etc/aiccu.conf looks like this:

# AICCU Configuration

# Login information (defaults: none)
#username <your nichandle/username>
username XXXX-SIXXS
#password <your password>
password XXXXXXXX

# Protocol and server to use for setting up the tunnel (defaults: none)
#protocol <tic|tsp|l2tp>
protocol tic
#server <server to use>
server tic.sixxs.net

# Interface names to use (default: aiccu)
# ipv6_interface is the name of the interface that will be used as a tunnel interface.
# On *BSD the ipv6_interface should be set to gifX (eg gif0) for proto-41 tunnels
# or tunX (eg tun0) for AYIYA tunnels.
#ipv6_interface sixxs
ipv6_interface ip6-0

# The tunnel_id to use (default: none)
# (only required when there are multiple tunnels in the list)
#tunnel_id Txxxx
tunnel_id TXXXXXX

# Be verbose? (default: false)
verbose false

# Daemonize? (default: true)
# Set to false if you want to see any output
# When true output goes to syslog
#
# WARNING: never run AICCU from DaemonTools or a similar automated
# 'restart' tool/script. When AICCU does not start, it has a reason
# not to start which it gives on either the stdout or in the (sys)log
# file. The TIC server *will* automatically disable accounts which
# are detected to run in this mode.
#
daemonize true

# Automatic Login and Tunnel activation?
automatic true

# Require TLS?
# When set to true, if TLS is not supported on the server
# the TIC transaction will fail.
# When set to false, it will try a starttls, when that is
# not supported it will continue.
# In any case if AICCU is build with TLS support it will
# try to do a 'starttls' to the TIC server to see if that
# is supported.
requiretls false

# PID File
#pidfile /var/run/aiccu.pid

# Add a default route (default: true)
#defaultroute true

# Script to run after setting up the interfaces (default: none)
#setupscript /usr/local/etc/aiccu-subnets.sh

# Make heartbeats (default true)
# In general you don't want to turn this off
# Of course only applies to AYIYA and heartbeat tunnels not to static ones
#makebeats true

# Don't configure anything (default: false)
#noconfigure true

# Behind NAT (default: false)
# Notify the user that a NAT-kind network is detected
#behindnat true

# Local IPv4 Override (default: none)
# Overrides the IPv4 parameter received from TIC
# This allows one to configure a NAT into "DMZ" mode and then
# forwarding the proto-41 packets to an internal host.
# 
# This is only needed for static proto-41 tunnels!
# AYIYA and heartbeat tunnels don't require this.
#local_ipv4_override

The configuration file is exactly the same as the one I use on an Xubuntu laptop without any problems. And yes, the laptop uses WLAN too. Oh, and I have tried to set verbose true I get the following lines in /var/log/daemon.log and /var/log/syslog:

Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: ifplugd 0.28 initializing.
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Using interface sit0/00:00:00:00:00:00
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Using detection mode: IFF_RUNNING
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Initialization complete, link beat detected.
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Executing '/etc/ifplugd/ifplugd.action sit0 up'.
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: client: OK
Sep 15 12:40:26 Machine wpa_supplicant[1793]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: client: Ignoring unknown interface sit0=sit0.
Sep 15 12:40:26 Machine ifplugd(wlan0)[1753]: Link beat lost.
Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Program executed successfully.

Any ideas?

Problems with AICCU on Raspbian 3.12.25+

Jeroen Massar SixXS Staff

on Wednesday, 17 September 2014 10:19:04

Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Executing '/etc/ifplugd/ifplugd.action sit0 up'.

You might want to check that script. What is really strange though is that 'sit0' gets involved at all. Your aiccu.conf has "ipv6_interface ip6-0" (maybe that '-' / dash in there confuses things?) hence AICCU will just touch that, sit0 should not be touched at all; actually, sit0 is for protocol 41 tunnels (static / heartbeat). As you have a RFC1918 address on your interface though you need AYIYA, which requires a tun/tap interface. Hence sit0 will not be involved at all.

I get the following lines in /var/log/daemon.log and /var/log/syslog:

When do you get those lines? How do you start AICCU? What magic is in the initscript? Why is there no output mentioning AICCU in anyway?

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Wednesday, 17 September 2014 11:27:51

Jeroen Massar wrote:

> Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Executing '/etc/ifplugd/ifplugd.action sit0 up'. You might want to check that script.

It basically runs 'ifup sit0', which should not do anything since sit0 is not mentioned in /etc/network/interfaces.

What is really strange though is that 'sit0' gets involved at all.

I agree.

Your aiccu.conf has "ipv6_interface ip6-0" (maybe that '-' / dash in there confuses things?) hence AICCU will just touch that, sit0 should not be touched at all; actually, sit0 is for protocol 41 tunnels (static / heartbeat). As you have a RFC1918 address on your interface though you need AYIYA, which requires a tun/tap interface. Hence sit0 will not be involved at all.

I'll try without but it did no harm on my Ubuntu laptop.

> I get the following lines in /var/log/daemon.log and /var/log/syslog: When do you get those lines? How do you start AICCU?

I get the lines when trying to install AICCU, so it tries to start it automatically at that time.

What magic is in the initscript?

What do you mean?

Why is there no output mentioning AICCU in anyway?

Beats me!

Problems with AICCU on Raspbian 3.12.25+

Jeroen Massar SixXS Staff

on Wednesday, 17 September 2014 11:42:15

Sep 15 12:40:26 Machine ifplugd(sit0)[2844]: Executing '/etc/ifplugd/ifplugd.action sit0 up'.

You might want to check that script.

It basically runs 'ifup sit0', which should not do anything since sit0 is not mentioned in /etc/network/interfaces.

You might want to check what actually references sit0.

I get the lines when trying to install AICCU, so it tries to start it automatically at that time.

Seems some scripts on your host are, well, odd.

What magic is in the initscript?

What do you mean?

Some "distributions" seem to think they are smarter than the author of AICCU and modify the init scripts to do all kind of magic things. As the magic is different, it really depends on the version you have. The SixXS version just starts AICCU, nothing more nothing less, and thus no such oddities would exist. I think something is going wrong completely though, as there is no mention of AICCU anywhere in your logs.

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Tuesday, 07 April 2015 02:39:31

Torben Rybner wrote:

Did you ever solve this? I see a very similar problem. I wouldn't say 'the external IP address is taken over by the SIT0 interface". My logs show that the sixxs interface comes up, at which point I assume the SIT0 interface is assigned an IPv6 "link" level address based on the IPv4 address, but I believe that's irrelevant to the actual problem. Then wpa_supplicant gets CTRL-EVENT-DISCONNECTED on the wlan0 interface, and my tunnel is setup but there's no IPv4 carrier to tunnel through.

sit0      Link encap:IPv6-in-IPv4  
          inet6 addr: ::192.168.1.132/96 Scope:Compat
          inet6 addr: ::127.0.0.1/96 Scope:Unknown
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sixxs     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::4830:1100:321:2/64 Scope:Link
          inet6 addr: 2001:4830:1100:321::2/64 Scope:Global
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1280  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 B)  TX bytes:304 (304.0 B)

wlan0     Link encap:Ethernet  HWaddr e8:4e:06:25:d6:6b  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:1086 errors:0 dropped:665 overruns:0 frame:0
          TX packets:1424 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:138348 (135.1 KiB)  TX bytes:1563051 (1.4 MiB)

My Raspbian is 3.18.7-v7, and I have a Debian sid laptop on which I used exactly the same /etc/aiccu.conf successfully. The big difference, I think, is that the laptop is running network-manager and the Pi is running wicd. Log:

Apr  6 21:45:30 raspberrypi ifplugd(wlan0)[1657]: Link beat detected.
Apr  6 21:45:30 raspberrypi ifplugd(wlan0)[1657]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'.
Apr  6 21:45:30 raspberrypi ifplugd(wlan0)[1657]: client: /sbin/ifup: interface wlan0 already configured
Apr  6 21:45:30 raspberrypi ifplugd(wlan0)[1657]: Program executed successfully.
Apr  6 21:45:32 raspberrypi ntpd[2596]: Listen normally on 8 wlan0 192.168.1.132 UDP 123
Apr  6 21:45:32 raspberrypi ntpd[2596]: Listen normally on 9 wlan0 fe80::ea4e:6ff:fe25:d66b UDP 123
Apr  6 21:45:32 raspberrypi ntpd[2596]: peers refreshed
Apr  6 21:45:34 raspberrypi ntpd_intres[3008]: DNS 0.debian.pool.ntp.org -> 173.243.192.18
Apr  6 22:47:26 raspberrypi aiccu[5775]: Successfully retrieved tunnel information for T164937
Apr  6 22:47:27 raspberrypi aiccu[5784]: AICCU running as PID 5784
Apr  6 22:47:27 raspberrypi ifplugd(sixxs)[5807]: ifplugd 0.28 initializing.
Apr  6 22:47:27 raspberrypi ifplugd(sixxs)[5807]: Using interface sixxs/00:00:00:00:00:00 with driver <tun> (version: 1.6)
Apr  6 22:47:27 raspberrypi ifplugd(sixxs)[5807]: Using detection mode: SIOCETHTOOL
Apr  6 22:47:27 raspberrypi ifplugd(sixxs)[5807]: Initialization complete, link beat detected.
Apr  6 22:47:27 raspberrypi aiccu[5784]: [AYIYA-start] : Anything in Anything (draft-02)
Apr  6 22:47:27 raspberrypi aiccu[5784]: [AYIYA-tun->tundev] : (Socket to TUN) started
Apr  6 22:47:27 raspberrypi ifplugd(sixxs)[5807]: Executing '/etc/ifplugd/ifplugd.action sixxs up'.
Apr  6 22:47:28 raspberrypi wpa_supplicant[3720]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
Apr  6 22:47:28 raspberrypi ifplugd(sixxs)[5807]: client: OK
Apr  6 22:47:28 raspberrypi kernel: [ 4143.468682] rtw_wx_set_mlme
Apr  6 22:47:28 raspberrypi kernel: [ 4143.468705] rtw_wx_set_mlme, cmd=0, reason=3
Apr  6 22:47:28 raspberrypi wpa_action: WPA_IFACE=wlan0 WPA_ACTION=DISCONNECTED
Apr  6 22:47:28 raspberrypi ifplugd(sixxs)[5807]: client: Ignoring unknown interface sixxs=sixxs.
Apr  6 22:47:28 raspberrypi wpa_action: WPA_ID=0 WPA_ID_STR= WPA_CTRL_DIR=/var/run/wpa_supplicant
Apr  6 22:47:28 raspberrypi wpa_action: ifdown wlan0
Apr  6 22:47:28 raspberrypi ifplugd(wlan0)[1657]: Link beat lost.
Apr  6 22:47:28 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2
Apr  6 22:47:28 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium.
Apr  6 22:47:28 raspberrypi dhclient: All rights reserved.
Apr  6 22:47:28 raspberrypi dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr  6 22:47:28 raspberrypi dhclient: 
Apr  6 22:47:28 raspberrypi ifplugd(sixxs)[5807]: Program executed successfully.
Apr  6 22:47:28 raspberrypi dhclient: Listening on LPF/wlan0/e8:4e:06:25:d6:6b
Apr  6 22:47:28 raspberrypi dhclient: Sending on   LPF/wlan0/e8:4e:06:25:d6:6b
Apr  6 22:47:28 raspberrypi dhclient: Sending on   Socket/fallback
Apr  6 22:47:29 raspberrypi dhclient: DHCPRELEASE on wlan0 to 192.168.1.1 port 67
Apr  6 22:47:30 raspberrypi wpa_action: removing sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid
Apr  6 22:47:30 raspberrypi kernel: [ 4145.593609] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr  6 22:47:31 raspberrypi ntpd[2596]: Listen normally on 10 sixxs fe80::4830:1100:321:2 UDP 123
Apr  6 22:47:31 raspberrypi ntpd[2596]: Listen normally on 11 sixxs 2001:4830:1100:321::2 UDP 123
Apr  6 22:47:31 raspberrypi ntpd[2596]: Deleting interface #9 wlan0, fe80::ea4e:6ff:fe25:d66b#123, interface stats: received=0, sent=0, dropped=0, active_time=3690 secs
Apr  6 22:47:31 raspberrypi ntpd[2596]: Deleting interface #8 wlan0, 192.168.1.132#123, interface stats: received=203, sent=216, dropped=0, active_time=3690 secs
Apr  6 22:47:31 raspberrypi ntpd[2596]: 162.219.6.68 interface 192.168.1.132 -> (none)
Apr  6 22:47:31 raspberrypi ntpd[2596]: peers refreshed
Apr  6 22:47:38 raspberrypi ifplugd(wlan0)[1657]: Executing '/etc/ifplugd/ifplugd.action wlan0 down'.
Apr  6 22:47:38 raspberrypi ifplugd(wlan0)[1657]: client: /sbin/ifdown: interface wlan0 not configured
Apr  6 22:47:38 raspberrypi ifplugd(wlan0)[1657]: Program executed successfully.
Apr  6 22:48:27 raspberrypi aiccu[5784]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Apr  6 22:49:27 raspberrypi aiccu[5784]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Apr  6 22:50:08 raspberrypi ifplugd(sixxs)[5807]: Link beat lost.
Apr  6 22:50:08 raspberrypi ifplugd(sixxs)[5807]: Exiting.
Apr  6 22:50:09 raspberrypi ntpd[2596]: Deleting interface #11 sixxs, 2001:4830:1100:321::2#123, interface stats: received=0, sent=0, dropped=0, active_time=158 secs

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Tuesday, 07 April 2015 02:43:01

btw, the big difference between my config and yours is that my Pi is natted. So aiccu.conf includes: behindnat true Also, I use the default: ipv6_interface sixxs

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Tuesday, 07 April 2015 03:56:58

Found the problem. It's the wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf in /etc/network/interfaces. /etc/ifplugd/action.d/action_wpa says

# If an ifplugd managed interface is brought up, disconnect any
# wpa-roam managed interfaces so that only one "roaming" interface
# remains active on the system.

Oops. In my case, it involved removing any reference to wlan0 in /etc/network/interfaces, purging and reinstalling wicd (until I did that, wicd didn't seem to see the interface). In Torben's case, with a static IP, he might be able to simply change wpa_roam to wpa_conf.

Problems with AICCU on Raspbian 3.12.25+

Jeroen Massar SixXS Staff

on Tuesday, 07 April 2015 09:25:05

So aiccu.conf includes:

behindnat true

That option does exactly nothing on non-Windows GUI platforms. The only thing it used to do in the very old Windows GUI edition of AICCU is warn the user that they are behind a NAT and that they where trying a proto-41 based tunnel, which does not work behind a NAT. For working behind NAT there are two options: AYIYA (easiest) or proto-41/heartbeat but then you have configure the NAT box to appoint the device as the DMZ host (which does not always fully happily work).

Problems with AICCU on Raspbian 3.12.25+

Jeroen Massar SixXS Staff

on Tuesday, 07 April 2015 09:19:14

What exact command did you use to see this output:

sit0 Link encap:IPv6-in-IPv4

inet6 addr: ::192.168.1.132/96 Scope:Compat

inet6 addr: ::127.0.0.1/96 Scope:Unknown

Noting that the sit0 interface always shows the IPv6-compat addresses of the IPv4 addresses on all other interfaces, thus that 192.168.1.132/24 address is configured on another interface. The important bit in your log is:

Apr 6 22:47:28 raspberrypi kernel: [ 4143.468705] rtw_wx_set_mlme, cmd=0, reason=3

Googling for "rtw_wx_set_mlme, cmd=0, reason=3" shows that various people report disconnects with RTL8188CUS based wifi dongles (TP-Link makes a variety of them). An 'lsmod |grep 8192cu' will show if you are also using that driver. As it concerns a Raspberry Pi, what kind of power are you feeding to it. Might just be that the actual sending of packets causes the device to suck up too much power and get disconnected. Thus check the power ratings of the Pi, the thing you feed it power with etc. Connecting plugged devices to a powered USB hub is typically a good idea (and the reason that in the end a working Pi with some devices actually still costs over a 100 bucks..)

Problems with AICCU on Raspbian 3.12.25+

Shadow Hawkins on Tuesday, 07 April 2015 12:02:03

Jeroen Massar wrote:

What exact command did you use to see this output:

sit0 Link encap:IPv6-in-IPv4

inet6 addr: ::192.168.1.132/96 Scope:Compat

inet6 addr: ::127.0.0.1/96 Scope:Unknown

Apr 6 22:47:28 raspberrypi kernel: [ 4143.468705] rtw_wx_set_mlme, cmd=0, reason=3

No, really, as I said, I solved the problem. Power is nothing to do with it. The Debian/Raspbian wpa_supplicant package installs /etc/ifplugd/action.d/action_wpa, and that explicitly takes down any device with "wpa-roam" in /etc/network/interfaceswhich various sources told me I needed when I initially set up the Pi as soon as any other interface (in this case sixxs) comes up. I had to remove and reinstall wicd, as there was clearly something wrong with that config, but after that it worked perfectly. fwiw, I am using 8192cu, and the status info came from ifconfig.

Please note Posting is only allowed when you are logged in.