[PD] netsend (UDP): cannot connect to 255.255.255.255

[Hans-Christoph Steiner]

They have been (re?)enabled in 0.43

.hc

On Sep 12, 2010, at 9:41 AM, Andy Farnell wrote:

>
>
>
>
> Broadcast addresses were disabled in [netsend], quite a
> while ago IIRC.
>
>
>
>
> On Sun, 12 Sep 2010 15:09:20 +0200
> Matteo Sisti Sette <matteosistisette at gmail.com> wrote:
>
>> Hi,
>>
>> In Windows, I've always used "connect 255.255.255.255 (someport)"  
>> with a
>> [netsend 1] to broadcast packets to the whole local network to a  
>> given port.
>>
>> Any [netreceive (someport) 1] on the same network and/or the same
>> machine could receive all packets sent with the netsend above.
>>
>> However, I am trying this in Linux (ubuntu) now and it doesn't work.
>>
>> The [netsend 1] object won't even connect (the outlet doesn't  
>> output a
>> 1) but it won't complain either: it says "connecting to port 5555"  
>> but
>> doesn't print any error message when failing to connect.
>> It does print error messages ("netsend: not connected") when trying  
>> to
>> send messages.
>>
>> I know I can use the specific address of the network, e.g.
>> 192.168.1.255, but this won't work if I use the patch on a network  
>> with
>> a different address other than 192.168.1.XXX
>>
>> Why doesn't 255.255.255.255 work and is there a workaround?
>>
>> thanks
>> m.
>>
>> _______________________________________________
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>
>
> -- 
> Andy Farnell <padawan12 at obiwannabe.co.uk>
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list



----------------------------------------------------------------------------

Computer science is no more related to the computer than astronomy is  
related to the telescope.      -Edsger Dykstra