05-05-2007
RAW socket and CONFIG_FILTER
Hi,
Im doin a project on DHCp client-server setup. i have to use RAW sockets in the code for this. The call PF_PACKET, SOCK_RAW as the first two arguments. The code compiles but when i try to start the Dhcp client, I get an error saying "Make sure CONFIG_PACKET and CONFIG_FILTER is enabled". I tried to build the kernel using a source tree. I found CONFIG_PACKET=y but didnt find CONFIG_FILTER. So i added a line CONFIG_FILTER=y. I got the foll error
Heres a full snapshot of the error :
bash-3.1# make
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/i386/Kconfig
.config:384:warning: trying to assign nonexistent symbol FILTER
#
# configuration written to .config
#
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-i386
ln: creating symbolic link `include/asm' to `asm-i386': Operation not permitted
make: *** [include/asm] Error 1
bash-3.1#
How else can i add it? Is there ne other way out. Im using Fedora 6 with 2.6.20 source tree.
Pls help
Thanks in advance
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_delete
gd_delete(3) GETDATA gd_delete(3)
NAME
gd_delete -- remove a field from a dirfile
SYNOPSIS
#include <getdata.h>
int gd_delete(DIRFILE *dirfile, const char *field_code, int flags);
DESCRIPTION
The gd_delete() function attempts to delete the field specified by field_code in the dirfile specified by dirfile. The field_code should
not contain a representation suffix.
The flags argument influences how the deletion attempt occurs. It may be zero, for the default behaviour, or else one or more of the fol-
lowing flags, bitwise or'd together:
GD_DEL_DATA
If the field to be deleted is a RAW field, also delete the binary data file associated with it. If field_code specified a RAW
field and this flag is not specified, the field will still be deleted but the binary file will be left untouched.
GD_DEL_DEREF
If the field to be deleted is a CONST or CARRAY field which is used as a parameter in the specification of other fields, resolve
these other fields dependence on the deleted field by replacing instances of field_code in their field specifications with the val-
ue of the scalar field.
GD_DEL_FORCE
Delete the indicated field, even if it is used in the specification of other fields, either as a input for a derived vector field
or as a scalar parameter in a field specification.
GD_DEL_META
If the field to be deleted has metafields attached to it, attempt to delete those, too. If the field has metafields and this flag
is not specified, the call will fail with the GD_E_DELETE error.
RETURN VALUE
On successful deletion, zero is returned. On error, -1 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 in the database.
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_DELETE
The attempt to delete the field failed. Either the specified field is used in the specification of other fields and GD_DEL_FORCE
or GD_DEL_DEREF was not specified, or it has metafields and GD_DEL_META was not specified.
GD_E_INTERNAL_ERROR
An internal error occurred in the library while trying to perform the task. This indicates a bug in the library. Please report
the incident to the GetData developers.
GD_E_PROTECTED
The metadata of the fragment containing the field was protected from change. Or, the deletion of the binary data file associated
with a RAW field was attempted and the data of the fragment was protected.
GD_E_RAW_IO
An error occurred while trying to close or delete the binary file associated with a RAW field.
GD_E_UNKNOWN_ENCODING
The GD_DEL_DATA flag was given but the encoding scheme of the indicated format specification fragment is not known to the library.
As a result, the library was unable to delete the binary file associated with a RAW field.
GD_E_UNSUPPORTED
The GD_DEL_DATA flag was given but the encoding scheme of the indicated format specification fragment does not support deleting the
binary file associated with a RAW field.
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_open(3), gd_close(3), gd_error(3), gd_error_string(3), gd_metaflush(3)
Version 0.7.0 3 November 2010 gd_delete(3)