New oleg firmware version

[lly]

I'm not sure ecaddict... an m-search is just a udp broadcast so an ip should be resolved by the control point (miniupnpd in this case), setting an ip for the device shouldn't make a difference

M-SEARCH has a multicast target address, but sender(source) address in packet is?

[wpte]

M-SEARCH has a multicast target address, but sender(source) address in packet is?

Yes, the ip-endpoint is set at 255.255.255.255:1900
then an ipv4 socket is created with udp and datagram settings.

then twonky sends the m-search message 3 times (according to upnp spec)
and reads the responses back.

It's importand that if you have multiple devices on 1 host that either way you solve the problem of multiple sockets on 1 interface with a root device (which could act like a sort of switch) or like most programs do because of compatebility issues: do not bound on the socket but simply send and receive data.

In my programming I've never had to use the ip of the device... well... only for serving the service, but not for m-searches and responses
In wireshark the ip of the twonky m-search just popped up as my router ip, as expected.