NethSecurity Install on Proxmox shield (doc error)

[giacomo (Giacomo Sanchietti)]

@michelandre

It should be with no .gz ?
qm importdisk 401 nethsecurity-23.05.0-x86-64-generic-squashfs-combined-efi.img local-lvm

Thank you for pointing it out, I’ve fixed the doc.

@michelandre

Also, why taking port 443 to access the manager page ???

Then after that how do you want to redirect port 443 to the webserver of another server ???

This is the default of OpenWrt and it seems to me a good default for real usage scenario: the first time you install a firewall, you probably will not have anything listens on port 443 on the public internet.

Still, you can change the port of the web user interface. It’s already documented inside the developer manual. But from you questions I got it’s hard to find it Added to the admin manual: Remote access — NethSecurity documentation

@michelandre

Developers assume that testers will plug their test server directly into the internet because they also assume that you have more than one public IP address.

Not really: OpenWrt auto-configuration is much more complex than this, and it depends on the running hardware. The logic is buried inside the core code, but I’d say the developers assume the testers are using virtual machines.
There is a special logic for VMs:

• QEMU: always use DHCP, eth0 is lan, eth1 is wan
• Digital Ocean: always use DHCP, eth1 is lan, eth0 is wan

@michelandre

That is why the NethSecurity LAN interface will not have an IP address because, in the majority of cases, 192.168.1.1 is already taken by the main server.

You’re right, there is a note about it in the manual. This is again a default from OpenWrt. We can change it for sure, but is there a really good static default IP address? I think most of use will try just 192.168.1.1 without reading the doc