Fórum Ubuntu CZ/SK
Ubuntu pro osobní počítače => Internet a sítě => Téma založeno: funnyman 21 Února 2010, 18:59:37
-
Dobrý den,
na ntb lenovo R61, ubuntu 9.10 a připojení ufon přes modem axesteel mám problémy rozchodit tunel od Sixxs. Registrace i nainstalování aiyia klienta proběhlo v pořádku, tunel končí někde v mariboru (není to zbytečně daleko? Nic jiného jsem na výběr neměl, nedá se to ještě někde donastavit?) a je v provozu, sixxs mi přidělili IPv6 adresu. Vše se tváří jako že funguje, ale žádný webový "zjišťovač" adresy mi IPv6 neobjeví, jen IPv4.
Zapomněl jsem něco nastavit?
-
jako "zjišťovače" adres jsem použil např. http://www.showmyip.com/ (http://www.showmyip.com/) a http://ipv4.whatismyv6.com/ (http://ipv4.whatismyv6.com/). Při pokusu otevřít http://ipv6.whatismyv6.com/ (http://ipv6.whatismyv6.com/) dostanu error 404.
//Při instalaci jsem se řídil návodem na http://wiki.ubuntu.cz/ipv6 (http://wiki.ubuntu.cz/ipv6). Vše proběhlo v pořádku až do věty "To je vše, nyní máte veřejnou IPv6 adresu."
//EDIT
přikládám výpis z aiccu test
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (85.161.104.94)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 85.161.104.94 (85.161.104.94) 56(84) bytes of data.
64 bytes from 85.161.104.94: icmp_seq=1 ttl=64 time=0.021 ms
64 bytes from 85.161.104.94: icmp_seq=2 ttl=64 time=0.049 ms
64 bytes from 85.161.104.94: icmp_seq=3 ttl=64 time=0.048 ms
--- 85.161.104.94 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.021/0.039/0.049/0.013 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 212.18.63.73 (212.18.63.73) 56(84) bytes of data.
64 bytes from 212.18.63.73: icmp_seq=1 ttl=51 time=239 ms
64 bytes from 212.18.63.73: icmp_seq=2 ttl=51 time=239 ms
64 bytes from 212.18.63.73: icmp_seq=3 ttl=51 time=291 ms
--- 212.18.63.73 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 239.017/256.689/291.142/24.364 ms
######
####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
sh: traceroute: not found
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.039 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.053 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.050 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.039/0.047/0.053/0.008 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:379::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:15c0:65ff:379::2(2001:15c0:65ff:379::2) 56 data bytes
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=1 ttl=64 time=0.035 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=3 ttl=64 time=0.060 ms
--- 2001:15c0:65ff:379::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.035/0.051/0.060/0.011 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:379::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
PING 2001:15c0:65ff:379::1(2001:15c0:65ff:379::1) 56 data bytes
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=1 ttl=64 time=303 ms
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=2 ttl=64 time=287 ms
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=3 ttl=64 time=318 ms
--- 2001:15c0:65ff:379::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 287.070/303.035/318.138/12.706 ms
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:15c0:65ff:379::2, 30 hops max, 16 byte packets
1 gw-890.mbx-01.si.sixxs.net (2001:15c0:65ff:379::1) 683.744 ms 299.956 ms 281.101 ms
2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 310.881 ms 272.084 ms 271.96 ms
3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::6) 499.955 ms 372.996 ms 474.959 ms
4 de-cix.he.net (2001:7f8::1b1b:0:1) 303.933 ms 323.967 ms 297.002 ms
5 10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1) 274.908 ms 298.36 ms 272.996 ms
6 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 298.901 ms 375.995 ms 295.969 ms
7 2001:838:5:a::2 (2001:838:5:a::2) 271.942 ms 328.806 ms 326.879 ms
8 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 323.971 ms 328.596 ms 320.888 ms
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:15c0:65ff:379::2, 30 hops max, 16 byte packets
1 gw-890.mbx-01.si.sixxs.net (2001:15c0:65ff:379::1) 281.453 ms 283.917 ms 324.234 ms
2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 251.67 ms 275.999 ms 283.953 ms
3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::6) 299.964 ms 295.995 ms 287.964 ms
4 de-cix.he.net (2001:7f8::1b1b:0:1) 271.94 ms 323.986 ms 303.968 ms
5 10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1) 303.942 ms 319.717 ms 271.951 ms
6 10g-1-4.core1.lon1.ipv6.he.net (2001:470:0:3f::1) 331.954 ms 323.988 ms 323.957 ms
7 10gigabitethernet4-4.core1.nyc4.he.net (2001:470:0:128::1) 407.952 ms 371.976 ms 359.908 ms
8 10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10e::1) 431.986 ms 451.988 ms 436.158 ms
9 10g-1-3.core1.pao1.ipv6.he.net (2001:470:0:34::1) 451.674 ms 486.111 ms 449.739 ms
10 3ffe:80a::b2 (3ffe:80a::b2) 424.034 ms 475.856 ms 424.418 ms
11 hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3) 552.503 ms 586.943 ms 559.946 ms
12 2001:200:0:1c04::251 (2001:200:0:1c04::251) 595.869 ms 636 ms 551.946 ms
13 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 559.943 ms 571.528 ms 555.954 ms
14 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 571.946 ms 579.985 ms 575.952 ms
######
###### ACCU Quick Connectivity Test (done)
-----
a také toto:
tom@tom-laptop:~$ sudo tcpdump -Xns 1500 -i sixxs
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 1500 bytes
11:42:15.080861 IP6 :: > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 0000 0000 0000 0000 `....$..........
0x0010: 0000 0000 0000 0000 ff02 0000 0000 0000 ................
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 7458 07d0 0000 0000 0000 0000 0000 ..tX............
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
11:44:22.211603 IP6 :: > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 0000 0000 0000 0000 `....$..........
0x0010: 0000 0000 0000 0000 ff02 0000 0000 0000 ................
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 7458 07d0 0000 0000 0000 0000 0000 ..tX............
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
11:46:25.283611 IP6 fe80::14c0:65ff:379:1 > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 fe80 0000 0000 0000 `....$..........
0x0010: 14c0 65ff 0379 0001 ff02 0000 0000 0000 ..e..y..........
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 f79d 07d0 0000 0000 0000 0000 0000 ................
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel
-----------
//EDIT: doplněn test
//EDIT2
asi jsem měl hned na úvod napsat že jsem s linuxem začátečník, ta chyba v bodu tři je moje blbost, neměl jsem nainstalován program traceroute...
přikládám tedy výpis:
####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 212.18.63.73 (212.18.63.73), 30 hops max, 60 byte packets
1 172.18.52.14 (172.18.52.14) 117.527 ms 117.460 ms 117.419 ms
2 * * *
3 ge-1-1-0-31.prg11.ip4.tinet.net (77.67.66.41) 117.267 ms 117.235 ms 117.205 ms
4 xe-4-2-0.fra60.ip4.tinet.net (89.149.184.157) 129.148 ms xe-1-0-0.fra60.ip4.tinet.net (89.149.185.101) 129.116 ms xe-0-0-0.fra60.ip4.tinet.net (89.149.185.105) 118.128 ms
5 as1299.ip4.tinet.net (77.67.67.194) 118.146 ms as1299.ip4.tinet.net (77.67.72.14) 118.082 ms 118.121 ms
6 ffm-bb2-link.telia.net (80.91.247.188) 118.102 ms ffm-bb1-link.telia.net (80.91.251.121) 118.094 ms ffm-bb1-link.telia.net (80.91.251.249) 118.077 ms
7 win-b2-link.telia.net (80.91.252.77) 125.960 ms 125.945 ms win-b2-link.telia.net (80.91.253.128) 125.939 ms
8 amis-ic-124784-win-b2.c.telia.net (213.248.94.134) 257.934 ms amis-ic-124783-win-b2.c.telia.net (213.248.72.106) 475.712 ms amis-ic-124784-win-b2.c.telia.net (213.248.94.134) 475.656 ms
9 simbx01.sixxs.net (212.18.63.73) 343.651 ms 359.626 ms 343.576 ms
//EDIT2 - doplněn traceroute
-
Už jsem na to přišel. Problém je v Opeře. Asi nepodporuje IPv6 nebo co. Přes firefox mi to normálně funguje.
Přesto mám dotaz: SixxS pravidelně zkouší, jestli tunel funguje. Chtěl bych proto umožnit na mém počítači, aby odpovídal na ping z internetu. Zkoušel jsem to na http://www.selfseo.com/ping_test.php a tvrdí to, že jsem offline. Můžete to zkusit vy - moje IP 2001:15c0:65ff:379::2. Předpokládám, že to musím někde v systému povolit..?
-
root@mail ~ # ping6 2001:15c0:65ff:379::2
PING 2001:15c0:65ff:379::2(2001:15c0:65ff:379::2) 56 data bytes
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=1 ttl=59 time=86.7 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=2 ttl=59 time=128 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=3 ttl=59 time=166 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=4 ttl=59 time=106 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=5 ttl=59 time=215 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=7 ttl=59 time=188 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=10 ttl=59 time=172 ms
^C
--- 2001:15c0:65ff:379::2 ping statistics ---
11 packets transmitted, 7 received, 36% packet loss, time 10019ms
rtt min/avg/max/mdev = 86.750/152.437/215.983/42.976 ms
root@mail ~ # traceroute !$
traceroute 2001:15c0:65ff:379::2
traceroute to 2001:15c0:65ff:379::2 (2001:15c0:65ff:379::2), 30 hops max, 40 byte packets
1 kiklhorn-1.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:1006::1) 35.621 ms 39.509 ms 41.361 ms
2 1g-2-4.core1.fra1.ipv6.he.net (2001:470:0:69::1) 41.793 ms 41.744 ms 43.125 ms
3 frankfurt1-ge-1-13-2004.amis.net (2001:7f8::218f:0:1) 131.149 ms 131.102 ms 131.055 ms
4 maribor3-te-1-3.amis.net (2001:15c0:ffff:d::5) 68.752 ms 68.706 ms 76.906 ms
5 simbx01.sixxs.net (2001:15c0:ffff:7::2) 76.859 ms 76.812 ms 76.763 ms
6 cl-890.mbx-01.si.sixxs.net (2001:15c0:65ff:379::2) 120.840 ms 95.692 ms 114.053 ms//edit: ty ztráty paketů jsou u mne, mladej něco stahuje a ještě jsem nenahodil shapping.
-
děkuji mnohokrát, teď už jen musím zjistit proč se mi nepřičítají sixxs kredity...
-
Tak teď mám trochu problém. Protože se mi aiccu nespouští při startu, ač by (podle návodu) mělo, zkusil jsem napsat příkaz sudo update-rc.d aiccu defaults. Proces proběhl a terminál vypsal, že byly zadány spouštěče (či tak něco). Zkusil jsem počítač restartovat, ale aiccu znovu neběželo a v terminál nijak nereagoval na příkazy sudo aiccu start, stop, ani test a autotest... vždy se po vteřině znovu objevila konzole.
Rozhodl jsem se tedy aiccu odinstalovat a znovu nainstalovat, přes příkazy apt-get remove a apt-get install. Oboje proběhlo v pořádku, ale po instalaci místo nastavení terminál pouze vypsal:
Nastavuji balík aiccu (20070115-9) ...
* Starting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)... [fail]
přes sudo dpkg-reconfigure aiccu jsem se dostal do nastavení a zadal login a heslo, načež mi vypsal:
tom@tom-laptop:~$ sudo dpkg-reconfigure aiccu
* Stopping SixXS Automatic IPv6 Connectivity Client Utility (aiccu)... [ OK ]
Couldn't connect to the TIC server tic.sixxs.net
Podotýkám, že jsem právě připojený přes Eduroam na univerzitní síti UK, což by mohl být problém (ale z principu by neměl, těžko bude univerzitní síť blokovat traffic do slovinska).
Pokud zadám tracert na adresu PoP serveru (která je hádám stejná jako předevčírem, kdy jsem dělal testy viz výše), vypíše mi terminál toto:
tom@tom-laptop:~$ traceroute 212.18.63.73
traceroute to 212.18.63.73 (212.18.63.73), 30 hops max, 60 byte packets
1 ra.eduroam.cuni.cz (195.113.92.1) 44.407 ms 44.458 ms 46.824 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * *^C
přičemž vždy po cca dvou vteřinách naskočí dalších asi 6 řádků s hvězdičkama. Mám podezření že cesta je zacyklená.
Pokud zadám
tom@tom-laptop:~$ traceroute tic.sixxs.net
traceroute to tic.sixxs.net (193.109.122.244), 30 hops max, 60 byte packets
1 ra.eduroam.cuni.cz (195.113.92.1) 3.588 ms 3.534 ms 4.127 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *^C
tom@tom-laptop:~$ ,
je výsledek stejný.
Ping funguje v pořádku
tom@tom-laptop:~$ ping 212.18.63.73
PING 212.18.63.73 (212.18.63.73) 56(84) bytes of data.
64 bytes from 212.18.63.73: icmp_seq=1 ttl=55 time=12.2 ms
64 bytes from 212.18.63.73: icmp_seq=2 ttl=55 time=11.1 ms
64 bytes from 212.18.63.73: icmp_seq=3 ttl=55 time=11.4 ms
64 bytes from 212.18.63.73: icmp_seq=4 ttl=55 time=20.4 ms
64 bytes from 212.18.63.73: icmp_seq=5 ttl=55 time=13.6 ms
^C
--- 212.18.63.73 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 11.113/13.766/20.433/3.445 ms
tom@tom-laptop:~$ ping tic.sixxs.net
PING tic.sixxs.net (213.204.193.2) 56(84) bytes of data.
64 bytes from broker04.ams.nl.sixxs.net (213.204.193.2): icmp_seq=1 ttl=54 time=31.6 ms
64 bytes from broker04.ams.nl.sixxs.net (213.204.193.2): icmp_seq=2 ttl=54 time=26.4 ms
64 bytes from broker04.ams.nl.sixxs.net (213.204.193.2): icmp_seq=3 ttl=54 time=25.8 ms
64 bytes from broker04.ams.nl.sixxs.net (213.204.193.2): icmp_seq=4 ttl=54 time=27.8 ms
^C
--- tic.sixxs.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 25.842/27.936/31.615/2.244 ms
Můj problém s programem aiccu ale podle mě s cestou nesouvisí, po zadání příkazu vůbec nereaguje, vypíše jen verzi, licenci a podporované brokery:
tom@tom-laptop:~$ sudo aiccu
aiccu (start|stop|brokers|tunnels|test|autotest|license|version) [<configfile>]
tom@tom-laptop:~$ sudo aiccu version
AICCU 2007.01.15-console-linux by Jeroen Massar
tom@tom-laptop:~$ sudo aiccu brokers
AARNet|tsp://broker.aarnet.net.au|http://broker.aarnet.net.au|au|
UKERNA|tsp://broker.ipv6.ac.uk|http://www.broker.ipv6.ac.uk|gb|
Wanadoo France|tsp://ts.ipv6.wanadoo.fr|http://www.ipv6.wanadoo.fr|fr|
ECS Southampton|tsp://broker.ecs.soton.ac.uk|http://broker.ecs.soton.ac.uk|gb|
Hexago / Freenet6|tsp://broker.freenet6.net|http://www.freenet6.net|ca|
ACADEMIA Sinica Computing Centre|tsp://tb2.ipv6.ascc.net|http://tb2.ipv6.ascc.net|tw|
SixXS|tic://tic.sixxs.net|http://www.sixxs.net|be de ee fi gb ie it nl nz pl pt si se us|
tom@tom-laptop:~$ sudo aiccu start
tom@tom-laptop:~$ sudo aiccu stop
tom@tom-laptop:~$ sudo aiccu test
tom@tom-laptop:~$ sudo aiccu autotest
tom@tom-laptop:~$ sudo aiccu tunnels
tom@tom-laptop:~$
Podle návodu se to zdálo jednoduché, realita je trochu jiná. Nejsem pokročilý uživatel linuxu a nevím kde by mohla být chyba, proč aiccu dělá co dělá, tak mě prosím nekamenujte, pokud to bude nějaká trivialita
//edit: vložen konfigurační soubor
# Under control from debconf, please use 'dpkg-reconfigure aiccu' to reconfigure
username THO2-SIXXS
password ........
protocol tic
server tic.sixxs.net
tunnel_id T25541
# AICCU Configuration
# Login information (defaults: none)
#username <your nichandle/username>
#password <your password>
# Protocol and server to use for setting up the tunnel (defaults: none)
#protocol <tic|tsp|l2tp>
#server <server to use>
# 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 sixxs
# 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