Gives error: nethsecurity-23.05.0-x86-64-generic-squashfs-combined-efi.img.gz: non-existent or non-regular file
It should be with no .gz ? qm importdisk 401 nethsecurity-23.05.0-x86-64-generic-squashfs-combined-efi.img local-lvm
root@pve-1:/temp# qm importdisk 401 nethsecurity-23.05.0-x86-64-generic-squashfs-combined-efi.img local-lvm
importing disk 'nethsecurity-23.05.0-x86-64-generic-squashfs-combined-efi.img' to VM 401 ...
Rounding up size to full physical extent 320.00 MiB
Logical volume "vm-401-disk-0" created.
transferred 0.0 B of 316.3 MiB (0.00%)
transferred 4.0 MiB of 316.3 MiB (1.26%)
...
transferred 316.3 MiB of 316.3 MiB (100.00%)
Successfully imported disk as 'unused0:local-lvm:vm-401-disk-0'
root@pve-1:/temp#
Hello, about this alpha, i tried to test on proxmox but the IMG wont boot. (No bootable device)
I tried import as a disk and as a CD IMG. Both import wont boot. Any suggestion?
Thanks
By default, the network configuration will be as follows:
The LAN interface will be configured with a static IP address of 192.168.1.1.
The WAN interface will be configured to use DHCP to obtain an IP address from your ISP.
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.
In reality, an ordinary tester has only one public IP address and he first checks on a virtual machine on his private network.
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.
Did you use 401 as VM ID? If the answer is no you need to change the VM ID in the other commands too.
Do you have two network interfaces in your Proxmox server?
I followed the installation steps for proxmox (except of the appended .gz part) and it worked, so maybe one of the commands failed on your side.
The only difference Is my storage: local-zfs instead of local-lvm.
I think that i can’t import the image on zfs block storage… Maybe i have to dd the image…
Thank you for pointing it out, I’ve fixed the doc.
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
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
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
I noticed that my proxmox Vm won’t show guest agent properties.
Quickly Downloaded qemu-ga last package on openwrt repo and works well.
Should be possibile to include the package in nethsec?
Added to the admin manual: 