SixXS::Sunset 2017-06-06

Tunnel does not work on CentOS
[de] Shadow Hawkins on Friday, 30 March 2007 11:26:14
Hi, i am using my Server with CentOS4 x86_64. I created i ifcfg-tun6to4 in the /etc/sysconfig/network-scripts folder with the following content: EVICE=tun6to4 ONBOOT=no BOOTPROTO=none IPV6INIT=yes IPV6TUNNELIPV4=212.224.0.188 IPV6TUNNELIPV4LOCAL=85.14.213.255 IPV6ADDR=2001:6f8:900:272::1/64 If i try to start the interface i got no message and there's also no interface visible in ifconfig... Of course i added the following lines to the /etc/sysconfig/network file: NETWORKING_IPV6=yes IPV6_DEFAULTDEV=tun6to4 The kernel is compiled with IPv6 and also Tunnel Support. What do i wrong? Thanks! Regards Tobias
Tunnel does not work on CentOS
[ch] Jeroen Massar SixXS Staff on Friday, 30 March 2007 13:22:43
I hope that first line is a cut&paste typo and that it says "DEVICE=tun6to4" Check the initscripts-ipv6 documentation which also has some tips for debugging (although a 'set -x' at the top will help out too I am pretty sure :) Next to that, read the "Reporting Problems" section, which outlines quite some ways of testing how it can be configured. Seeing that .255 and: inetnum: 85.14.213.224 - 85.14.213.255 netname: UNITEDCOLO-TOBIAS-BAUER-NET How sure are you btw that .255 is not a broadcast address? Unless it is part of a /23 or something of course, which can be possible.
Tunnel does not work on CentOS
[nl] Shadow Hawkins on Wednesday, 23 May 2007 10:28:47
The most important issue here is that you should not use tun6to4 but sit1 as device.
/etc/sysconfig/network-scripts/ifcfg-<tunnelinterface-name> [tunnelinterface-name=sitX (X > 0)] Control a dedicated IPv6-in-IPv4 tunnel interface
The quote from the link should be clear enough.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker