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?
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?