OK I "fixed" it. - quote un-quote :) The "can't unmap" thing is not fatal because the logic is that it will continue without doing remapping, so setsockopt multicast will succeed anyway. The fatal part if is unknown socket family thingie. I am not sure if is application bug, but since the application is working under windows, I modified ws_sockaddr_ws2u to force the 'default' switch/case to treat is as WS_AF_INET. This is called brute force coding. ;) It works like on Windows after that. Cheers.
