On Wednesday 19 November 2003 14:24, Thomas Smith wrote:Well, it's currently a pretty basic setup--no packet filtering, no traffic shaping. It does have two interfaces, though--one unroutable, the other live. (It's stricly a test server to plan our migration from Red Hat to Gentoo.)
I've had Gentoo setup and running on a test server for about a month now and didn't notice any of these errors until I configured Nagios--it immediately started reporting WARNINGs regarding this error.. I've googled for this problem and every body seems to agree that it's an issue with the Kernel but no one has offered a solution. The error I get is:
WARNING: failed to install socket filter
: Protocol not available
This error occurs when PINGing /any/ host. It doesn't happen with every
ping--that is, it occurs after every few responses. It doesn't seem to
be causing any other functionality problems.
I've set up a little Gentoo server at work that I believe experiences exactly the same thing. I'll confirm tomorrow, but for the time being I'll list some details of how it's configured network-wise.
* one interface with multiple IPs * IP fowarding enabled * TCP packets with destination of port 80 redirected to localhost * connection tracking for everything the kernel supports * traffic shaping for both incoming and outgoing traffic
That's all that I can remember at the moment. If you could supply the same thing, we can use the similarities to hopefully track the source of the problem down.
I'm going to investigate the previous post regarding CONFIG_FILTER=y. I'm not quite sure what the poster meant by "It's used for attack filter to any socket, used by the program." or how this option will affect other aspects of the server. If you or anyone can elaborate on this option please do so.
-- [EMAIL PROTECTED] mailing list
