| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
The latter allows you to set 'disable' as community and the front end (!)
will not be as critical about the results.
|
| | |
|
|/ |
|
|
|
|
| |
Firefox....
|
| |
|
| |
|
| |
|
|
|
|
| |
Just skips the db
|
| |
|
|\ |
|
| |\
| | |
| | | |
README.rst: Add absolute link to the API for pure convenience
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a device replies from two or more IPs we can't assume it actually
knows what IPs it replied from... (great, right?).
This adds a fall-back when that happens where we compare the actual
interfaces. We require a minimum of 10 matching MAC addresses and skip the
once that are blank to gain confidence in the result.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Truns out people suck at making sensible network hardware.
Lots of replies on IPs that the devices didn't know they had. I discard
these now, but should keep some sort of map. The reason this is a problem
is that we later "Deduplicate" results by comparing IP lists - but that
doesn't work when the devices don't know about all of the IPs they listen
to.
I might have to revisit this since the IPs are obviously valid...
|
| |/ |
|
| |
| |
| |
| |
| | |
Now also populates snmpresults artificially with data from LLDP when
needed.
|
| |
| |
| |
| |
| |
| |
| | |
Still need to populate the ipmap with results from LLDP somehow.
E.g.: If we can't contact a switch over SNMP that we see over LLDP we know
the sysname and IP.
|
| |
| |
| |
| |
| |
| |
| | |
This removes the actual mapping, but introdcues crawling.
All the data for mapping is there, and now the collision detection and
fixing is starting to look actually sensible.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The lldp-only map ensures we aren't fooled by vlans and other logical
links, but if lldp is disabled it obviously doesn't tell the whole story.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
what?
lol...
just figure it out for me.
Ok, so the tool isn't entirely done, but it departs from the simple
lldpdiscver.pl method that was very limited when things weren't working as
they should.
The long-term idea of lolwhat is that it should be able to do all sorts of
discovery. Right now it just takes a list of IPs and figures out how things
are connected by SNMP. It uses LLDP info from SNMP, but it does not
_currently_ traverse new hosts based on what it finds.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Still needs lots of work, but mainly with regards to gluing it all
together.
Possibly populate a nice little "local macs" hash to map mac addresses to
systems/ports easily.
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
The HTML/detail should probably be tweaked, but I think we need a way to
show that Gondul is still alive now that we are hiding the time stamp by
default.
Feel free to throw the HTML/CSS away in favor of some other subtle but
noticeable "animation".
|
|
|
|
|
|
|
| |
Without this the individual endpoints' local overrides would... well...
override it.
The idea is that any historic data is cached for a very long time.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #93
Fixes #92
Fixes #91
The hash logic with FreezeThaw wasn't consistent, which broke a lot of
optimizations. This might be slower (?) but it's consistent which means
we'll make up for it by better cache utilization.
To utilize this I also added delayed JSON parsing (#91) with a big
description of why we want it. This also means that #90 and #89 is a lot
less important. One issue right now is that "time" isn't part of the ETag.
This is both a blessing and a curse. If we are going through time we will
actually use in-app cache (not browser cache - the URL changes). This
makes for nice CPU savings, but ultimately means we can't tell that the
data for two distinct times is identical because we only see one. Oh
well...
On the simpler side, I fixed/improved the clearBox logic to fix the
artifacts. Might need to tune this. I also added some optimizations to
avoid redrawing identical text. This is what pointed out to me that the
hash was broken too: The resizeEvent was triggering all the time, forcing
redraws all the time. This happened because nmsData.switches "updated"
frequently which should only happen if someone adds/moves/removes a switch
or linknet - regardless of time travel. This was caused by the inconsistent
hash causing a false cache miss.
Anyway, if you are still reading this, you almost got a patch with "kjell
magne bondevik uten mellomnavn" as a literal text string... TOO BAD.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a result of testing with TG16-data, I was able to find and fix a few
outstanding issues and tune the health map to make more sense.
Also introduced both temperature and dhcp into the health map and info box.
Removed the switchInfo text on the health map unless the score is above a
threshold.
Still more tuning needed. After introducing dhcpInfo it's become even more
important to address #88
|
|
|
|
|
|
| |
- Don't overload the logbook overlay
- Neater date formatting (ugh, I hate that we need to do this)
- Caption for the logbook in the info box
|
|
|
|
| |
Makes it more snug and look the same all over
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I think we can say this
Fixes #53
and
Fixes #52
still should add support for making it configurable, that that's not a must
for DX16 to take place.
|
|\
| |
| | |
DX16 salkart
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I can never get it all in a single commit.
But I compensate by some times putting multiple unrelated things in the
same commit.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #69 #11 #5
Introduces nmsTime which unifies the time travel code a bit. It still needs
some work, but this is much better.
All conversion is now done by native JavaScript methods, freeing us from
the hell that is parsing it ourself.
One thing should be added: The backend should discard any now=values that
are not 5-minute intervals. We don't want to kill the cache and the
database by extension.
Still need to re-implement the "replay event" shorthand, but that ties in
to #54
|
| |
| |
| |
| |
| |
| | |
References #53 #52 #54
It's hardcoded, but I can live with that for now.
|
| |
| |
| |
| |
| |
| |
| | |
- Time in oplog is now localtime and properly padded (00:10, not 0:10)
- Health map instead of combo/aggregated
- Tweak the menu slightly
- Rotate and resize the random switch in guess_placement
|
| | |
|