|
FreeBSD 7.2 "protocol not supported" error
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Saturday, 05 September 2009 17:26:55
hullo,
I've got my ipv6 tunnel connected on a FreeBSD 7.2 amd64 box, however, it seems I may be lacking something either as a module or in the kernel. The kernel is quite small but it does have ipv6 in it. kldstat shows if_tun0, if_gif0 and if_faith0 there too.
I get this error when I try to ping6:
ping6: socket: Protocol not supported
And the tun0 output in ifconfig doesn't look right either:
tun0: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
Opened by PID 82766
(82766 is sixxs-aiccu)
in /var/log/messages, I get this:
Sep 5 17:15:02 XXXX sixxs-aiccu: [tun-tun->tundev] Error while writing to TUN: 0 != 108
Sep 5 17:15:35 XXXX last message repeated 5 times
Sep 5 17:17:06 XXXX last message repeated 14 times
thus, who any know what else I could look for here or what other module I could use?
ta, t.
FreeBSD 7.2 "protocol not supported" error
tun0: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
An MTU of 1500 is definitely wrong. Also, it seems that that interface is not "UP" either and it looks like it is lacking IPv6 addresses too.
Sep 5 17:15:02 XXXX sixxs-aiccu: [tun-tun->tundev] Error while writing to TUN: 0 != 108
It seems that nothing can be output over the tunnel, which is not so odd as the interface is not UP.
Please provide the output of AICCU in verbose mode.
(Don't forget to mask out the 'password' line in the TIC output, the MD5 line doesn't matter, unless somebody really wants to spend a long time on cracking it, but still then they would only have a collision for that one, and the challenges are random anyway ;).
FreeBSD 7.2 "protocol not supported" error
Shadow Hawkins on Sunday, 06 September 2009 11:02:15
hello,
thanks for the very quick reply. Here is the verbose output, when I start up the tunnel:
Tunnel Information for T19751:
POP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:7f::2/64
IPv6 Remote : 2001:1af8:fe00:7f::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
As you can see, it makes the connection just fine. However, it the gif0/tun0 device is this:
tun0: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
Opened by PID 41291
if_tun, if_gif and if_faith are loaded in the system as modules. it's an amd64 system.
during the nite, the /var/log/message was full of the same error as before.
are there settings needed in the /etc/sysctl.conf? Would you have any other ideas on points I may have missed here?
ta, t.
FreeBSD 7.2 "protocol not supported" error
Here is the verbose output, when I start up the tunnel:
That is not the verbose output. The verbose output contains AICCU version numbers and the TIC protocol output, and that is what we need.
FreeBSD 7.2 "protocol not supported" error
Shadow Hawkins on Sunday, 06 September 2009 19:59:48
I'm sorry, I tried looking at the man page (there isn't one) and googling for examples (couldn't find any).
Thus, what do I need to do exactly to get the output you need? When you said verbose, I thought you just wanted that verbose output from the aiccu.conf file. Running FreeBSD 7.2 amd64
ta, t.
FreeBSD 7.2 "protocol not supported" error
Shadow Hawkins on Sunday, 06 September 2009 20:17:07
aaargh, it must be the test option you mean. the xubuntu version does have a man page.
you're right with the tun0 issue. here's some output:
ifconfig: up: permission denied
ifconfig: ioctl (set mtu): Operation not permitted
ifconfig: socket(family 28,SOCK_DGRAM: Protocol not supported
ifconfig: socket(family 28,SOCK_DGRAM: Protocol not supported
route: writing to routing socket: Operation not permitted
so I think here is the problem. this box is a virtual box and it could be the security settings are blocking this.
This was run as sudo as well.
Do you need anymore info here?
ta, t.
FreeBSD 7.2 "protocol not supported" error
Looks to me that you are not the administrator of your own machine. Nothing can solve that problem, except becoming a proper one.
FreeBSD 7.2 "protocol not supported" error
Shadow Hawkins on Wednesday, 09 September 2009 18:58:04
True, it seems so. The machine I'm using is a virtual machine. And I'm not sure of the setup, if it's xen or something else.
I did the command as sudo and you saw it making the connection, then I saw that the card wasn't changed. This is what confused me.
I've been talking to the head of the project about this. Setting up sixxs is very easy, you don't need much kernel/module wise. So, this was quite odd. I'm used to be able to do what I want as root!
ta, t.
FreeBSD 7.2 "protocol not supported" error
AICCU has an aiccu.conf, this file contains the option to add "verbose true" and "daemonize false", if you do that, you get a whole lot of details.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 05 September 2009 22:04:57
Posting is only allowed when you are