SixXS::Sunset 2017-06-06

FBSD: failed to add route
[si] Carmen Sandiego on Sunday, 04 January 2004 01:37:07
My kernel is always complaining: /kernel: nd6_lookup: failed to add route for a neighbot(Tunnel IPV6 POP endpoint), errno=17 for gif0 i'm using prefixlen 128 but nothing helps.... Any ideas? Thank you
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Sunday, 04 January 2004 01:43:23
You might want to tell what kind of kernel and which version you are using and the exact configuration you typed and the exact configuration that the system has currently.
FBSD: failed to add route
[si] Carmen Sandiego on Sunday, 04 January 2004 02:10:31
FreeBSD 4.9-release gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 tunnel inet 193.77.34.220 --> 212.224.0.188 inet6 2001:6f8:900:a5::2 --> 2001:6f8:900:a5::1 prefixlen 128 inet6 fe80::20c:6eff:fea8:e398%gif0 prefixlen 64 scopeid 0x6 i used ifconfig gif0 create gifconfig gif0 193.77.34.220 212.224.0.188 ifconfig gif0 inet6 2001:6f8:900:a5::2 2001:6f8:900:a5::1 prefixlen 128 route add -inet6 default 2001:6f8:900:a5::1 That was it...
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Sunday, 04 January 2004 02:25:18
The "gifconfig" command can be replaced with "ifconfig gif0 tunnel <src4> <dst4>" You might want to try adding "-alias" as in: ifconfig gif0 inet6 2001:6f8:900:a5::2 2001:6f8:900:a5::1 prefixlen 128 -alias And you can try to add a route to 'the remote side' using: route add -inet6 2001:6f8:900:a5::1 -prefixlen 128 2001:6f8:900:a5::2
FBSD: failed to add route
[nl] Shadow Hawkins on Sunday, 04 January 2004 15:54:28
I'm having the same problems with the same configuration. I tried your suggestions: ifconfig gif0 inet6 2001:960:2:10f::2 2001:960:2:10f::1 prefixlen 128 -alias Results in: ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address ifconfig gif0 inet6 2001:960:2:10f::2 2001:960:2:10f::1 prefixlen 128 alias Results in: works okay route add -inet6 2001:960:2:10f::1 -prefixlen 128 2001:960:2:10f::2 Results in: route: writing to routing socket: File exists add host 2001:960:2:10f::1: gateway 2001:960:2:10f::2: File exists I still get the kernel messages. Ifconfig gif0 looks like this: gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 tunnel inet 129.125.103.171 --> 213.204.193.2 inet6 fe80::210:a7ff:fe09:664f%gif0 prefixlen 64 scopeid 0x8 inet6 2001:960:2:10f::2 --> 2001:960:2:10f::1 prefixlen 128 Netstat -rn -f inet6 results in: Routing tables Internet6: Destination Gateway Flags Netif Expire default 2001:960:2:10f::1 UGSc gif0 ::1 ::1 UH lo0 2001:960:2:10f::1 2001:960:2:10f::2 UH gif0 2001:960:2:10f::2 link#8 UHL lo0 fe80::%rl0/64 link#1 UC rl0 fe80::210:a7ff:fe09:664f%rl0 00:10:a7:09:66:4f UHL lo0 fe80::%ed0/64 link#2 UC ed0 fe80::4a54:e8ff:fe21:e8ea%ed0 48:54:e8:21:e8:ea UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#4 UHL lo0 fe80::%gif0/64 link#8 UC gif0 fe80::210:a7ff:fe09:664f%gif0 link#8 UHL lo0 ff01::/32 ::1 U lo0 ff02::%rl0/32 link#1 UC rl0 ff02::%ed0/32 link#2 UC ed0 ff02::%lo0/32 ::1 UC lo0 ff02::%gif0/32 link#8 UC gif0
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Sunday, 04 January 2004 16:38:58
Indeed it is 'alias', '-alias' removes the alias ;) Try: ifconfig gif0 inet6 2001:960:2:10f::2 prefixlen 128 alias route add -inet6 2001:960:2:10f::1 -prefixlen 128 2001:960:2:10f::2 route add -inet6 default 2001:960:2:10f::1 I have various FBSD's 4.9-RELEASE running with this and they don't complain, so it should work.
FBSD: failed to add route
[nl] Shadow Hawkins on Sunday, 04 January 2004 17:06:39
Why not: ifconfig gif0 inet6 2001:960:2:10f::2 2001:960:2:10f::1 prefixlen 128 alias as it says in the FAQ? It seems when I use the above, the route: route add -inet6 2001:960:2:10f::1 -prefixlen 128 2001:960:2:10f::2 is automatically added. Or something like that, I'm now using what you said you're using. But the message still seems to occur. I'll wait for a while. I'm on 4.7 RELEASE myself. I waited a while, but I still get the message :(
FBSD: failed to add route
[si] Carmen Sandiego on Monday, 05 January 2004 01:20:43
No success here either.. i used both ways, combining each other.. but no success... that message still occures... :(
FBSD: failed to add route
[si] Carmen Sandiego on Monday, 05 January 2004 23:47:09
I cant get it working... but the message dissapeared if i didn't do the 'route' routine... as soon as i added routes... error is back i tryed different ways from other site,same thing... i dont know but... does it affect this is the machine is acting like a gateway? :? i will just have to disable the tunnel and wait until i figure something out, i hate dealing with this kind of problem :(
FBSD: failed to add route
[nl] Shadow Hawkins on Wednesday, 07 January 2004 06:15:19
Hmm, my machine is a router/gateway also. So maybe it has something to do with it. Unfortunately I can't solve the problem. I have very little knowledge and I hope someone will have a good idea on how to solve it. I don't think it harms really, but the messages are plenty, and my logs are growing fast!
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Wednesday, 07 January 2004 12:08:24
Most people use their endpoint as a router to give the rest of their LAN IPv6 connectivity. You can always edit the source and comment the message away ofcourse ;)
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Wednesday, 07 January 2004 12:06:58
Have you checked google: [http://mail-index.netbsd.org/netbsd-users/2001/08/23/0012.html http://mail-index.netbsd.org/current-users/2000/10/06/0005.html The error seems to happen when configuring two interfaces oin the same prefix.
FBSD: failed to add route
[nl] Shadow Hawkins on Wednesday, 07 January 2004 20:37:25
I googled, but I couldn't find an direct answer. I'm sorry, but I don't really understand it even now. I'm very n00b with ipv6 and with networks. This is what I have: netstat -rn | egrep 2001:960 default 2001:960:2:10f::1 UGSc gif0 2001:960:2:10f::1 2001:960:2:10f::2 UGHS gif0 2001:960:2:10f::2 link#8 UHL lo0 This is a bad thing? What should I change to solve this?
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Wednesday, 07 January 2004 20:52:50
There is nothing wrong with those routes in my opinion.
FBSD: failed to add route
[si] Carmen Sandiego on Thursday, 08 January 2004 11:36:24
What to do then? my netstat -nr is like this (after route add -inet6 default POP-ipv6) Internet6: Destination Gateway Flags Netif Expire default 2001:6f8:900:a5::1 UGSc gif0 ::1 ::1 UH lo0 2001:6f8:900:a5::1 2001:6f8:900:a5::2 UH gif0 2001:6f8:900:a5::2 link#6 UHL lo0
FBSD: failed to add route
[si] Carmen Sandiego on Thursday, 08 January 2004 13:43:16
I solved my problem: I added this to my rc.conf ipv6_enable="YES" ipv6_static_routes="default" ipv6_route_default="default -interface gif0" ipv6_gateway_enable="YES" ipv6_network_interfaces="sis0" =>interface of NIC for internet ipv6_prefix_sis0="MyPrefixOfSubnet" => like 2001:xxx:xxx:1 gif_interfaces="gif0" prefixcmd="YES" gifconfig_gif0="MyIpv4 PopIpv4" And it works like a charm... B-)
FBSD: failed to add route
[nl] Shadow Hawkins on Thursday, 08 January 2004 13:54:52
But... where do you configure your ipv6client address. And there is no need for a ipv6_default_router?
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Thursday, 08 January 2004 14:01:25
This is called unnumbered tunneling and though it works you didn't configure the endpoint of your tunnel, which will cause latency tests to not work and your tunnel to be disabled after credits have been deducted. Next to that if you are using a heartbeat tunnel the local gateway will change and packets will be lost.
FBSD: failed to add route
[si] Carmen Sandiego on Saturday, 10 January 2004 15:24:20
But if i add to rc.conf ifconfig_gif0="inet6 myipv6ednpoint popipv6endpoint" will it be ok then?
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Saturday, 10 January 2004 15:25:22
Try and find out, at least then you have your endpoints configured and you go an IP to which you can use as your gateway.
FBSD: failed to add route
[si] Carmen Sandiego on Saturday, 10 January 2004 15:34:27
if i do this ifconfig_gif0="muipv6 popipv6" when the sistem boots and i do ifconfig i dont'se any 2001:6f8:900:a5::2 -> 2001:6f8:900:a5::1 why is that/
FBSD: failed to add route
[ch] Jeroen Massar SixXS Staff on Saturday, 10 January 2004 15:35:43
Probably because that is not the correct way of setting op tunnels in FreeBSD ? Read the manuals (or scripts)... and find out ;)
FBSD: failed to add route
[si] Carmen Sandiego on Saturday, 10 January 2004 16:14:42
but i already know what it's gonna happen if i do it 'old fashion way'... i'll be at the start again... :P indeed.. im back at the start... same warning.. same sh*t im loosing credits.. woohoo.. and i'm tired... weeeee ;(
FBSD: failed to add route
[si] Carmen Sandiego on Monday, 12 January 2004 00:09:26
I FIXED it.. well.. semi fixed it i edited /usr/src/sys/netinet6/nd6.c and commented out log(LOG_ERR, "nd6_lookup: failed to add route for a " "neighbor(%s), errno=%d\n", ip6_sprintf(addr6), e); I seen some post somewhere.. that in never KAME versions, this error is logged and showed in console... in previous version this error wasn't printed.. so idecided to change this file.. because ipv6 works normaly anyways... Thanks all for replying

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

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