Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!news.glorb.com!news-xxxfer.readnews.com!textspool2.readnews.com!news-out.readnews.com!transit3.readnews.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Problem receiving UDP broadcast packets. Date: Wed, 20 Apr 2011 15:32:26 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 26 Message-ID: References: <4dae172e$0$65870$e4fe514c@news.xs4all.nl> <4dae1d82$0$81483$e4fe514c@news.xs4all.nl> NNTP-Posting-Host: dsl.comtrol.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: reader1.panix.com 1303313546 7664 64.122.56.22 (20 Apr 2011 15:32:26 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 20 Apr 2011 15:32:26 +0000 (UTC) User-Agent: slrn/pre0.9.9-102 (Linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:3720 On 2011-04-20, Grant Edwards wrote: > On 2011-04-20, Heiko Wundram wrote: >>> I've thought about the SOCK_RAW option, but the CPU load of looking >>> all received Ethernet packets in user-space would be a big down-side. >> >> Not necessarily: instead of using UDP datagrams to send the data, >> use ethernet datagrams (without any IP/UDP header) with your own >> ethernet-type (there is a range of "local" types that you can use for >> your own local use-case), and then simply create a RAW socket that >> only listens on packets that have the specified ethernet types. We >> use something similar at work for a high-availability application. > > Same here. What I'm working on is a replacement for just such a > protocol. Now that I think of it, I added raw socket support to Python just so I could implement that protocol in Python! [A rather vain attempt to inject some Python content back into the thread.] -- Grant Edwards grant.b.edwards Yow! Awright, which one of at you hid my PENIS ENVY? gmail.com