Ping ping: sendmsg: Operation not permitted



  • 1. htb and kernel version
    MAtB < XXXX@XXXXX.COM > wrote in news: XXXX@XXXXX.COM : Problem fixed: i was using an older version of tc.
  • 2. Redhat 9 Networking Problems
    Hi all! I have been playing around with Redhat 9.0 for over a week now trying to get my Microsoft MN-510 Wireless USB Adapter working. Today I finally (after literally hours and hours of searching through newsgroups and web pages) got it to work...kind of. I am running to computers, 1 w/Win XP Pro and the second w/dual boot Win 2000 Pro and Redhat 9.0. Everything works perfect through Windows. After all my hard work I am now able to ping both pcs, but that is it through the terminal. I am running Mediacom Cable internet through a Microsoft MN-500 Wireless Base Station. I am not sure what I am doing wrong. I cannot access the internet. That is really all I am worried about right now. I know the USB adapter uses the Prism2.5 chipset. So that was the driver I used. Is there anybody that can help me? What do you need to know? Any help would be greatly appreciated. Thanks!!!
  • 3. denying CONNECT() in httpd.conf
    i have been hit by a spammer using my server as a remailer. when i run the command: grep CONNECT /var/log/http/access_log i get the following output: - - [01/Jul/2003:05:58:14 -0400] "CONNECT HTTP/1.0" 302 0 "-" "-" so i'm going to assume that the offender is (or someone using their server as a remailer to my server). so if i put the following in httpd.conf: Deny from would this deny anything from this address from exploiting the CONNECT() of apache (using version 1.3.27-1.2)? thanks for any help. XXXX@XXXXX.COM

Ping ping: sendmsg: Operation not permitted

Postby » Sun, 22 Jan 2006 01:31:18 GMT

When I try: ping
I receive: ping: sendmsg: Operation not permitted
Does anyone know a possible reason for this behaviour?
I'm using Ubuntu 5.10 on switched LAN. Is it possible that my LAN
router doesn't support multicast?

-- mario

Re: Ping ping: sendmsg: Operation not permitted

Postby Steve Horsley » Sun, 22 Jan 2006 02:13:41 GMT

It works for me. With Ethereal, I can see the packets going out 
(Ethernet to a 4-port switch). Oddly, I can see my router 
answering (in Ethereal) but the ping command says timeout. This 
is also on Ubuntu 5.10, so I don't know why you can't do it. Are 
you running a firewall?

Re: Ping ping: sendmsg: Operation not permitted

Postby prg » Sun, 22 Jan 2006 03:01:00 GMT

Probably because the computers/routers know that this makes _no_sense_

The multicast address space is used to assign IPs to multicast
_groups_, ie., that's how a particular multicast stream is identified.
It is _not_ assigned_ to any particular _host_, so just what would you
expect from pinging such an address?

The _source_ of a multicast stream retains the _unicast_ (assigned)
host address of the host originating the stream.  If you are trying to
ping that host, you will need to ping its unicast IP address, _not_ the
group address.  BTW, it is bad form to burden multicast sources with
unnecessary traffic.  Even ping -c1 should be used with discretion and
for good reason.


Re: Ping ping: sendmsg: Operation not permitted

Postby Paul Black » Tue, 24 Jan 2006 17:59:19 GMT

Why not?

How is this different to pinging a broadcast address?


Re: Ping ping: sendmsg: Operation not permitted

Postby prg » Wed, 25 Jan 2006 12:47:37 GMT

I confess to being a bit over dramatic :-)  And harried and hurried
these past two weeks.

I'm pretty sure the OP was trying to _find_ a multicast router and this
method is very unreliable in my experience.  It depends on the router
_joining_ the multicast group (all routers) but that is not a
requirement of the spec.  In fact, it is one of the weakest "shoulds"
that you'll run across.  Especially on larger switched networks, it is
not uncommon for the _switch_ to drop such pings.  IGMP and the
multicast routing protocols have a much better discovery/query
mechanism anyway.  So no ping response to is not conclusive
unless you know _beforehand_ that it should/will respond.

