|
Ticket ID: SIXXS #3559805 Ticket Status: User PoP: plwaw01 - ICM (Warsaw)
Problem with T15329 since 2011-02-01 about 12:00 GMT
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Wednesday, 02 February 2011 19:07:17
Seems like I have a problem with the ICM tunnel, about 12:00 suddenly packet loss spiked and I'm unable to route anything through the tunnel. Interesting thing is that there seem to be packets on the traffic graphs. Neither pinging anything directly from the router works nor from the subnet.
ping 2001:6A0:200:85::1
Feb 2 17:55:30.389: %SYS-5-CONFIG_I: Configured from console by vty0 (91.194.188.58)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:6A0:200:85::1, timeout is 2 seconds:
Feb 2 17:55:33.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
Feb 2 17:55:35.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
Feb 2 17:55:37.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
Feb 2 17:55:39.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
Feb 2 17:55:41.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
Success rate is 0 percent (0/5)
It was working before and it's also working if I set up another tunnel provider on that box.
I've checked the firewall settings, even disabled it but it didn't help.
State change: user
The state of this ticket has been changed to user
Problem with T15329 since 2011-02-01 about 12:00 GMT
Please read and follow the "Reporting Problems" section on the Contact page.
Feb 2 17:55:33.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120).
That is RFC1918 address space, did you configure your NAT properly?
Problem with T15329 since 2011-02-01 about 12:00 GMT
Shadow Hawkins on Thursday, 03 February 2011 00:38:14Feb 2 17:55:33.265: Tunnel1: IPv6/IP encapsulated 192.168.1.99->193.219.28.26 (linktype=79, len=120). That is RFC1918 address space, did you configure your NAT properly?
Like I said before, it was working until yesterday 12:00 on the graphs.
All incoming traffic is being redirected to the internal address
IPv4 traceroute to POP
traceroute 193.219.28.26
Type escape sequence to abort.
Tracing the route to plwaw01.sixxs.net (193.219.28.26)
1 * * *
2 c192-1.icpnet.pl (85.221.192.1) 8 msec 36 msec 36 msec
3 c97-93.icpnet.pl (62.21.97.93) 16 msec 24 msec 12 msec
4 * * *
5 * * *
6 ICM.plix.pl (195.182.218.68) 16 msec 24 msec 16 msec
7 plwaw01.sixxs.net (193.219.28.26) 24 msec 12 msec 16 msec
IPv6 traceroute:
traceroute 2001:6a0:200:85::1
Type escape sequence to abort.
Tracing the route to gw-134.waw-01.pl.sixxs.net (2001:6A0:200:85::1)
1 * * *
2 * * *
(and loops on that until "Destination not found inside max hopcount diameter.")
Other details:
#show ipv6 route
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S ::/0 [1/0]
via ::, Tunnel1
C 2001:6A0:154::/64 [0/0]
via ::, FastEthernet0/1
L 2001:6A0:154::/128 [0/0]
via ::, FastEthernet0/1
C 2001:6A0:200:85::/64 [0/0]
via ::, Tunnel1
L 2001:6A0:200:85::2/128 [0/0]
via ::, Tunnel1
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Config:
ipv6 unicast-routing
interface Tunnel1
description Sixxs tunnel plwaw
no ip address
no ip route-cache
ipv6 address 2001:6A0:200:85::2/64
ipv6 enable
tunnel source 192.168.1.99
tunnel destination 193.219.28.26
tunnel mode ipv6ip
interface FastEthernet0/0
ip address 192.168.1.99 255.255.255.0
no ip route-cache
speed auto
full-duplex
Regards,
--
ukasz [DeeJay1] Jerna
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 02 February 2011 23:43:10
Posting is only allowed when you are