|
help with compiling aiccu with native GUI for osx 10.4.9
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 05 May 2007 15:51:50
hello experts,
i would like to test the provided sixx subnet without Radv first
whitch would work on my router with OPENWRT but i am afraid to \" kill\" him ?
I downloaded the required tun/tap librarys for osx
<http://www-user.rhrk.uni-kl.de/~nissler/tuntap/>
It seems like there is no native GUI for osx , so do i need to have X11 installed ?
Any pointers are greatly appreciated
marc :
help with compiling aiccu with native GUI for osx 10.4.9
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Friday, 18 May 2007 21:38:14
Here's the key for somewhat instant success:
% sudo -s
# wget http://www-user.rhrk.uni-kl.de/~nissler/tuntap/tuntap_tiger_20060513_src.tar.gz
# tar zxvf tuntap_tiger_20060513_src.tar.gz
# cd tuntap
# make
# make install_kext
# chown -R root:wheel /Library/Extensions/tap.kext
# chown -R root:wheel /Library/Extensions/tun.kext
# make install_scripts
And then reboot. You don't need any GUI to do this. Just compile it and then compile aiccu as well and edit the /etc/aiccu.conf file according your need. After that You're good to go.
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Friday, 18 May 2007 22:37:43
Hello Jari,
thanks you very much , i think the "tuntap" installation was successful .
After i restarted it was asking me for fixing permissions on startup item and that was it. O-)
Whats the next step to compile AICCU ? After that i just need to put my data into the aiccu.conf file ?
thanks again
marc
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Saturday, 19 May 2007 01:03:07
It goes like this:
% sudo -s
# wget --no-check-certificate https://noc.sixxs.net/archive/sixxs/aiccu/unix/aiccu_current.tar.gz
# tar xzvf aiccu_20070115.tar.gz
# cd aiccu
# make
# make install
# nano /etc/aiccu.conf
And pick from these elements while editing that file:
username MM76-6BONE
password _your_passwd_here_
protocol tic
server tic.sixxs.net
ipv6_interface tun0
tunnel_id _your_tunnelid_here_
verbose true
daemonize false
automatic true
requiretls false
behindnat true
Depending on your NAT setup, you may or may not need the behindnat line at all. Save the file, and as root type:
# aiccu start
If all went well, you may start surfing in the IPv6 world with Safari and running X-Chat Aqua with your local IRCnet IPv6 servers.
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Saturday, 19 May 2007 01:26:17
hello jari,
worked well so far , just a question regarding the tunnel, i have requested
a subnet from sixx and i can´t find the tunnel ID
thats my config so far
thanks again *D
********************************************************************************
# AICCU Configuration
# Login information (defaults: none)
username MM76-6BONE
password xxxxxxxxxx
# Protocol and server to use for setting up the tunnel (defaults: none)
protocol tic
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 tun0
# The tunnel_id to use (default: none)
# (only required when there are multiple tunnels in the list)
tunnel_id Txxxx ????????????????
# 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
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Saturday, 19 May 2007 09:27:33
You can see all your tunnels that belong to your account with the command:
% sudo -s
# aiccu tunnels
It's probably the second last line that is printed out by that command.
By the way, you probably may want to make aiccu to run without giving the root priviledges password every time. That's accomplished by making the aiccu binary suid root with the command:
# chmod +s /usr/sbin/aiccu
You would need to make the same thing with the route command as well, otherwise it complains:
route: must be root to alter routing table
But then again setting that suid root may not be a good idea at all. I'd recommend starting the tunnel every time with the administrator password.
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Saturday, 19 May 2007 12:09:43
hello jari,
thats cool , worked well . I see 2 tunnels , the second one i requested for my static ip
T5218 2001:6f8:xxx:3f1::2 heartbeat deham01
T10135 2001:6f8:900:xxx::2 87.79.236.249 deham01
but just for my understanding, the subnet could be routed over any of the tunnels right ?
I have 2 machines behind a Linksys router with OpenWRT and i have
several services that run on this machines , like BIND , Postfix a tracwiki
a darwin streaming server and a reflector , My goal is to make them
all ipv6 ready step by step.
So both machines need an ipv6 adress and thats what i acomplish with the
AICCU tool right ?
thanks again
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Saturday, 19 May 2007 21:05:54
Login into noc.sixxs.net and in the logged user home you'll find your tunnels and subnets. Click on the subnet id and look for the first label "IPv6 Them" address field. That's the IPv6 address that the subnet traffic is routed to. It's been bound into one or the another.
The trivial solution would be using different tunnels for different machines, for both running aiccu separately with their own tunnel. That's probably what you want to do right now in order to gets things up and running.
But I'd recommend that you actually end up terminating your IPv6 connection into that OpenWRT router and advertize your tunneled subnet with radvd ( http://www.linuxhq.com/IPv6/radvd.html ) from that router to your local area network. I'm not there myself yet , so I cannot give exact details on how to accomplish that. But I'd certainly like to read about it. :z
help with compiling aiccu with native GUI for osx 10.4.9
Shadow Hawkins on Monday, 21 May 2007 13:26:21
ok, i renamed my interface and changed
my subnet settings and i get till there
mini:~ mini$ aiccu start
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:xxx:795::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING6(56=40+8+8 bytes) 2001:6f8:xxx:795::2 --> 2001:6f8:xxx:795::1
--- gw-1942.ham-01.de.sixxs.net ping6 statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
so. something is still wrong in my configuration ?
thanks a lot marc
|
Posting is only allowed when you are