Board index Linux Networking

ping: WARNING: failed to install socket filter : Protocol not available

ping: WARNING: failed to install socket filter : Protocol not available

Post by Matthias Feche » Thu, 18 Apr 2002 05:28:31



Hello!

my system: SuSE 7.3, Kernel 2.4.18, German T-DSL

server:/etc/ppp # rpm -qa | grep ppp
smpppd-0.49-7
ppp-2.4.1-95
server:/etc/ppp #

Since I did an rpm update of ppp and smpppd (standard Version SuSE
7.3-CDs to the Version 2.4.1-95 and 0.49-7) I have the following
problem:

server:/etc/ppp # ping www.heise.de
PING www.heise.de (193.99.144.71) from xxx.xxx.xxx.xxx : 56(84) bytes of
data.
64 bytes from www.heise.de (193.99.144.71): icmp_seq=1 ttl=250
time=106.276 msec
64 bytes from www.heise.de (193.99.144.71): icmp_seq=2 ttl=250
time=65.618 msec
WARNING: failed to install socket filter
: Protocol not available
64 bytes from www.heise.de (193.99.144.71): icmp_seq=3 ttl=250
time=57.614 msec
64 bytes from www.heise.de (193.99.144.71): icmp_seq=4 ttl=250
time=78.779 msec
64 bytes from www.heise.de (193.99.144.71): icmp_seq=5 ttl=250
time=59.363 msec

--- www.heise.de ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4041ms
rtt min/avg/max/mdev = 57.614/73.530/106.276/17.980 ms
server:/etc/ppp #

This warning comes up randomly when I do a ping to any site.
Has anybody an idea how to solve this problem?

CU
Matthias

 
 
 
Top

1. PING: Failed to install socket filter after kernel update

Okay I finally made it through my kernel recompile with iptables 1.2.7a in
there, and it seems to be working (I can do a #iptables -L and it lists my
default chains) but there's about a 10-second delay with anything
network-related now. When I ssh to the box, it used to come up immediately,
now there's the delay. When I lynx to a site, delay. When I ping, I get
useful info, then a delay.

The is the output of a simple ping apple.com:

PING apple.com (17.254.3.183) from 10.1.1.8 : 56(84) bytes of data.
WARNING: failed to install socket filter
: Protocol not available
64 bytes from apple.com (17.254.3.183): icmp_seq=1 ttl=51 time=49.8 ms
64 bytes from apple.com (17.254.3.183): icmp_seq=2 ttl=51 time=50.5 ms
64 bytes from apple.com (17.254.3.183): icmp_seq=3 ttl=51 time=56.7 ms
64 bytes from apple.com (17.254.3.183): icmp_seq=4 ttl=51 time=58.8 ms

--- apple.com ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 15398ms
rtt min/avg/max/mdev = 49.835/53.987/58.830/3.877 ms

Notice the time 15398ms... It comes up after a couple seconds with the
WARNING, then delays about 5 seconds, then spits out the ping info slowly,
even though the return times may be under 10ms.

So what's up with the failing to install socket filter stuff? What did I do
to my kernel? :-)

Machine info: RH 7.3 on a Dell PE 350, with a newly compiled 2.4.19 kernel
and compiled iptables 1.2.7a (tried 1.2.6a with same results). I have
completely removed ipchains.

If anyone wants to see my kernel config file, or some of the flags from it,
lemme know.

Thanks!!
# Nathan

-
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/

2. IBM 8.3 GB Hard disks

3. help: ipfwadm: setsockopt failed: Protocol not available error

4. Clocks for CL5428

5. ipfwadm gives the error: "setsockopt failed: Protocol not available"

6. XAP in slackware doesn't work!!!

7. HELP ! ipfwadm: setsockopt failed: Protocol not available

8. Help! Nvidia GForece 2Go

9. ipfwadm problem? setsockop failed: Protocol not available

10. calling socket protocol family from another socket protocol family ?

11. Netscape warning: accept failed (Protocol error)

12. accept failed (protocol error) warning

13. ping: unknown protocol icmp (yes, /etc/protocols exists)


All times are UTC
Board index