"
Hi, there are a great deal of errors in the opnsense code: I try to remember
1) WebGui Interface and CARP: the interface is disabled but the card IP is active on this interface. This is not only a mistake in the webgui but also in the systrem. The routes seems to be in place but lack of an active interface , the ip is offline, sometime the whole system. ( a poor alternativ: go to interace click to enable it , then cleick to disable it again and then press save and apply changes . NOW is the result as it has to be )
2) FW-> LogFiles -> LiveView : Checking a rule with label "FLOAT Allow anything without WAN " is red, and dropped BUT the rule is definitivly a pass rule. Even more , I saw a the same rule twice at the same time in the live view, once red/blocked and once green/pass . More then strange ! Not shure what happened with the traffic?
3) CARP is a huge problem: on the backup machine the carp ip X is nocht active ( carp: BACKUP vhid 11 advbase 5 advskew 100
, inet X netmask 0xffffff00 broadcast x.255 vhid 11 ) but dpinger has -B X
4) After removing a carp IP, the connection to the machine broke down . Even the ip in the same network was not reachable.I had to reboot. Not acceptable behaviour!
5) wireguard is a mess and to buggy to explain all the bugs. Don't use it on opnsense,
1) WebGui Interface and CARP: the interface is disabled but the card IP is active on this interface. This is not only a mistake in the webgui but also in the systrem. The routes seems to be in place but lack of an active interface , the ip is offline, sometime the whole system. ( a poor alternativ: go to interace click to enable it , then cleick to disable it again and then press save and apply changes . NOW is the result as it has to be )
2) FW-> LogFiles -> LiveView : Checking a rule with label "FLOAT Allow anything without WAN " is red, and dropped BUT the rule is definitivly a pass rule. Even more , I saw a the same rule twice at the same time in the live view, once red/blocked and once green/pass . More then strange ! Not shure what happened with the traffic?
3) CARP is a huge problem: on the backup machine the carp ip X is nocht active ( carp: BACKUP vhid 11 advbase 5 advskew 100
, inet X netmask 0xffffff00 broadcast x.255 vhid 11 ) but dpinger has -B X
4) After removing a carp IP, the connection to the machine broke down . Even the ip in the same network was not reachable.I had to reboot. Not acceptable behaviour!
5) wireguard is a mess and to buggy to explain all the bugs. Don't use it on opnsense,
