Because of our requirements I have changed the Topology-Map, primary the d3.js / json part.
It does work, but I think the implementation in the libmap.php can be better.
It’s not finished yet. I’m open for suggestions and feedbacks.
Additional features like save positions, map zoom, change background and more will be implementend soon. For more information please visit the NeDi-Forum http://forum.nedi.ch/ .
The code is in the alpha phase.
This is coded for the NeDi version 1.5 .
I didn’t touch the original functions in the libmap.php file.
I copied it and created two new functions with my changes.
When you call the Topolgy->D3jsmap it creates a new json map file called “map3js_$username.json” instaed of “map_$username.json”
please backup the original file first.
like that \hmtl\inc\libmap.php.backup
copy the two files on your nedi HTML folder.
edit nedi.conf and put this line on GUI Settings.
module Topology D3jsmap paint net
I haven’t change anything here.
In the d3js map I have only changed the D3js code for my expected results.
I have focused on the Output from the Devices and Nodes(nodes without interface).
Metric: you can set the Charge of the forcelayout // lal default is 120, 120/4=30
Length: you can change the link distance between devices or nodes // len default default is 50, -3*50=-150
If Name: show the linked interface between the two devices
Device IP: show the device IP expected in nedi
Room: show the room from the snmp string
Rack: show the rack from the snmp string
When you select both Room and Rack then it show the complete snmp string
To better indentifying the devices on the same building or room, they have the same font color.
Mode: show the device contact
Mode: show the device model
Go to print mode and then position your devices to print as PDF… or so.
Default Output with Interface like SVG and PNG output… but you can place your devices vy yourself .
Today I had some issues on my Laptop with DirectAccess. The DirectAccess vpn connection haven’t connect to the corporate network. The DirectAccess connection status stay on “connecting” and doesn’t connect with success. To troubleshoot the problem I’ve also used the Microsoft Tool “Direct Access Client Troubleshooter” .
The Problem was the NLS Server.
To determine if the client is inside or outside of the corporate network we use the NLS component of DirecAccess. If the client can successfully connect to the NLS server, it is on the internal corporate network and DirecAccess is not used. If the NLS server aren’t reachable, the client is outside of the corporate network and the client try to establish a remote tunnel to the corporate network using DirecAccess.
NLS stays for Network Location Server and is a critical component when you’re deploying DirectAccess. The NLS is nothing more than a internal webserver with an valid SSL certificate installed on it. The NLS server never should not be reachable over the internet.
Two helpful command:
netsh namespace show effectivepolicy