SixXS::Sunset 2017-06-06

RTNETLINK answers: No route to host
[nl] Shadow Hawkins on Tuesday, 02 September 2003 16:43:39
I get this message whenever I give the "Ifup sixxs" command in debian. I Have set my /etc/network/interfaces accordingly to the Linux debian Faq. it looks like this: auto sixxs iface sixxs inet6 v4tunnel address 3ffe:8114:1000::68a netmask 127 endpoint 212.19.192.219 ttl 64 up ip link set mtu 1280 dev sixxs up ip route add 2000::/3 via 3ffe:8114:1000::68b dev sixxs After ifup I get this message: RTNETLINK answers: No route to host If I give the commands by hand (As in Linux new FAQ) everything works out fine, until this command: ip -6 ro add default via 3ffe:8114:1000::68a dev sixxs I get the same message: RTNETLINK answers: No route to host Afterwards I can seem to ping both ends of the tunnel, but showehow this looks a bit like the linux-2.4.21 bug so I would be just pinging myself. But pingen an random chosen IP out here in the forum is not possible. @ the moment I'm trying to compile an 2.4.20 kernel. but I'm not sure this is going to work. Anyone any idea??? Thanks Marc (Newbie).
RTNETLINK answers: No route to host
[nl] Shadow Hawkins on Tuesday, 02 September 2003 21:38:11
OK ipv6 with kernel 2.4.21 :Y)
RTNETLINK answers: No route to host
[ch] Jeroen Massar SixXS Staff on Wednesday, 03 September 2003 00:24:14
Anycast is NOT a bug. It's a real live feature, that it only was implemented until 2.4.21 in the Linux kernels is a shame. 8<-------------- Anycast is adressing one of many hosts with one address, or is it? There's a lot of myths out there and this IETF Draft tries to clarify: The memo tries to identify the problems and issues in the use of IPv6 anycast [Hinden, 1998] defined as of today. The goals of the draft are to understand the currently-defined IPv6 anycast better, to provide guidelines for people trying to deploy anycast services, and to suggest updates to IPv6 anycast protocol specification. Analysis of IPv6 anycast, IETF Draft, June 2003 ------------------------>8 Using 2 /128's (one to the localside and one to the remote over the interface) with the IPng POP solves this 'problem'

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

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