05-06-2007
Hi
Is there ne other way i can use the foll socket call in kernel 2.6.18 without getting the error message saying "make sure CONFIG_PACKET and CONFIG_FILTER is enabled in the kernel" :
sock = socket(PF_PACKET, SOCK_RAW, htons((short)ETH_P_ALL)
Thanks
8 More Discussions You Might Find Interesting
1. IP Networking
Hi There,
Suppoose we have configured logical Interface 2.2.2.2 on a server with Primary IP 1.1.1.1.
Now when I am sending a packet from this server, is it possible to make receiver assume that this packet has come from IP 2.2.2.2 and not 1.1.1.1
I think it is possibl using RAW sockets??? but... (1 Reply)
Discussion started by: Ankit_Jain
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
3. Programming
Hi all,
On the server side, one socket is used for listening, the others are used for communicating with the client.
My question is: if i want to set option for socket, which socket should be set on?
If either can be set, what's the different?
Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies
4. UNIX for Advanced & Expert Users
To create RAW socket in Unix/Linux why should one have root permissions?
Any other work around to create raw sockets in Unix/Linux using a normal login id? Since I don't have super user credentials and I want to create RAW sockets.
Let me know if you are aware of any work around. (3 Replies)
Discussion started by: anilgurwara
3 Replies
5. Programming
Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct...
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <string.h>
#include... (3 Replies)
Discussion started by: cyler
3 Replies
6. Programming
Dear Experts,
i am compiling my code in suse 4.1 which is compiling fine,
but at runtime it is showing me for socket programming error no 88
as i searched in errno.h it is telling me socket operation on non socket,
what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies
7. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
8. Programming
Hi,
I have the requirement to sniff packets from
the Ethernet card on my Linux machine and
process it and feed it to a RANAP protocol stack.
So far I have written the raw packet sniffer
and successfully sniffing packets and do little
processing. However, for huge number of packets ... (9 Replies)
Discussion started by: rstnsrr
9 Replies
LEARN ABOUT DEBIAN
gd_reference
gd_reference(3) GETDATA gd_reference(3)
NAME
gd_reference -- retrieve or set the reference field for a dirfile
SYNOPSIS
#include <getdata.h>
const char *gd_reference(DIRFILE *dirfile, const char *field_code);
DESCRIPTION
The gd_reference() function sets or retrieves the reference field (see dirfile(5)) associated with the dirfile specified by dirfile. If
the field_code argument is non-NULL, the reference field for the dirfile will be set to the field specified. If field_code is NULL, the
reference field is not modified. The field code should refer to a RAW field, and may not contain a representation suffix.
RETURN VALUE
On success, gd_reference() returns the field code of the dirfile's reference field, which will be field_code, if field_code is non-NULL.
If no RAW fields are defined in the dirfile, this function will return NULL, without raising an error. On error, NULL is returned and the
dirfile error is set to a non-zero error value. Possible error values are:
GD_E_ACCMODE
The specified dirfile was opened read-only.
GD_E_ALLOC
The library was unable to allocate memory.
GD_E_BAD_CODE
The field specified by field_code was not found.
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_BAD_FIELD_TYPE
The field specified by field_code was not a RAW field.
GD_E_PROTECTED
The metadata of the primary format specification fragment (the file named format in the root dirfile directory) was protected from
change.
The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from
a call to gd_error_string(3).
SEE ALSO
gd_metaflush(3), gd_open(3), gd_error(3), gd_error_string(3), dirfile(5), dirfile-format(5)
Version 0.7.0 20 July 2010 gd_reference(3)