Re: [pupnp-user] Unsupported setsockopt level=0 optname=35

[Nektarios K. P. <npa...@in...>]

Ishay Peled wrote:
> On Jan 16, 2008 10:16 AM, Nektarios K. Papadopoulos
> <npa...@in...> wrote:
>> Ishay Peled wrote:
>>> Hi,
>> Hi,
>> I CC the pupnp-user list and please do the same in any follow up, so other can
>> join in or benefit from the discussion.
>>
>>> I'm writing an application using Scratchbox in Ubuntu linux, it
>>> emulates an ARM processor, but I don't think the scratchbox part is
>>> relevant.
>> I've never used Scratchbox myself so I can't be sure, but it seems like a
>> network configuration issue with QEMU to me. I can't help you fixing it, but I
>> can't tell you that setsockopt is *not* a windows method, it is a POSIX system
>> call available of course in linux.
>>
>> The error message you get corresponds (probably) to upnp/src/ssdp/ssdp_server.c
>> line 937 call:
>>    setsockopt( ssdpSock, IPPROTO_IP, IP_ADD_MEMBERSHIP, ...
>>
>> Multicast must be enabled for the interface you specify (sorry but I can't tell
>> you how to check/ensure this in Scratchbox)
>>
>>> The same thing happens with the examples.
>> Do you have a non-loopback interface in QEMU to try this on ?
>>
>> Have you tried the same examples on your native Ubuntu linux? I'm sure they'll work.
>>
>> I'd also guess that the fact that the shell hangs, instead of returning with
>> "All bad", is also related to the fact that you are running on a simulated
>> environment.
>>
>>
>>>    Thanks,
>>>    Ishay Peled.
>>>
>> You are welcome
>>
>> --
>> nek
>>
> Well, even if it works native it won't solve my problem as this is
> going to be an embedded device, I have to use scratchbox so I can get
> binaries to my device...

IIUC, scratchbox is both a cross compiling toolchain and an emulation
environment (QEMU). I suggested that you use scratchbox for cross compiling but
don't use QEMU for testing (unless you can configure it properly to support
MULTICAST). Test directly in the embedded device. At least this is what I do and
last time I checked it worked fine (on ARM). To be honest never tested 1.6.3,
but the problem you are facing is very basic and nothing changed in that area
for a very long time.

Can you share some more details about linux/processor of the embedded device?
> Ill try to test ssdp_server separately and see if anything comes up,

 From what you've said so far, the problem seems to be in the ability to call 
setsockopt( ssdpSock, IPPROTO_IP, IP_ADD_MEMBERSHIP, ...) in your environment. 
Maybe you can come up with a very simple test case that does just that. If it 
still fails then you can request help on the scratchbox ml/fora how to properly 
configure your emulation environment.

> Ill post again if I get it fixed.
Please do, I'd greatly appreciate it.

>     Thanks,
>     Ishay Peled.

cheers,
nek