Ticket ID: SIXXS #991094 Ticket Status: User PoP: deham01 - Easynet (Hamburg)
No packets anymore routed into my established tunnel
Shadow Hawkins on Wednesday, 04 March 2009 19:21:31
Hi,
My tunnel T14069 (type AYIYA, POP deham01) did work fine for many months.
Since yesterday evening, my tunnel endpoint 2001:6f8:900:acf::2 does
not receive Packets from the tunnel and Sixxs reports a packet loss of
100% too.
The tunnel information says:
IPv6 Prefix 2001:6f8:900:acf::1/64
PoP IPv6 2001:6f8:900:acf::1
Your IPv6 2001:6f8:900:acf::2
Created 2008-01-28 20:18:19 CET
Last Alive 2009-03-03 18:43:53 CET
ping6 to 2001:6f8:900:acf::1 receives no answer. tcpdump on the
ipv6-interface and on the underlying ipv4-interface prints the outgoing
packets, but no reply packets.
Stopping the tunnel with "aiccu stop" and starting with "aiccu start"
was successful, but there is still no traffic coming in. "aiccu test"
reports Userstate: enabled.
The Ping through an other (working) tunnel hosted too by deham01 wrote:
PING 2001:6f8:900:acf::2(2001:6f8:900:acf::2) 56 data bytes
From 2001:6f8:900:a27::1 icmp_seq=1 Destination unreachable: No route
From 2001:6f8:900:a27::1 icmp_seq=2 Destination unreachable: No route
The tunnel endpoint resides inside a private network which is connected
via a NAT-Router (dynamic IPv4 adr's) to the internet. At the critical
time there was no reconnect and no change of the IPv4 address.
Thanks in advance
Andreas
State change: user
Jeroen Massar on Wednesday, 04 March 2009 19:26:33
The state of this ticket has been changed to user
No packets anymore routed into my established tunnel
Jeroen Massar on Wednesday, 04 March 2009 19:27:02
Please actually read the "Reporting Problems" section.
No packets anymore routed into my established tunnel
Shadow Hawkins on Wednesday, 04 March 2009 20:48:32
Thanks Jeroen for the fast reply.
I already read the section. Unfortunly I have no cut&pate-capable access to the system while the tunnel is broken; only a KVM-like access.
I just tried to post a lot of related information, but it seems to be lost because it took more time than the login-timeout permitted. Please stand by,
until I hopefully could recover it.
Andreas
No packets anymore routed into my established tunnel
Shadow Hawkins on Wednesday, 04 March 2009 21:17:44
Rehi,
hier sind nun die restaurierten Angaben; fehlt noch was?
Tunnel Information for T14069:
POP Id : deham01
IPv6 Local : 2001:6f8:900:acf::2/64
IPv6 Remote : 2001:6f8:900:acf::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 20510 870 0 0 13296 0 0 0 BMRU
eth1 1500 0 9169 0 0 0 10022 0 0 0 BMRU
ip6 1280 0 0 0 0 0 7 0 0 0 MOPRU
lo 16436 0 57 0 0 0 57 0 0 0 LRU
---------- ip4 tables ---------------
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
--------- ip6tables ---------------
Chain INPUT (policy ACCEPT)
target prot opt source destination
HOST 0 anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain HOST (1 references)
target prot opt source destination
ACCEPT 0 anywhere anywhere state RELATED,ESTABLISHED
ACCEPT ipv6-icmp anywhere anywhere
LOG tcp anywhere anywhere tcp flags:SYN,RST,ACK/SYN LOG level info
ACCEPT tcp anywhere anywhere tcp dpt:ssh
LOG 0 anywhere anywhere LOG level info
DROP 0 anywhere anywhere
-------------- netstat -A inet6 -r -----------------
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:6f8:900:acf::/64 :: U 256 1 0 ip6
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 ip6
::/0 2001:6f8:900:acf::1 UG 1024 0 0 ip6
::1/128 :: U 0 5 3 lo
2001:6f8:900:acf::2/128 :: U 0 0 1 lo
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 ip6
--------------- netstat -A inet -r ---------------------
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.129.0 * 255.255.255.0 U 0 0 0 eth1
192.168.142.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth1
default 192.168.129.1 0.0.0.0 UG 0 0 0 eth1
Viele GrüÃe,
Andreas
No packets anymore routed into my established tunnel
Shadow Hawkins on Wednesday, 04 March 2009 21:35:35
Danke! Thanks!
Whoever may have repaired the item, the tunnel works again.
You may close the ticket as resolved.
Posting is only allowed when you are logged in. |