> Hello,
>
> I have compiled the iproute2 package and am running on my own built
kernel.
> The distribution is homegrown and most everything works except for
> networking functions. I cannot get the "ip" command to function correctly,
> >from the dump it appears to not be able to send data on a previously
opened
> socket but I am not sure why. Is this a problem with the kernel? I have
used
> my own "ip" command that I built and one from linuxppc.org and both
exhibit
> the same behaviour. Does anyone know what is causing this?
>
>
############################################################################
> #
> #Output from running "ip link"
> command############################################
>
############################################################################
> #
>
> / # ip link
> Cannot send dump request: Connection refused
>
>From http://snafu.freedom.org/linux2.2/docs/ip-cref/ip-cref.html
The most common mistakes are:
1. Netlink is not configured in the kernel. The message is:
Cannot open netlink socket: Invalid value
2. RTNETLINK is not configured in the kernel. In this case one of the
following messages may be printed, depending on the command:
Cannot talk to rtnetlink: Connection refused
Cannot send dump request: Connection refused <------ Here's your
problem...
3. Option CONFIG_IP_MULTIPLE_TABLES was not selected when configuring
kernel. In this case any attempt to use command ip rule will fail, f.e.
kuznet@kaiser $ ip rule list
RTNETLINK error: Invalid argument
dump terminated
check your kernel I think
Eduardo
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
