Yes, I did in those mention places, as I do not use IPv6 in my network.
GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0 ipv6.disable=1"
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1...
Sorry for the delay . . . .
Here is the response on the "ip6tables -nvL" command . . .
"ip6tables v1.6.0: can't initialize ip6tables table `filter': Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded."
Thank you for your patience!
I am getting this error in the node syslog now, since the last subscription update today. Any help to alleviate this is greatly appreciated.
"pve-firewall: status update error: iptables_restore_cmdlist: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information."...
Thanks for the reply,
Is this a 'normal' operation in Proxmox, or is there something I would need to adjust?
When you say pve-firewall daemon is restarting itself, this does not include the server
node as whole, but just the firewall, correct?
I have Proxmox running a server with 32GB RAM (of which about 40% is used), yet I am getting this entry in the node syslog about 45-60 mins, regularly:
Aug 06 15:31:27 xxxxxxxx pve-firewall: restarting server after 365 cycles to reduce memory usage (free 91996160 (5246976) bytes)
Here are the contents of the following files:
IN ACCEPT -p tcp -dport 8006 -sport 8006 # Proxmox GUI
IN ACCEPT -p tcp -dport xxxxx -sport...
I have been reading several information sources on the firewall operation,
though I'm still having the same firewall issues:
proxmox-ve: 5.2-2 (running kernel: 4.15.18-1-pve)
pve-manager: 5.2-5 (running version: 5.2-5/eb24855a)
Not sure where to start with this error, firewall is open for 5900. I did notice this error appearing after I installed a Let's Encrypt! certificate. Not sure if the 2 are related . . .
Anyway comments are welcomed . . .
Error occurs on either a container or a virtual machine console request...
I submitted some of these questions to my host provider, as I do not know the configuration up to the server.
Traceroute shows the following on the 'A' pool routing:
traceroute to www.google.com (220.127.116.11), 30 hops max, 60 byte packets