[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: xAP Plug-in for SlimServer beta release
I use the subnet broadcast address eg 192.168.1.255 but I've seen
quite
a few 255.255.255.255
( aside - interestingly Crestron kit will only see broadcast packets on
192.168.1.0 and can't see xAP messages directly ...)
Edward Pearson wrote:
> How do other xAP applications behave in this area?
>
>
------------------------------------------------------------------------
> *From:* xap_automation@xxxxxxx
> [mailto:xap_automation@xxxxxxx] *On
Behalf Of *trash231
> *Sent:* 10 November 2006 15:24
> *To:* xap_automation@xxxxxxx
> *Subject:* [xap_automation] Re: xAP Plug-in for SlimServer beta
> release
>
> One problem I had with the xAP Slimserver is the use of
> 255.255.255.255 as the broadcast. On my network, broadcasts are
> limited to the subnet which you are on. All broadcasts that are
not
> in the subnet (including the 255.255.255.255) are filtered at the
PC.
> This caused the plugin to operate correctly, but no messages being
> seen in the hub. I had to change the above to 192.168.1.255 so
that
> it only broadcasts on the 192.168.1.xxx network.
>
> YMMV as not everyone would have the same type of network setup.
Maybe
> this could be configurable in the options page?
>
> Trash
>
> __._,
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|