|
sit1 not passing traffic on Centos 5
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 23 May 2007 11:43:53
On my Centos 5 machine I am unable to make sit1 to work properly.
Configuring the interface and activating it is not the problem. The config in /etc/sysconfig/network-script/ifcfg-sit1:
DEVICE=sit1
ONBOOT=yes
BOOTPROTO=none
IPV6INIT=yes
IPV6TUNNELIPV4=213.204.193.2
IPV6TUNNELIPV4LOCAL=84.244.132.201
IPV6ADDR=2001:960:2:595::2/64
The interface is up:
sit1 Link encap:IPv6-in-IPv4
inet6 addr: 2001:960:2:595::2/64 Scope:Global
inet6 addr: fe80::54f4:84c9/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Routing is taken care of:
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:888:10fa::12/128 2001:888:10fa::12 UC 0 6 0 sit1
2001:960:2:595::/64 :: U 256 0 0 sit1
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 sit1
::/0 :: U 1 0 0 sit1
::1/128 :: U 0 3 1 lo
2001:960:2:595::/128 :: U 0 0 2 lo
2001:960:2:595::2/128 :: U 0 0 1 lo
fe80::54f4:84c9/128 :: U 0 0 1 lo
fe80::219:d1ff:fe13:cd5e/128 :: U 0 0 1 lo
fe80::250:56ff:fec0:1/128 :: U 0 0 1 lo
fe80::250:56ff:fec0:8/128 :: U 0 0 1 lo
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 sit1
When I check with tcpdump on eth0 I do notice my system reports the tunnel is not working:
11:04:03.893503 IP broker04.ams.nl.sixxs.net > balin.waakhond.net: IP6 aragorn.hugo.vanderkooij.org.49755 > cl-1430.ams-04.nl.sixxs.net.traceroute: UDP, length 16
11:04:03.893535 IP balin.waakhond.net > broker04.ams.nl.sixxs.net: ICMP balin.waakhond.net protocol 41 port 0 unreachable, length 92
As far as I can tell the modules list is fine too:
Module Size Used by
ip_conntrack_netbios_ns 6977 0
ipt_LOG 10177 1
ipt_REJECT 9537 1
xt_state 6209 10
ip_conntrack 53153 2 ip_conntrack_netbios_ns,xt_state
nfnetlink 10713 1 ip_conntrack
iptable_filter 7105 1
ip_tables 17029 1 iptable_filter
ip6t_REJECT 9409 1
xt_tcpudp 7105 20
ip6table_filter 6849 1
ip6_tables 18181 1 ip6table_filter
x_tables 17349 7 ipt_LOG,ipt_REJECT,xt_state,ip_tables,ip6t_REJECT,xt_tcpudp,ip6_tables
ipv6 250369 39 ip6t_REJECT
I tried to dig around a bit based on the error but could not find any hints via google or in the forum here.
Any suggestions towards a solution are welcome as I ran out of ideas at the moment.
sit1 now passing traffic on Centos 5
Shadow Hawkins on Wednesday, 23 May 2007 11:54:47
Right. The sound you just heard is me hitting myself with a LART.
If one makes a mistake to fill in the incorrect IPv4 address the tunnel is oddly connected. Too bad it didn't shout "stupid" to me.
When I put in a remark and restated the interface it worked fine:
#IPV6TUNNELIPV4LOCAL=84.244.132.201
I just coded the following metal subroutine:
IF [ 201 -ne 155 ] THEN
LART HUGO
FI
Thanks,
Hugo.
|
Posting is only allowed when you are