jNetMap 0.5.5-RC1

by

It’s been a while, I know – this one has been a long time in the making, and brings several changes under the hood, namely a completely new plugin framework. All relevant plugins have been ported, while some others have been replaced by scripts (RDP, SSH etc.).
Even more under the hood, I’ve switched the project over to maven, plus it’s now capable of reproducible builds 🥳

» Download 0.5.5-RC1

… and let me know what you think, or if you’re encountering any issues with this RC.

Changelog

  • switched build system from ant to maven
  • switched plugin frameworks from jspf to pf4j
  • added history section to InfoPanel
  • added live preview for connection styles
  • improved SNMP request handling
  • fixed connection status logic
  • added ability to change connection target
  • added name field to connection
  • added background color setting
  • added background image to maps
  • improved handling for scaling/translating with the mouse
  • fixed device interfaces not sorted by name
  • added several new command line arguments
  • improved man page documentation
  • introduced reproducible builds
  • removed splash screen (halves loading time)
  • made number of ports, tcp timeout and zoom steps configurable
  • added ignore device/connection for events
  • added ARP device lookup

18 thoughts on “jNetMap 0.5.5-RC1”

  2. Since you already pre-released 0.5.5 (to me) quite some time ago, shouldn’t this be 0.5.6?

  3. Tested on debian/testing amd64. Everything is working well with OpenJDK-11 and also older -10. No bugs so far noticed. Older maps can be loaded, and everything is running smooth and clear. Great work, thank you very much! Hans

  4. Ok, for those who are interested: When building a new livefile system with live-build (in my case KALI-Linux), you will put the “jNetMap-0.5.5-694.deb”-package into the required “packages.chroot”-subdir. But this does not work!

    During the build, the package is not recognized by the installer, even, when you can install the package manually with “dpkg -i” on a debian system.

    The problem is IMO the capital letters in the name.

    The easy solution is, to rename the package with “dpkg-name jNetMap-0.5.5-694.deb”, which will convert the package to “jnetmap-0.5.5_all.deb”.

    The renamed package is now recognized by live-build and well installed.

    To do so, for the future, I suggest like Heynneman to release a newer package with a higher version, as “0.5.5” already exists and the new package version got the same as installed, for example 0.5.6 or better (due to the many changes) 0.6.1.
    Hope this helps someone.

    Hans

    • Thanks for investigating! I have not come across this limitation, however the Debian packaging guidelines state that lower case should be used, so I’ll change that.

  5. Another request… If you resize the jNetMap window, and center the map appropriately in the window, and size the zoom level appropriately, when you quit and restart jNetMap, you have to do it all over again. It needs to remember window size and position, and map size and position, and zoom level.

    It also always asks if you wish to save the map when quitting, even if you just opened jNetMap and made no changes.

    • Huh, I always leave mine zoomed out to see everything, but you are right – when I zoom in the view state is not saved. I’ll see if that’s possible…
      (regarding the save message, stuff certainly has changed, such as the internal state of devices going from unknown to up or something, but I see how this may not be “relevant” enough to save… maybe I’ll add a setting)

  6. Hi Al,

    the first isssue I can not confirm, tried several ways. I am running debian/testing amd64 here. This is independent of saving the card or not.

    About the second issue: Yes, I can confirm this. Although nothing has changed by me, it is asking to save the map. Saving does no harm to anything, even to the window size.

  7. Hi Al,

    just for the window settings: In the menu “Allgemein” (might be named “General” or “Main” in the English version), here I mean the top Position in the settings window), you can set the behaviour of the window (size and position) of jNetMap. Please check, if you have set these options to active.

    • Hello Hans,

      Yes, I have those settings checkmarked. The window size/position does remain across restarts of the app,

      My description of the problem was a little inaccurate. The real problem is that it doesn’t remember the position and zoom level of the map itself. On every restart of the app I have to recenter the map, and reset the icon zoom level.

      • Hi Al,
        yes, I rechecked this, and can confirm this. I also deleted my old configuration to get rid of any old settings and did a fresh install – same result.

        Just another info for Dave: Installed openjdk-17 for testing purposes (this is the highest version in debian and jnetmap started, but the saved card could not be opened. However, openjdk-17 is still in development!

  8. Hello, this looks to be an amazing program and would be perfect for IoT development but unfortunately i can’t get it to save a map under Win10, keeps throwing “corrupted” when trying to open, tried install on VM under debian but can’t even get it to install on linux, would be willing to pay to have an app like this working. any help would be greatly appreciated.

    • Hi – just tested it on an old Win10 laptop, works for me. Would you be willing to send me the resulting file for analysis? Alternatively you could also follow the steps outlined here so I can have a look at the logs…

      • that was my bad, updated jdk not actual runtime, all is good now was running java build 151 and it’s at like 256 now lol. On a different note, would you be interested in some different/updated icons? Google mini’s, Wifi light bulbs/plugs etc?

        • Ah, good to hear 🙂
          Absolutely! Have a look at the existing ones to see what it expects format-wise (64x64px PNG, filename is the type in lower case, _s variant for “selected” state). Note that introducing new types currently requires a change in the code, which I may have to rethink ^^)

Comments are closed.