RE: Setsockopt() api in 2.6 implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, thanks. 

I've been using same file as an example. Problem turned out to be quite
trivial: for some reason, SOL_DCCP was defined differently on user
level. Now everything is fine. I've set service numbers and socket
starts to listen.

B.R.
Vladimir.

>-----Original Message-----
>From: ext Burak Gorkemli [mailto:burakgorkemli@xxxxxxxxx] 
>Sent: 12 September, 2006 15:23
>To: Moltchanov Vladimir (Nokia-NRC/Helsinki)
>Subject: Re:  Setsockopt() api in 2.6 implementation
>
>vladimir.moltchanov@xxxxxxxxx wrote:
>
>>Hi all,
>>
>>Can anybody provide an example of basic steps required under DCCP for 
>>Linux 2.6 implementation to create a simple listening socket?
>>
>>I have:
>>
>>	Sk = socket(AF_INET, SOCK_DCCP, 0);
>>	...
>>	...
>>	Bind();
>>	...
>>	...
>>	Int Buf_len=1400;
>>	Error = setsockopt(sk, SOL_DCCP, 
>DCCP_SOCKOPT_PACKET_SIZE, &Buf_len, 
>>sizeof(Buf_len));
>>
>>Setsockopt() fails with code 92 - (not supported, I believe).
>>Apparently, I never reach dccp setsockopt() implementation. 
>So, what am 
>>I missing?
>>
>>B.R.
>>Vladimir.
>>
>>
>>  
>>
>Vladimir,
>
>I was getting the same error, don't remember why exactly, but 
>the following code works. just look at receive_over_dccp() and 
>init_socket() functions.
>
>The code attached is based upon ttcp_acme.c, so I recommend 
>you to look at  http://wand.net.nz/~iam4/dccp/ttcp_acme.c
>
>BTW, this kind of questions fit better to dccp@xxxxxxxxxxxxxxx
>



[Index of Archives]     [Linux Kernel Development]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]

  Powered by Linux