|
AICCU on FreeBSD 6.3-Stable
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 29 January 2008 13:49:34
Hi,
I upgrade in the last days my FreeBSD to the new RELANG_6 version.
But after this it seems the aiccu isn't working anymore.
If I try to start the tunnel with:
/usr/local/etc/rc.d/sixxs-aiccu start
I cannot see any message on screen or in dmesg, just nothing.
Aaaaaah I reinstalled now aiccu and the port killed my config file (overwritten it with a sample file). That should be really fixed in the port!
AICCU on FreeBSD 6.3-Stable
Shadow Hawkins on Tuesday, 29 January 2008 14:10:29
so after restoring the config file from a backup I did more testing.
Started no aiccu again and get the following message:
Tunnel Information for T10829:
POP Id : demuc02
IPv6 Local : 2001:a60:f000:45::2/64
IPv6 Remote : 2001:a60:f000:45::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
and ifconfig says:
tun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
inet6 fe80::219:66ff:fe35:2416%tun3 prefixlen 64 scopeid 0x13
inet6 fe80::860:f000:45:2%tun3 prefixlen 64 scopeid 0x13
inet6 2001:a60:f000:45::2 --> 2001:a60:f000:45::1 prefixlen 128
Opened by PID 11768
config file is:
username xxxx
password xxxx
ipv6_interface tun3
tunnel_id T10829
verbose true
daemonize true
automatic true
requiretls false
defaultroute true
but if i try now to ping all connections from the server are reseted and I got the message from ping6:
PING6(56=40+8+8 bytes) 2001:a60:f035:2::1 --> 2a01:138:100:1:219:d1ff:fe6a:ef49
ping6: sendmsg: No buffer space available
ping6: wrote fechner.net 16 chars, ret=-1
Has anyone an idea where the problem can be?
Thx
Matthias
AICCU on FreeBSD 6.3-Stable
See the "Reporting Problems" checklist and go through it. Most likely you will either have:
- weird/leftover routing entries
- some nice kernel issue which requires a quick reboot or sysctl buffer change.
The above information doesn't tell a thing though.
AICCU on FreeBSD 6.3-Stable
Shadow Hawkins on Tuesday, 29 January 2008 15:06:05
ah ok, i check now the reporting problem checklist and while doing this I found the error.
The IPv6 default route points to tun0.
But i set on the config file the aiccu should set the default route why is aiccu not doing this?
What I did now manually was:
route -inet6 delete default
route add -inet6 default -iface tun3
AICCU on FreeBSD 6.3-Stable
There is nothing like tun0 hardcoded in aiccu, but the default is to use tun0 though and as you ran it with the default config, maybe it used that.
AICCU on FreeBSD 6.3-Stable
Shadow Hawkins on Tuesday, 29 January 2008 15:27:16
hm doesn't make sense, my config is like you see above:
ipv6_interface tun3
defaultroute true
so should aiccu not set the default route to tun3 in that case?
AICCU on FreeBSD 6.3-Stable
It doesn't use the interface name, it uses: route add -inet6 default $pop
This should always go correctly, unless you have the $pop/64 or more specific pointing somewhere else.
AICCU on FreeBSD 6.3-Stable
Shadow Hawkins on Tuesday, 29 January 2008 17:50:18
thx for that info that works too.
But can you please fix or at least inform to the responsible person that the aiccu port on freebsd should not overwrite the file /usr/local/etc/aiccu.conf.
The port system can install a file like /usr/local/etc/aiccu.conf.sample but never a .conf file.
Thx a lot for your help.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 29 January 2008 14:23:54
Posting is only allowed when you are