Stoiko,
Thank you! Your solution has repaired the problem. Thank you for your patience concerning this matter! Thank you for this very fine product!!!
Sandy
Sorry,
Yes, I did in those mention places, as I do not use IPv6 in my network.
/etc/default/grub:
#GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0 ipv6.disable=1"
/etc/sysctl.conf:
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[13722]: 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?
Thanks
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[1527]: restarting server after 365 cycles to reduce memory usage (free 91996160 (5246976) bytes)
Aug 06...
BAM! That nailed it! Thank you very much as this was EXTREMELY frustrating! Have a great weekend, I know I will, lol! :D
Yes, also using fail2ban and restrictive firewall settings . . .
Here are the contents of the following files:
cluster.fw
[OPTIONS]
policy_in: DROP
enable: 1
policy_out: ACCEPT
[RULES]
GROUP pve_gui
GROUP ssh_usr
[group pve_gui]
IN Web(ACCEPT)
IN ACCEPT -p tcp -dport 8006 -sport 8006 # Proxmox GUI
[group ssh_usr]
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:
package versions:
proxmox-ve: 5.2-2 (running kernel: 4.15.18-1-pve)
pve-manager: 5.2-5 (running version: 5.2-5/eb24855a)
pve-kernel-4.15: 5.2-4
pve-kernel-4.15.18-1-pve...
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...
Bob,
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 (172.217.5.196), 30 hops max, 60 byte packets
1 104-250-(xxx)-113.static.gorillaservers.com...
Unfortunately, above solution does not work. Leaving either the IP or netmask blank results in a nerfed connection . . .
I know there has to be an answer out there . . . Would the IT gods smile upon this IT noob adventurer . . .
I have cruised the forums fairly thorough and have not quite found a
solution to my problem. Maybe someone can help . . . Thanks in advance!
I have (2) /29 'non-contiguous' IP blocks to be used as public IPs for
a few containers and 2 websites (VM's).
I have a rough understanding of how the...
I have successfully installed CT's that are running fine, but when I try to install a VM (via ISO, and boot order is correct), the VM never makes it past the SeaBIOS screen with a flashing cursor in noVNC. ISO is valid and bootable (tested in VMware Workstation) . . .
Not sure what I am...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.