Problem with routing in the IPv6 stack

Problem with routing in the IPv6 stack

Post by Frank Victor Fisch » Thu, 22 May 2003 00:30:17



Hello out there,

I have encountered the following error message when trying to set up a
new entry in the IPv6 routing table with the command "ip -6 route add":

RTNETLINK answers: Cannot allocate memory

This has happened after I have had a working IPv6 configuration for
several days, and the error message is independent from the interface on
which I am trying to establish the route on.

No information at all has been recorded in the system logs by the
kernel, however I have straced the command which did not reveal any
useful information either. I backed up the results of the strace as well
as the /proc/net/ and /proc/sys/net/ trees, along with the ifconfig.

This occured the following platform:
AMD Duron 800 with 256 MB 133 MHz SDR-SDRAM
vanilla linux kernel 2.4.20 patches with XFS 1.2 and IPsec 1.98b.

I am not subscribed to the list so it would be most helpful if you
included me in the CC: list.

Thanks in advance,

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

Problem with routing in the IPv6 stack

Post by FORT Davi » Thu, 22 May 2003 12:20:05



>Hello out there,

>I have encountered the following error message when trying to set up a
>new entry in the IPv6 routing table with the command "ip -6 route add":

>RTNETLINK answers: Cannot allocate memory

>This has happened after I have had a working IPv6 configuration for
>several days, and the error message is independent from the interface on
>which I am trying to establish the route on.

>No information at all has been recorded in the system logs by the
>kernel, however I have straced the command which did not reveal any
>useful information either. I backed up the results of the strace as well
>as the /proc/net/ and /proc/sys/net/ trees, along with the ifconfig.

>This occured the following platform:
>AMD Duron 800 with 256 MB 133 MHz SDR-SDRAM
>vanilla linux kernel 2.4.20 patches with XFS 1.2 and IPsec 1.98b.

>I am not subscribed to the list so it would be most helpful if you
>included me in the CC: list.

>Thanks in advance,

>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

I have the same message on my firewall with USAGI when the route to add
already exists. This
is when changing routes associated with an ipv6 tunnel, but the error
looks very related. This
may be system call that doesn't set properly errno, or ip which could be
buggy.

My 2 euro cents.

--
%------ -- This was sent by Djinn running Linux 2.4.21-rc1 -- ------------%

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

Problem with routing in the IPv6 stack

Post by Robert Olsso » Sat, 24 May 2003 11:20:12


Quote:Frank Victor Fischer writes:

 > I have encountered the following error message when trying to set up a
 > new entry in the IPv6 routing table with the command "ip -6 route add":
 >
 > RTNETLINK answers: Cannot allocate memory
 >
 > This has happened after I have had a working IPv6 configuration for
 > several days, and the error message is independent from the interface on
 > which I am trying to establish the route on.
 >
 > vanilla linux kernel 2.4.20 patches with XFS 1.2 and IPsec 1.98b.

 I've heard about this on 2.5.66 as well. /proc/slabinfo can give some clues.

 Cheers.

                                                        --ro
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. IPv6 and fec0::/64 network route - why did I have to manually add this route?

K ... I FINALLY got my Solaris 8 machine to talk IPv6 to a OpenBSD 2.9
system using site-local addressing.  How?  I had to MANUALLY add the
fec0::/64 network route.  Now the machine can talk via link-local
(which they already could) and site-local addressing.

route add -interface -inet6 fec0::/64 fec0::161

My question is why did I have to add the site-local network route ?
Shouldn't something in /etc/rc2.d/S69inet already do that for me or
maybe /usr/lib/inet/in.ndpd or maybe /usr/lib/inet/in.ripngd ?

Any thoughts appreciated.

-
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill

2. DLT tape drive problem in Solaris 2.6

3. pf: ipv6 route-to (source-based routing)

4. Help with modem

5. Most likely a very simple question - IPv6 problems - route

6. Double entries in /etc/passwd

7. IPv6 radvd, default route and forwarding problem

8. chat -v

9. IPv6 Routing Problem

10. problem with IPv6 host entry in routing table

11. system problem with not used ipv6 module and routing table , alpha machine kernel 2.2.19

12. Ipv6 routing problem

13. IPv6 problem: Routes aren't deleted after expiry / Source address selection