Newcore SSID change
dr
Newcore now has a drastic change to how SSIDs are handled.  Networks and
clients now have multiple SSID records including independent rates,
encryption options, etc.

Cloaked/Uncloaked is (mostly) gone.  Cloaked SSIDs are listed as
cloaked beacon ssids, and SSIDs disclosed from probe responses are listed 
as uncloaked probe response networks.

A kismet client ought to be able to cleanly handle 1 beacon SSID
and 1 response SSID as an uncloaked single SSID, but we'll leave that up
to the client logic and track them independently on the server.

Multiple-SSID handling will fail if multiple SSIDs are beaconed by an
AP, cloaked, with the same length SSID (if the AP beacons as a zeroed
N-length tag), with the exact same encryption options.  Obviously, if
the beacons look identical, theres no way to tell there are really 2.
(And if the AP were smart, it would beacon as a single item anyhow)

This SSID change has caused some significant changes elsewhere in the
code as well, such as the NETXML and NETTXT logging files.  This is
another major change to the NETXML log format for kismet-newcore,
which accentuates why I haven't frozen the log format yet.  This also
deprecates and removes the NETWORK protocol and replaces it with the
BSSID and SSID protocols.  Client authors be warned, this may change
yet more.