Re: sendto() giving EPERM outside a jail

On Wednesday 28 March 2007 10:54, Steve Watt wrote:
} I guess it would be nice if the man page(s) mentioned that a firewall
could } cause EPERM. I have seen it before with other apps but the sendto()
confused } me.

It's one of those unpleasant interactions between pluggable subsystems,
so it's a bit tough to document -- there are various different firewalls
available, after all.

True, but it doesn't matter which firewall you're using, the result is the
same :)

} It doesn't say anything about EPERM.

If you're sending broadcast broadcast or multicast datagrams, you need
to set the SO_BROADCAST socket option, as well.

Ahh, understood.

Still, it seems to work without that - the sendto() call works fine now I have
explicitly allowed multicast.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

Attachment: pgpobre2DLqIa.pgp
Description: PGP signature