Re: UDP catchall
- From: Matus Harvan <mharvan@xxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 02:15:16 +0100
On Mon, Oct 29, 2007 at 07:49:47PM +0000, Bruce M. Simpson wrote:
Brooks Davis wrote:
While I think this idea has some merit, I think we specifically want
the current wildcard ability to allow for a system that requires
minimal configuration. The problem with a range is that it doesn't
allow disjoint sets and it requires that if you really do want all the
ports you need to produce a list of currently allocated ports to avoid
allocating. A more (over)engineered solution holds some attraction, but
I'm not yet convinced the fact that it could exist precludes the current
implementation.
Actually I concur with you on this point, based solely on the disjoint sets
point.
Another vector of attack would be to put the relay functionality into PF,
which can do the packet matching. However this of course suffers from the
problem that if you just want a plain old UDP socket for mtund, you won't
get that unless you go to the inpcb layer anyway.
But who says mtund needs to use sockets for its traffic relay? There is
definite appeal in *not* doing it in the socket layer at all -- an
adaptation of pf's log socket may suffice...
My initial understanding of a raw IP socket was that I could simply
receive any packet for a particular protocol. This almost works for
ICMP, but TCP and UDP don't seem to be supported. Hence, I have
perceived the patch also as a natural extension of the idea of a raw
IP socket for the UDP protocol.
Matus
Attachment:
pgpyUtM0EWqoa.pgp
Description: PGP signature
- References:
- Re: UDP catchall
- From: Matus Harvan
- Re: UDP catchall
- From: Bruce M. Simpson
- Re: UDP catchall
- From: Brooks Davis
- Re: UDP catchall
- From: Bruce M. Simpson
- Re: UDP catchall
- Prev by Date: Re: TCP listenall
- Next by Date: Re: UDP catchall
- Previous by thread: Re: UDP catchall
- Next by thread: Re: UDP catchall
- Index(es):
Relevant Pages
- Re: SetSockOpt with SO_REUSEADDR parameter
... So I create multiple UDP sockets with the same port to send data. ...
happening is that you are throwing away the old socket and replacing it with the new ...
When the second client is connecting to server, I still get the error code ... (microsoft.public.vc.mfc) - Re: Socket connect vs. bind? What is the difference
... Actually, if you're doing UDP Multicast, you don't need to connect. ... to call
Connect to establish a TCP connection to the remote IPEndPoint. ... is connectionless,
so it isn't even necessary to establish a connection to ... It can be set with an overload of
the Socket constructor. ... (microsoft.public.dotnet.languages.csharp) - Re: Strange UDP Socket problem
... You can catch that exception and move on. ... never get any udp reply
back to post an exception. ... >> I suspect you would get the same response if you
used one thread to send ... >> thread on same socket. ... (microsoft.public.dotnet.languages.csharp) - Re: UDP performance.
... issue - it has traditionally been the source of statements like "FreeBSD's threading implementation
is weak/bad/broken". ... And these days ISC can't consciously recommend FreeBSD for use on high-traffic
DNS servers because UDP performance has gone downhill since 5.x. ... Dinesh>
affect voip applications/servers such as asterisk when run on ... One of the problems ISC diagnosed
had to do with the highly unusual workload pattern of UDP: many different threads simultaneously sending
using a single socket leading to unnecessary socket buffer contention. ... (freebsd-performance) - Re: UDP catchall
... minimal configuration. ... ports you need to produce a list of currently
allocated ports to avoid ... Actually I concur with you on this point, based solely on the disjoint
sets ... adaptation of pf's log socket may suffice... ... (freebsd-net)