Some javascript/style in this post has been disabled (
why?)
Hi All,
I have a question about IP address configuration for UPnP
devices. In our use-cases, there’s the strong possibility that
we’ll have a control point with a static IP address assigned to it,
searching for a specific UPnP-compatible device.
This seems to be a problem: if the control point has a static
IP address on a different subnet from the device, then the unicast responses to
the M-SEARCH messages will fail…
This scenario doesn’t seem to be addressed by the UPnP
spec. One solution I thought of is to require the static IP assignment to be in
the 169.254.0.0/16 range. But, if there are other hosts that the control point must
communicate with on a different subnet (e.g. 192.168.1.0/24), this doesn’t
work so well…I suppose it would be possible to allow the control point to
configure the device’s IP address using Actions as well.
Any other thoughts or ideas?
Regards,
Caleb
_______________________________________________
coherence-dev mailing list
[hidden email]
http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
