No firewall log and

Oct 1, 2018
11
2
3
54
Hello,

I have read every wiki, official document and forum post concerning this issue- and I have reinstalled proxmox 5 times since October- had hardware failure and have been locked out when trying to change host ip address or move it to a vlan on another subnet. That being said (as if that isn't bad enough) I feel totally stupid.. Prior to this recent release I always had a firewall log; no all I get is
28/Jan/2019:12:18:41 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:12:18:41 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:12:20:08 -0600 starting pvefw logger
0 5 - 28/Jan/2019:13:07:29 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:13:07:29 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:13:09:33 -0600 starting pvefw logger
0 5 - 28/Jan/2019:13:17:54 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:13:17:54 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:13:19:21 -0600 starting pvefw logger
0 5 - 28/Jan/2019:14:19:35 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:14:19:35 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:14:19:35 -0600 starting pvefw logger
0 5 - 28/Jan/2019:14:24:24 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:14:24:24 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:14:25:52 -0600 starting pvefw logger
0 5 - 28/Jan/2019:14:25:56 -0600 received terminate request (signal)
0 5 - 28/Jan/2019:14:25:56 -0600 stopping pvefw logger
0 5 - 28/Jan/2019:14:25:56 -0600 starting pvefw logger

and in the system log:
Jan 28 15:46:08 pve1 systemd[1]: Started 100.scope.
Jan 28 15:46:08 pve1 systemd-udevd[7493]: Could not generate persistent MAC address for tap100i0: No such file or directory
Jan 28 15:46:08 pve1 kernel: device tap100i0 entered promiscuous mode
Jan 28 15:46:08 pve1 systemd-udevd[7548]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Jan 28 15:46:08 pve1 systemd-udevd[7566]: Could not generate persistent MAC address for fwln100i0: No such file or directory
Jan 28 15:46:08 pve1 systemd-udevd[7564]: Could not generate persistent MAC address for fwpr100p0: No such file or directory
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 28 15:46:08 pve1 kernel: device fwln100i0 entered promiscuous mode
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jan 28 15:46:08 pve1 kernel: vmbr3: port 2(fwpr100p0) entered blocking state
Jan 28 15:46:08 pve1 kernel: vmbr3: port 2(fwpr100p0) entered disabled state
Jan 28 15:46:08 pve1 kernel: device fwpr100p0 entered promiscuous mode
Jan 28 15:46:08 pve1 kernel: vmbr3: port 2(fwpr100p0) entered blocking state
Jan 28 15:46:08 pve1 kernel: vmbr3: port 2(fwpr100p0) entered forwarding state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 28 15:46:08 pve1 kernel: fwbr100i0: port 2(tap100i0) entered forwarding state

this is the same for vmbr0 etc..

I have all firewall settings on in all areas.

I am at a loss to fix this; can someone please give me a lesson and slap me with some knowledge?
 
Oct 1, 2018
11
2
3
54
so far what I have notices is running the command line to version cluster.fw etc is that it did not represent the GUI- so I unchecked and rechecked and rebooted and settings magically appeared- but failed to magically work as expected.
 

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
4,763
316
83
Hi,

You have to be a bit more specific in case that somebody can help you.

have been locked out when trying to change host ip address or move it to a vlan on another subnet
Did you lose connection or do the firewall block you?

If you move the subnet the default lockout rules are no more working.
So, insure that ssh and port 8006 is open for the new subnet.
 
Oct 1, 2018
11
2
3
54
Wolfgang, sorry it took so long to get back- I ended up starting to log martains like crazy in the system log- same stuff in the firewall no info- deleted all of my VMs and all bridges but vmbr0 ran up a few VMs played arond the martians came back and right before the hard locked I got the IRQ 16 because nobody cares in the system log...end up me doing a hard shut down.
Upon restart pressing power button did nothing- pulled out scope and multimeter- all power good etc. pulled cmos battery reset bios- still nothing.
So I tore it all down and was thinking about doing some target practice in the morning (seriously pissed) instead went to bed. Put her all together tonight- she boots into bios just fine- have not put anything else together yet.

guess I will have to invest in some bifurcation hardware since bios supports it- I had left everything stock as I expected it to be fine... any thoughts?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!