In the OP's case, the returned message is from a firewall rule or acl
perhaps.  Multicast does not send back these sorts of messages.

Since you can't get beyond your local link without a multicast router
on the link, you just try to join the group you're interested in, and
if you think you're not having luck, then contact your sysadmin.  Many
places have pretty strict requirments for joining multicast groups
beyond a few simple ones like NTP.  Many only allow local lan or wan
multicasting and block all outside sources.  So you might find you have
a mulicast router on your link, but it does not forward the group
you're interested in.

You also bring up a point about broadcast pings and, indeed, they are
similar/related.  In fact the mish mash variety of broadcast pings
combined with the use of multicast pings is why some places just
drop/ignore/block and otherwise hinder the use of pings.  And we won't
mention some of the OS peculiarities/quirks/bugs surrounding
broadcast/multicast pings.

But, if everyone implemented a requirement that multicast routers join then we would have different story perhaps.  BTW, even hosts
joining 224.0.01 (all hosts) is not a requirement but at least it is a
convention that just about all nic drivers/OSes observe, IME.

Multicast is a bear and I hope I've not confused what is already a
confusing pile of incomplete specs.  That's why the fans of
multicasting push so hard for ipv6 -- it clears/solves many of the
present ipv4 ambiguities.


Similar Threads: sendto: Operation not permitted

On 2005-03-14, Kevin Brown < XXXX@XXXXX.COM > wrote:
> those pages I get a daunting "ping: sendto: Operation not permitted" 
> Every one in ten pings do make it back though, but the other nine give 
> me that error message.

The "Operation not permitted" is usually due to a firewall misconfiguration
or a non-completely working network card. It happens to me from time to
time when one of my VPN is busted (virtual interface stopped working),
usually taking down the virtual NIC and restarting it fixes the problem.

The fact that you said one in ten goes trought make me think of something
more hardware related. 


The three "R"s of Microsoft support: Retry Reboot Reinstall-- Mark Atwood
You forgot one: Repeat-- Lars Balker Rasmussen

2.Can't use internal network after dialup modem is used -- get ping: sendto: Operation not permitted

3.Kernel upgrade -> no network access (ping: sendmsg: Operation not permitted)

Dear all,

I have no network access following a kernel upgrade... I have upgraded
from 2.6.11-1.1369_FC4 to 2.6.17-1.2142_FC4. When I boot using the new
kernel X-server (graphics thing) fails, this isn't a problem I know how
to resolve this (I think). Once boot has completed I am able to login
but cannot access the network. When I try to ping or I get:

 ping: sendmsg: Operation not permitted

Being a complete newbie when it comes to these things I have absolutely
no idea how to resolve the issue. Any suggestions? I have edited my
grub.conf for the meantime so I boot the old kernel.



4.Ping from cron not having same effect as ping from console

I'm running a RedHat Enterprise 2.1 server as a group development
platform.  We're having some network problems which are being worked
on, but right now I need a workaround.  The problem is that this
server drops off of the network a couple of times a day.  I've found
that if I just ping another server from that server it comes back on
the network, everybody can see it and everything is fine.

To keep the server on the network I set up a cron job to ping another
server every two minutes.  I can see this ping running every two
minutes with "ps -e | grep ping".  However, the machine still drops
off of the network.  When the server drops off of the network I wait
until I see the cron ping as above and then verify that it is still
off of the network.  So the cron ping doesn't get the machine back on
the network.  Then I do a ping from a console and the server comes
back on the network.

For some reason the cron ping doesn't have the same effect that a ping
from the console does.  The crontab ping entry is by the same user
that I am logged in as when I do the ping from the console.

Anyone have any suggestions?  Why does a ping from the console have a
different effect than a ping from cron.

5.Some services working but can't ping (not ping-able)

6. Windows ping and Linux ping command?

7. Strange network problems - pings to host are fine, pings from host fail

8. HP-UX "ping -i" vs. Linux "ping -I"

Return to linux


Who is online

Users browsing this forum: No registered users and 58 guest