Re: RFFR

a few features i can think of...... (some may not be possible)


more protocols like appletalk, ipx and 802.11
ability to send collision frames (probably not possible due to hamming 
codes)
random port's (i have been meaning to write a patch..... busy this weekend 
maybe next)
bring the man page back (as much as i love the doxygen stuff a man page 
would still be really useful)
context queues to handle buffer management and timings (e.g. no more 
usleeps between libnet_writes)
name resolution from specified mac + ip addr (would help out a ton when an 
interface hasn;t got an IP.... but probably impossible without.......

a pcap interface + tcp/ip stack capability.... eg all the main funcs would 
be wrapped into a sort of file descriptor that can be read and wrote to 
(eg in terms of data, not frames and packets) All the sequence numbers, 
three way handshakes and such like would be hidden by a higher layer api. 
Eg sending large amounts of data would be handled by libnet opposed to at 
present where each individual packets of the connection setup needs to be 
crafted to send the data.


sorry guys for the dodgy interface patch i posted a while back.... it was 
an old version for one of the rc's for 1.1.1.
Thanks fred for tiding the patch up ;) :)



food for thought

cheers
Ste Jones
networkpenetration.com