SixXS::Sunset 2017-06-06

Routing problem with subnet
[fi] Shadow Hawkins on Wednesday, 14 April 2004 00:23:48
Today I requested a subnet (R1391) for my tunnel T2827 (heartbeat tunnel). The subnet got accepted by SixXS staff and I enabled and configured my Debian server and added a few IP's from my subnet range. It worked fine for couple minutes and suddenly the connection dropped. I waited some time and restarted the heartbeat client, the tunnel seems to work ok but subnet is not working anymore. Here's what ifconfig shows:
sit1 Link encap:IPv6-in-IPv4 inet6 addr: 2001:14b8:13d::1/48 Scope:Global inet6 addr: 2001:14b8:100:52::2/64 Scope:Global inet6 addr: fe80::50de:84f9/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1 RX packets:871 errors:0 dropped:0 overruns:0 frame:0 TX packets:1665 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:138316 (135.0 KiB) TX bytes:187293 (182.9 KiB)
Where 2001:14b8:100:52::2/64 is my tunnel and 2001:14b8:13d::/48 is the subnet. I tried traceroute6 from my friends machine (also SixXS user and same POP):
traceroute to 2001:14b8:13d::1 (2001:14b8:13d::1) from 2001:14b8:12b::14, 30 hops max, 16 byte packets 1 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 33.728 ms 33.298 ms 49.888 ms 2 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 35.271 ms 33.482 ms 53.649 ms 3 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 59.446 ms 75.49 ms 107.709 ms 4 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 107.454 ms 37.487 ms 35.673 ms 5 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 35.4 ms 37.556 ms 35.61 ms 6 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 37.458 ms 37.616 ms 37.661 ms 7 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 37.417 ms * 64.182 ms 8 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 39.493 ms 39.65 ms 39.533 ms 9 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 39.312 ms 39.487 ms 47.815 ms 10 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 39.38 ms 141.705 ms 39.551 ms 11 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 153.599 ms 225.632 ms 205.755 ms 12 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 49.352 ms 77.519 ms 159.82 ms 13 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 53.271 ms 175.585 ms 45.652 ms 14 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 43.436 ms 43.51 ms 43.676 ms 15 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 43.434 ms 47.662 ms 49.566 ms 16 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 45.479 ms 43.492 ms 49.686 ms 17 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 49.323 ms 43.528 ms 45.554 ms 18 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 47.459 ms 47.493 ms 57.748 ms 19 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 45.404 ms 59.509 ms 57.633 ms 20 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 65.774 ms 47.495 ms 47.657 ms 21 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 63.519 ms * 78.91 ms 22 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 157.545 ms 157.531 ms 63.509 ms 23 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 49.492 ms 49.461 ms 47.71 ms 24 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 53.531 ms 49.303 ms 49.529 ms 25 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 49.37 ms 55.467 ms 67.657 ms 26 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 51.454 ms 51.563 ms 53.581 ms 27 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 77.483 ms 51.556 ms 51.656 ms 28 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 51.518 ms 51.544 ms 61.55 ms 29 2001:14b8:100:1b::1 (2001:14b8:100:1b::1) 55.473 ms 53.49 ms 51.624 ms 30 2001:14b8:0:2000::201 (2001:14b8:0:2000::201) 57.507 ms 53.479 ms 55.623 ms
It seems to stuck into endeless loop. Thanks for help. Edit: I also tried to disable and enable the subnet, didn't help. Edit2: route -A inet6:
Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 1 0 lo ::80.222.132.249/128 :: U 0 0 0 lo ::127.0.0.1/128 :: U 0 0 0 lo ::/96 :: U 256 0 0 sit0 2001:14b8:100:52::2/128 :: U 0 0 0 lo 2001:14b8:100:52::/64 :: U 256 1 0 sit1 2001:14b8:13d::1/128 :: U 0 0 0 lo 2001:14b8:13d::2/128 :: U 0 0 0 lo 2001:14b8:13d::3/128 :: U 0 0 0 lo 2001:14b8:13d::4/128 :: U 0 0 0 lo 2001:14b8:13d::5/128 :: U 0 0 0 lo 2001:14b8:13d::6/128 :: U 0 0 0 lo 2001:14b8:13d::7/128 :: U 0 0 0 lo 2001:14b8:13d::8/128 :: U 0 0 0 lo 2001:14b8:13d::9/128 :: U 0 0 0 lo 2001:14b8:13d::10/128 :: U 0 0 0 lo 2001:14b8:13d::11/128 :: U 0 0 0 lo 2001:14b8:13d::12/128 :: U 0 0 0 lo 2001:14b8:13d::/48 :: U 256 0 0 sit1 2000::/3 2001:14b8:100:52::1 UG 1 6 0 sit1 fe80::50de:84f9/128 :: U 0 0 0 lo fe80::250:fcff:feb1:24bf/128 :: U 0 0 0 lo fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 sit1 ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sit1 ::/0 :: UD 256 0 0 eth0
Is there something wrong with that?
Routing problem with subnet
[fi] Shadow Hawkins on Wednesday, 14 April 2004 08:59:37
Just to note, I have exactly the same problem. I'm using the same PoP with heartbeat client and my subnet stopped working yesterday after being up for a day.
Routing problem with subnet
[fi] Shadow Hawkins on Thursday, 15 April 2004 22:30:00
I too had some problems with subnet routing couple of days ago. And some days before that. Always cyclic route with the two routers as you have. It seems that on some point I was routing my subnet back to fihel01 (now how stupid is that |:( ). The odd thing was that when I had a tunnel to the Scarlet PoP in Holland I don't remember ever seeing cyclic route, and I was using the same configuration script now with fihel01, as I used with Scarlet. I wonder if I somehow "made the cyclic route to appear" with my routing mistakes... Anyway, of course I didn't set route wrong, it just... got wrong... Fortunately I could compare my script with another and made few minor changes, and the route-subnet-back-to-PoP never appeared again. Here's the core of my script: NETIF - Internet interface 'eth0' TUNLIF - tunnel interface 'sixxs' SUBIF - LAN interface 'eth1'
ip tunnel add $TUNLIF mode sit ttl 64 local $MYIP4 remote $SXIP4 dev $NETIF ip link set mtu 1280 dev $TUNLIF ip link set $TUNLIF up ip -6 addr add $MYIP6 dev $TUNLIF ip -6 route add 2000::/3 dev $TUNLIF ip -6 addr add $SUBIP6 dev $SUBIF
I think the biggest mistake ws to omit the "dev $NETIF" from the first line. Toivanen, if I understand your routing table correctly, you are also routing your subnet back to your PoP. Check it out.

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

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