Scalar i6000 – Connect to the Webinterface

I got issues connecting to the Webinteface of our Scalar i6000.

Its java based and the problem is that it is designed for java version 1.6.

That means that if your’e using lets say java 1.8, there will be errors that prevents the execution of the applet.

So i found out that there are two main problems:

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
at java.lang.reflect.Constructor.newInstance(
at java.lang.Class.newInstance(
at sun.applet.AppletPanel.createApplet(
at sun.applet.AppletPanel.runLoader(
Caused by: access denied ("java.util.PropertyPermission" "user.home" "read")
at java.lang.SecurityManager.checkPermission(
at java.lang.SecurityManager.checkPropertyAccess(
at java.lang.System.getProperty(
at com.adic.amc.lm.client.LM3Applet.(
... 9 more access denied ("" "setProperty.networkaddress.cache.ttl")
at java.lang.SecurityManager.checkPermission(
at java.lang.SecurityManager.checkSecurityAccess(
at com.adic.amc.lm.client.LM3Applet.init(

You see java has a problem with AccessControl of
“java.util.PropertyPermission” “user.home” “read”
and “” “setProperty.networkaddress.cache.ttl”

The solution is pretty simple.

Java has a file in which permissions are controlled. In my system (archlinux), its located here:


Maybe in your system the file can be located otherwhere, so just use find oder locate.

I made two entrys in the grant-section in it:

grant {
permission java.util.PropertyPermission "user.home", "read";

The the applet loads and you dont have to install a old java version 🙂

CentOS 7 – Firewalld allow all traffic from a Server

I hate the default firewall in CentOS. 😀

Its so unneeded complicated that a simple Access-Rule seems to be as hard as climbing up the mount everest.

So, my problem was i wanted to configure a CentOS-Server for our backup system. Backup client was installed but the CentOS-Firwall was blocking the traffic.

Our backup-system needs several ports (in range) and communication comes from multiple servers.

But i didnt wanted to allow a port range because of security. So open up traffic for our backup-subnet was the way to go.

Here is the command:

firewall-cmd --permanent --zone=public --direct --add-rule ipv4 filter IN_public_allow 0 -s xx.x.xx.x/xx -j ACCEPT

firewall-cmd --reload

Have fun 😀