A quick round up for the 3 or 4 humans who watch the systhread rep...
nmapwt
The main tool I use for regression testing netward is
nmap; basically I like to loop and fire off a
variety of different scans using a shell loop like:
while true; do nmap -sS; nmap -sN; nmap -sX; nmap -P0; done
The problem of course is I got sick of writing them and even more sick of
watching of them; don't get me wrong I think nmap is one of
the most siginificant and coolest pieces of software in the world - but it
gets old when I know what I am going to see (over and over again) - kind
of like a James Bond Marathon. The solution?- script it - I wrote a thin
wrapper with levels
of scanning and a loop counter (to run forever
just send a -1). Here is an example run:
sudo ./nmapwt -c 2 -l 1 -e vela.aesun.net Starting Nmap 4.62 ( http://nmap.org ) at 2008-11-08 19:15 EST ...
The levels and options are explained in the usage message:
usage: nmapwt [[option][option arg]] usage: nmapwt [[-c count][-l level][-s host_or_ip_2scan]-u] options: -c int Loop the scan int times -l int Scan level of 1,2 or 3 -e expr Scan expression (see nmap man page) -q Close STDOUT -u Print usage message and exit -v Tell nmap to be verbose levels: 0: no options, default (might as well type nmap :) 1: TCP SYN/Connect/ACK/Window scans 2: TCP NULL, FIN and Xmas, zombie, FTP relay 3: Fingerprint and UDP
wakessAwhile ago I ran into a real interesting problem: I had moved some shared IPs on a linux host from one system to another - the changed addresses however refused to be recognized by a content switch that I did not have access to. The fix I discovered was to scan the content switch and spoof the source address with each shared address. I had to do the same thing a few weeks later... time for a script. Here is an example invocation:
wakess -i fn0 -a "192.168.43.1 192.168.43.2 192.168.43.3"
Wakess automatically closes STDOUT and STDERR so if
it doesn't work - might want to turn them back on. Wakess can easily be
wrapped in the shell too if you don't like typing those pesky IPs a lot:
for n in 1 2 3 ; do wakess -i fn0 192.168.43.$n ; done
etu Build Notes
For those who don't know it, the enlightenment project is now exclusively
hosted under a subversion server. I - of course - was not aware of this. As
it turns out the epeg libraries have been superceded by
something else
(I haven't jumped in and looked yet to see where it was
moved to). In any case - etu still works but under the svn trunk
epeg was moved to e/trunk/OLD/epeg (for the time
being at least). I am looking at updating etu.
netward Update
Last week the halloween release of netward rolled out
just fine (I had one question...). The big todo was refactoring
and that is still in progress. Another item was whether or not to validate
with libpcap-1.0.0. Item one is still underway item two is a
defintie yes. The new version of libpcap has a few speed
enhancements that might make it worth the time to investigate. I started
netward in May of 2008 and planned on having a
1.0 release within a year. So I am a little bit ahead of
schedule. That said - see below for what will slow up the first production
release ... however the current incarnation is pretty
much what the 1.0 release will be as far as using the program
goes. Only internal changes and libpcap testing are taking
place between 0.9 and 1.0.
It is November and two years since I did the last all site review of
content
... a task I both am happy with the results but so woefully
dread to do - I put off more than my annual physical. In any case it needs to get done
which means everything else will more or less grind to a halt until
December (the holidays of course....) The process itself is simple:
review each and every new text published within the last two years and every other
page for technical innacuracies, grammar, diction and style.
So yes it sucks...
... but it has to be done.
(based on last 2 months log reports)
