Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.030
X-Spam-Evidence: '*H*': 0.94; '*S*': 0.00; 'wed,': 0.04; 'subject:Problem': 0.09; 'am,': 0.14; 'wrote:': 0.14; 'abused': 0.16; 'picks': 0.16; 'socket.': 0.16; 'protocol': 0.16; 'things.': 0.16; "wouldn't": 0.18; 'device': 0.20; 'header:In-Reply-To:1': 0.22; 'discovery': 0.23; 'received:209.85.214.174': 0.23; 'received:mail-iw0-f174.google.com': 0.23; 'somehow': 0.23; 'properly': 0.25; 'chris': 0.27; 'message-id:@mail.gmail.com': 0.28; "doesn't": 0.28; 'looks': 0.28; 'noticed': 0.29; 'be.': 0.29; "can't": 0.31; 'to:addr:python-list': 0.32; "i've": 0.33; 'configured': 0.33; 'someone': 0.33; 'change': 0.34; 'correctly': 0.35; 'that,': 0.35; 'change,': 0.35; 'stuck': 0.35; 'hoping': 0.36; 'doing': 0.36; 'data': 0.37; 'raw': 0.37; 'should': 0.37; 'received:209.85': 0.37; '20,': 0.38; 'apr': 0.38; 'be,': 0.38; 'commands': 0.38; 'received:google.com': 0.38; 'but': 0.38; 'pretty': 0.38; 'received:209.85.214': 0.39; 'to:addr:python.org': 0.39; 'could': 0.39; 'received:209': 0.39; 'whatever': 0.39; 'would': 0.40; "it's": 0.40; 'header:Received:5': 0.40; 'skip:2 10': 0.61; '2011': 0.62; 'devices': 0.64; 'stupid': 0.84; 'edwards': 0.91
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=lhqxo0o0VzUvCOsg9+pqaobbP+nSLXWSbSn/jb0mtlM=; b=vN+A+IBmfGzO+ayzLnQ3gmocUhSZZ4Jch2zd8RvCimTh1sTA1dbk+tR8OikWnpkSeh L7sDfwJQjkKA4uuuImcqBRFD3YYGguUNYXWJISdoLcEVqyvCnteT3LaD27wOkalNxzx7 NVQZVRypAA8eHVkav8dVEh+QfVGp0RpRC/Vlk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=hkWVhN0CgrddmAGQm9qvlMqkJl8atxrqGsc0ts/znXZ4qi9Tc7EgTSHD3qRAL7I7an TLVviFF2ov+1ekVmYfYMxXQPoguKD8S/3ZiFYkrt+8zVZdYAuEB0hnnzWOkVluurVcaR yjgCW0BFwQHqYhHhExEauRi1+CLml/iLokXEg=
MIME-Version: 1.0
In-Reply-To: <iolc32$luj$1@reader1.panix.com>
References: <iol1tv$8dn$1@reader1.panix.com> <4dae172e$0$65870$e4fe514c@news.xs4all.nl> <iol5dm$rdb$2@reader1.panix.com> <4dae1d82$0$81483$e4fe514c@news.xs4all.nl> <mailman.592.1303257124.9059.python-list@python.org> <iol875$ah2$3@reader1.panix.com> <mailman.596.1303260785.9059.python-list@python.org> <iolc32$luj$1@reader1.panix.com>
Date: Wed, 20 Apr 2011 11:24:35 +1000
Subject: Re: Problem receiving UDP broadcast packets.
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.598.1303262678.9059.python-list@python.org>
Lines: 24
NNTP-Posting-Host: 82.94.164.166
X-Trace: 1303262678 news.xs4all.nl 81473 [::ffff:82.94.164.166]:49267
X-Complaints-To: abuse@xs4all.nl
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:3626

On Wed, Apr 20, 2011 at 11:15 AM, Grant Edwards <invalid@invalid.invalid> w=
rote:
>> Or can you simply use a stupid netmask like /1 that picks up all the
>> IP ranges? That way, the source-IP check wouldn't fail.
>
> That would require that the device somehow knows that it's not
> configured correctly and should change the netmask to /1. =A0The device
> doesn't have any way to know that, and it must respond to the
> discovery commands both before and after it's properly configured.

Was hoping that you could make such a change _only_ on the computer
that's receiving the data - that way it's only one change, the devices
don't need any tweaking. But if it can't be, it can't be.

> I've reread the protocol documentation and noticed that the device has
> to respond not only to broadcasts to 255.255.255.255 but also to
> subnet broadcasts send to subnets it's not on. =A0That pretty much
> clinches the requirement to use a raw socket. :/

Sounds to me like someone majorly abused IP to do weird things. Looks
like you're stuck doing the same weirdness, in whatever way you can
manage :| Sorry.

Chris Angelico