"
Thanks
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
#47
18.1 Legacy Series / Release 18.1 rc2: Where to Download?
January 19, 2018, 06:49:43 PM
Gents,
I am new to OPNsense, but would like to evaluate the 18.1 Release Candiates.
Where and how do I download the releases?
I am new to OPNsense, but would like to evaluate the 18.1 Release Candiates.
Where and how do I download the releases?
#48
17.7 Legacy Series / System: High Availability GUI Corruption
January 18, 2018, 04:40:19 PM
Hi,
I am using the System: High Availability GUI page to manage the CARP setup between two OPNsense units. Everythung is working fine, except that one of the units crashed and since then, there is a corruption in GUI two input fields
The IP address field of the Synchronize Peer IP and the Synchronize Config to IP has an old value (10.5.1.2) that is never erased. See screenshot attached.
Before i do a save of the page, I have to manually update the ip fields to the correct value (10.18.1.52) and then click on save. It accepts and use the correct value, as the sync etc all works.
However, after the save is done, the old value of 10.5.1.2 returns again immediately. Before the next save, I have to overwrite it again.
I have checked, the wrong value is not in the xml config file that I downloaded and uploaded again. The web GUI is picking it up from somewhere else.
Any ideas where and and how I can get rid of this value?
I am using the System: High Availability GUI page to manage the CARP setup between two OPNsense units. Everythung is working fine, except that one of the units crashed and since then, there is a corruption in GUI two input fields
The IP address field of the Synchronize Peer IP and the Synchronize Config to IP has an old value (10.5.1.2) that is never erased. See screenshot attached.
Before i do a save of the page, I have to manually update the ip fields to the correct value (10.18.1.52) and then click on save. It accepts and use the correct value, as the sync etc all works.
However, after the save is done, the old value of 10.5.1.2 returns again immediately. Before the next save, I have to overwrite it again.
I have checked, the wrong value is not in the xml config file that I downloaded and uploaded again. The web GUI is picking it up from somewhere else.
Any ideas where and and how I can get rid of this value?
#49
17.7 Legacy Series / CARP PFSYNC Deletes Firewall Rule
January 01, 2018, 07:45:48 PM
Hi,
I am running OPNSense 17.7.5-amd64 on a 2 x OPNsense Quad Core Gen3 SSD (Model SKU OPN19004R).
I have configured CARD and the Failover works 100%, even with a SITE-to-SITE IPsec tunnel to head-office Router.
The PFSYNC interfaces are dedicated and connected point-to-point with a cable.
I have one major problem. Whenever the Master syncs the config to the Slave, it deletes the firewall rule on the PFSYNC interface of the Slave that accepts sync traffic.
The rule simply accepts all traffic from PFSYNC net to PFSYNC net.
To start the sync process, I manually configure this rule on the Master and the Slave.
When I make any change to any firewall rule on the Master, even just changing the description of a rule on the master, this rule on the PFSYNC interface is deleted on the Slave and all further syncs fail until I manually add the rule again on the Slave.
Other firewall rules are transferred correctly to the Slave on the other interfaces.
Any ideas how to fix this?
I am running OPNSense 17.7.5-amd64 on a 2 x OPNsense Quad Core Gen3 SSD (Model SKU OPN19004R).
I have configured CARD and the Failover works 100%, even with a SITE-to-SITE IPsec tunnel to head-office Router.
The PFSYNC interfaces are dedicated and connected point-to-point with a cable.
I have one major problem. Whenever the Master syncs the config to the Slave, it deletes the firewall rule on the PFSYNC interface of the Slave that accepts sync traffic.
The rule simply accepts all traffic from PFSYNC net to PFSYNC net.
To start the sync process, I manually configure this rule on the Master and the Slave.
When I make any change to any firewall rule on the Master, even just changing the description of a rule on the master, this rule on the PFSYNC interface is deleted on the Slave and all further syncs fail until I manually add the rule again on the Slave.
Other firewall rules are transferred correctly to the Slave on the other interfaces.
Any ideas how to fix this?
