Search results

Hi Abkrim did you see the error message ? PVE could not mount the NFS share because you have it already mounted. so : * disable the NFS storage in PVE * unmout the NFS share and remove the fstab entry * reactivate the storage in PVE then you should have your NFS share working :)

This is most probably because the rpcbind service on your nfs server is not running. IIRC this service is needed for showing a list of exports. By setting the exports directly in /etc/fstab you bypass the need for the exports discovery , but the storage will probably marked as offline in the...

can post the log output or screenshot of the error ?

swap is not necesserly bad per se, it can for instance happen on servers with very large uptime, that the kernel puts on swapspace parts of processes that are rarely used, to get more place to cache disk accesses. What is suboptimal is when you're constantly swapping in and out, because this...

C) why don't you do this on pfsense ? personnally I would rather have have a single firewall taking care of all the VM access I would then assign the IP adress on the WAN port of psense, do port fortwarding to reach the VM sitting in vmbr30, and do source nat on pfsense again

had a look at your schema for B) and your external IP3. I would add this IP to pfSense/Opnsense by itself, and then do port forwarding on the firewall. C) Do i probably miss masq in Shorewall for the internal network? do you mean dnsmasq here ? In any case if you use a DHCP/DNS server for you...

with the following command: lspci -k | sed -n '/Ethernet/,/driver in use/p' you will get a list of network devices devices with their drivers then whith with ip link you will get at list of eth* or en* devices to configure

You can either pass to the VM a PCI device or an USB device. If your bluetooth dongle appears on the host system as an USB device (ie you see it in the output of lsusb) you should be able to pass it to a VM following the instructions from https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines

you can forward port ranges when specifying the --dport option synthax should be along so you could forward all port above 22, but keep in mind the web gui also binds to port 8006 # add to the PREROUTING chain a jump to the DNAT target iptables --table nat --append PREROUTING --in-interface...

Did you have a look at what is the output of of the commands: systemctl status lxc@101.service journalctl -xn

PVE uses the following to check if the NFS server is online: /sbin/showmount --no-headers --exports <my_server> is this command properly returning in less than two seconds when you server is marked as offline ?

the huge amount of I/O wait probably makes the storage status unresponsive, and as the storage is unresponsive, we mark the node as red if you have any doubt check the command 'pvesm status' on the host if this command does not return in a couple a seconds the node will be marked red the...

make sure that you don't have VMs connected to the vmbr0 bridge, all the nics of your VMs should be in the vmbr2 bridge if you put VMs on vmbr0 and they try to reach the internet without having their mac address registered in the OVH management interface, OVF will shutdown your network ( IIRC)...

it would be better to create a VM / container as the central log server with this IP, instead of running the central log server on the PVE host it's generally not advised to add network services to the pve host, which should be used only for running the guest machines

you should post your entire backup log so we get the context most backup errors are due to the backup storage being unavalable when the backup is run

is the windows firewall off ? to make sure you're not blocking from inside the VM, start a netcat client inside the VM and bind to your 8000 port using the external IP address of the VM

I think you should have the possibility of marking this thread as solved in the forum panel

looks to me like your gateway is wrong in the VM config it should be be the IP adress of the bridge vmbr0 where the routing is taking place (10.10.10.100 according to your /etc/network/interfaces )

just to make it 100% clear the VM config args you're talking about are the device boot order ?

Are you seeing the ARP replies when inspecting the veth device from the Proxmox host ? (the veth device as see from the host should have a name like veth0<CTID>i<nic index> normally you should for instance here I am inspecting the output of a veth device assigned to CT100( 192.168.31.134)...