hallo ipv6ler,

dank eines finnischen kollegen ist es mir nun gelungen "TunTap" und "AICCU" auf OSX zu compilieren
und zum laufen zu bringen.

<http://www.sixxs.net/forum/?msg=setup-514633>

Meine frage ist , nun ich habe jetzt einen sixxs tunnel und ein sixxs subnetz,
Route ich das subnetz über den tunnel ?

Das ist mein AICCU config:

Soweit ist alles ok oder ?

gruss

marc


************************************************************************ *******************************

# 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 hier kommt die tunnel ID rein <---------------

# 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


--
They said it couldn't be done but sometimes it
doesn't work out that way.
  - Casey Stengel

web: http://www.let.de
.local http://stattfernsehen.com



_______________________________________________
ipv6 mailing list
[email protected]
http://listserv.uni-muenster.de/mailman/listinfo/ipv6

Antwort per Email an