A new development/testing version of netward has been cut
for anyone tracking and the handful of testers out there. A lot of the
options have changed and a few oddball bugs were finally identified.
Thanks go to Steve Dickinson for helping to
identify some of the bugs. Some of the notable changes were:
-f | --filter expr
option and argument
have been dropped in favor of simply tacking filter options onto the
end of the argument string.
While the options changed - they did not change too much. After compiling
just type netward -u or refer to the manual page.
New site design is up and running after one trial
desgin that didn't go
so well. The new design is somewhat busier but designed for faster access to
a variety of information and pages. The digest entry about it has more information.
Along with the site change a lot of small code updates were done; mostly
cosmetic in some of the smaller modules. The netward utility
had a lot of patches to correct some bugs and validation testing:
All of the details can be found in the digest entry.
In the first part of the
libpcap series a rudimentry packet reader (or sniffer) was
built which could read and print tcp/ip traffic on a particular interface.
In the second text a look at some simple checks of the data itself, adding
options like interface selection, libpcap filter options
and verbosity levels. Some of the checks included are:
The filter options are eventually passed exactly like tcpdump
using the tcpdump argv vector copy.
The software utils called pksys have been integrated into a
single utility called netward. The arguments were compressed
into a more nmap-like syntax. Following are some of the changes
:
The TODO list has grown a bit too:
Of course the usual disclaimer; none or all of the mentioneded
changes may ever happen. As is, netward can run out of the
box and detect minor errors like mismatched lengths and will score
what it thinks might be scans or probes against a host. Suggestions, comments
and bricks are all welcome; feel free to
email me.
In the third (last) installment of the DNS series a look at setting up and managing primary and secondary DNS servers for redundancy covering topics such as:
Additionally a look at some of the other options involved with server and zone maintenance.
(based on last 2 months log reports)
