|
aiccu startup error (ioctl: No buffer space available)
![[us]](/s/countries/us.gif) Carmen Sandiego on Saturday, 21 February 2009 21:31:17
Trying to set up a static tunnel on a dedicated machine. This is a synopsis of the error I'm getting when I try to start aiccu. Any ideas? I'm using sit0 as the tunneling interface.
--Brian
[root@xenotime src]# /usr/local/bin/aiccu start
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.16.49-xen"
...
Succesfully retrieved tunnel information for T19893
sock_printf() : "QUIT This is not our farewell"
Tunnel Information for T19893:
POP Id : uschi02
IPv6 Local : 2001:xxxx:x:xxx::2/64
IPv6 Remote : 2001:xxxx:x:xxx::1/64
Tunnel Type : 6in4-static
Adminstate : enabled
Userstate : enabled
ioctl: No buffer space available
ttl != 0 and noptmudisc are incompatible
aiccu startup error (ioctl: No buffer space available)
Carmen Sandiego on Saturday, 21 February 2009 21:42:39
I don't know if this helps, but here is what my sit0 interface looks like prior to aiccu aborting:
sit0 Link encap:IPv6-in-IPv4
inet6 addr: 2001:xxxx:x:xxx::2/64 Scope:Global
inet6 addr: ::xx.xx.xx.xx/96 Scope:Compat
inet6 addr: ::127.0.0.1/96 Scope:Unknown
UP RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:8 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
pinging the :2 interface is successful; pinging the :1 (the other end of the tunnel?) is not.
--Brian
aiccu startup error (ioctl: No buffer space available)
Carmen Sandiego on Sunday, 22 February 2009 17:42:37
Apparently, aiccu is unable to do what it needs to do on my specific CentOS setup (CentOS 5 running under Xen). After quite a bit of trial and error, this is the setup that finally works for me (I offer this not as a criticism of aiccu [that runs fine on my iBook], but simply as help for those who might be having similar issues).
Note: The initscripts-ipv6 page is an excellent resource for trying to decipher the numerous IPv6 scripts in /etc/sysconfig/network-scripts. There is not a specific setup example for SixXS (perhaps one of the SixXS maintainers should make contact and have this added), but if you scroll down to the Hurricane Electric setup instructions, those match the SixXS requirements very closely.
Here are the files I modified:
/etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=yes
HOSTNAME=xenotime
IPV6_DEFAULTDEV="sixxs"
Here are the files I created:
/etc/sysconfig/network-scripts/ifcfg-sixxs
DEVICE="sixxs"
BOOTPROTO="none"
ONBOOT="yes"
IPV6INIT="yes"
IPV6_TUNNELNAME="SixXS"
IPV6TUNNELIPV4="xx.xx.xx.xx" # Tunnel endpoint IPv4 address
IPV6TUNNELIPV4LOCAL="xx.xx.xx.xx" # Your machine's local IPv4 address
IPV6ADDR="2001:xxxx:x:xxx::2/64" # Your machine's IPv6 endpoint address
IPV6_MTU="1280"
TYPE="sit"
Reset the network interfaces:
[root]# service network restart
Start the sixxs interface:
[root]# /etc/sysconfig/network-scripts/ifup-sit sixxs
aiccu startup error (ioctl: No buffer space available)
Carmen Sandiego on Sunday, 22 February 2009 17:46:49
(continued from previous reply)
To check your tunnels:
[root]# ip tunnel
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
sixxs: ipv6/ip remote xx.xx.xx.xx local xx.xx.xx.xx ttl 64
Try a ping:
[root]# ping6 ipv6.google.com
64 bytes from 2001:4860:b002::68: icmp_seq=0 ttl=58 time=52.6 ms
64 bytes from 2001:4860:b002::68: icmp_seq=1 ttl=58 time=53.8 ms
Success!
|
Posting is only allowed when you are