Routing table vulnerability comparison between two versions and analysis of performance in a scenari


 
Thread Tools Search this Thread
Operating Systems Linux Routing table vulnerability comparison between two versions and analysis of performance in a scenari
# 1  
Old 07-27-2010
Routing table vulnerability comparison between two versions and analysis of performance in a scenari

Hi
Routing tables in a typical linux kernel are implemented using hash data structures. So if the hash table is forced to behave more like a linked list(i.e create chaining) the purpose of using hash is defeated and time complexity increases.
I want to try to assess the performance deterioration in scenario when we above is forced by launching a dos on my lan.Any thoughts are welcome.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Performance analysis sed vs awk

Hi Guys, I've wondered for some time the performance analysis between using sed and awk. say i want to print lines from a very large file. For ex say a file with 100,000 records. i want to print the lines 25,000 to 26,000 i can do so by the following commands: sed -n '25000,26000 p'... (11 Replies)
Discussion started by: Irishboy24
11 Replies

2. Red Hat

What is the best tools for performance data gathering and analysis?

Dear Guru, IHAC who complaint that his CentOS is getting performance issue. I have to help him out of there. Could you please tell me which tools is better to gathering the whole system performance data? -- CPU/Memory/IO(disk & Network)/swap I would like the tools could be... (6 Replies)
Discussion started by: devyfong
6 Replies

3. HP-UX

how to read routing table

Hi all, Could someone please explain to me how I should read this routing table, # netstat -rn Routing tables Destination Gateway Flags Refs Interface Pmtu 127.0.0.1 127.0.0.1 UH 0 lo0 32808 10.222.47.82 10.222.47.82 UH... (3 Replies)
Discussion started by: rachael
3 Replies

4. Linux

Routing Table

Hello, how to make entries in routing table perminent (1 Reply)
Discussion started by: teenasuresh
1 Replies

5. IP Networking

Routing table

Hi all, I am confusing with routing table, i use linux and iptables. i have 1 internet gateway, and 1 router for VPN. here is my network. eth0=192.168.0.1 eth1=192.168.100.1 192.168.0.0/24 --- eth0(Linux Box)eth1 ---(DSL)---Internet | ... (4 Replies)
Discussion started by: blesets
4 Replies

6. IP Networking

routing table

hi all... i need to know, where is locate the routing table on sun solaris, how i can saved the configuration.... because when i restart the server, lost the configuration.... thank you... Regards... (3 Replies)
Discussion started by: chanfle
3 Replies

7. IP Networking

Ip routing table

hi all, how to access ip routing table throgh program, how should i integrate my rip routing table with the ip routing table :) (0 Replies)
Discussion started by: vinodkumar
0 Replies

8. UNIX for Dummies Questions & Answers

not following routing table

Hi, I'm trying to connect to a network device, with the connection follwoing the UNIX routing table we set up. Its to go via a specific network Gateway and out throught a specific Lan card (Lan4). However when trying to conenct it keeps going through Lan3 and will not get to its destination.... (3 Replies)
Discussion started by: nhatch
3 Replies
Login or Register to Ask a Question
hsearch(3)						     Library Functions Manual							hsearch(3)

NAME
hsearch, hcreate, hdestroy, hsearch_r, hcreate_r, hdestroy_r - Manage hash tables LIBRARY
Standard C Library (libc) SYNOPSIS
#include <search.h> ENTRY *hsearch( ENTRY item, ACTION action); int hcreate( size_t nel); void hdestroy(void); int hsearch_r( ENTRY item, ACTION action, ENTRY **target, struct hsearch_data *hsearch_data); int hcreate_r( size_t nel, struct hsearch_data *hsearch_data); void hdestroy_r( struct hsearch_data *hsearch_data); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: hsearch(), hcreate(), hdestroy(): XSH4.2 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
Identifies a structure of the type ENTRY as defined in the search.h header file. It contains two pointers: Points to the comparison key string. Points to any other data associated with the char *key parameter. Pointers to types other than char should be cast as char *. Specifies a value for an ACTION enum type, which indicates what is to be done with an item key when it cannot be found in the hash table. The following two actions can be specified for this parameter: Enter the key specified by the item parameter into the hash table at the appropriate place. When the table is full, a null pointer is returned. Do not enter the item key into the table, but return a null pointer when an item key cannot be found in the hash ta- ble. Specifies an estimate of the maximum number of entries that the hash table will contain. Under some circumstances, the hcre- ate() function may make the hash table larger than specified to obtain mathematically favorable conditions for access to the hash table. Points to the item actually found. Consists of data for the hash table. DESCRIPTION
The hsearch(), hcreate(), and hdestroy() functions are used to manage hash table operations: The hcreate() function initializes the hash table. You must call the hcreate() function before calling the hsearch() function. The hsearch() function searches a hash table. It returns a pointer into a hash table that indicates where a given entry can be found. The hsearch() function uses open addressing with a hash function. The hdestroy() function deletes the hash table. This allows you to start a new hash table because only one table may be active at a time. After the call to hdestroy(), the hash table data should no longer be considered accessible. [Tru64 UNIX] The hsearch_r(), hcreate_r(), and hdestroy_r() functions are reentrant versions of hsearch(), hcreate(), and hdestroy(). Upon successful completion, the hsearch_r() function returns 0 (zero). Upon failure, it returns -1 and sets errno. [Tru64 UNIX] Threads can share hash tables by using the hcreate_r, hsearch_r, and hdestroy_r functions with a common hsearch_data value. To prevent corruption of data when sharing a hash table, locks must be used around calls that use the common hsearch_data value. RETURN VALUES
The hsearch() function returns a null pointer when the action parameter is FIND and the key pointed to by item cannot be found or when the specified action is ENTER and the hash table is full. Upon successful completion, the hcreate() function returns a nonzero value. Otherwise, when sufficient space for the table cannot be allo- cated, the hcreate() function returns a value of 0 (zero). ERRORS
If any of the following conditions occur, the hsearch() function sets errno to the corresponding value: The table is full. [Tru64 UNIX] The search failed. RELATED INFORMATION
Functions: bsearch(3), lsearch(3), tsearch(3), qsort(3) Standards: standards(5) delim off hsearch(3)