Servicecyclev4 patch - Revision history

Kitz: Category

2024-05-17T00:36:43Z

Chrysalis: fix mistake

2023-07-22T14:30:44Z

fix mistake

Chrysalis: fix error on base path

2023-06-05T18:35:44Z

fix error on base path

Chrysalis at 10:41, 5 June 2023

2023-06-05T10:41:57Z

Chrysalis at 10:10, 5 June 2023

2023-06-05T10:10:15Z

Chrysalis: Created page with "Default behaviour on pfSense is to cycle all services if any configured gateways go offline, this can include VPN's and tunnels not just broadband connectivity. This can caus..."

2023-06-05T10:09:09Z

Created page with "Default behaviour on pfSense is to cycle all services if any configured gateways go offline, this can include VPN's and tunnels not just broadband connectivity. This can caus..."

New page

Default behaviour on pfSense is to cycle all services if any configured gateways go offline, this can include VPN's and tunnels not just broadband connectivity.

This can cause problems e.g. if your pfSense is hosting LAN services such as a NTP server or UPS daemon. Consider a scenario e.g. if you have a power cut, your WAN goes offline, pfSense then puts services into a cycle loops, which in turn drops connectivity to the UPS daemon so client machines are unaware of power status and battery level which might prevent automated safe shutdown/hibernation.

This patch changes the behaviour so services will only get cycled if a gateway comes back online with a different IP address, if its a cycle keeping the existing IP, then it will not cycle all services, services such as OpenVPN should still behave the same as before.

This is the IPv4 version of the patch, there is also a IPv6 version.

Paste the below code into the ''Patch Contents'' box.

Add a description such as 'Better diagnostics limiters layout' in the ''Description'' box.

Set ''Path Strip Count'' to '0'.

''Base Directory'' to '/usr/local/www/'.

<pre>--- /etc/rc.newwanip 2023-04-18 03:05:04.404321000 +0100
+++ /etc/rc.newwanip 2023-04-18 03:05:50.740612000 +0100
@@ -233,10 +233,12 @@
if (isset($config['system']['ip_change_kill_states'])) {
log_error("IP Address has changed, killing all states (ip_change_kill_states is set).");
pfSense_kill_states(utf8_encode($oldip));
+ restart_packages();
filter_flush_state_table();
} else {
log_error("IP Address has changed, killing states on former IP Address $oldip.");
pfSense_kill_states(utf8_encode($oldip));
+ restart_packages();
}
}

@@ -270,7 +272,7 @@
/* restart snmp */
services_snmpd_configure();

- restart_packages();
+ // restart_packages();
} else {
/* signal filter reload */
filter_configure();</pre>

← Older revision		Revision as of 00:36, 17 May 2024
Line 43:		Line 43:
	/* signal filter reload */		/* signal filter reload */
	filter_configure();</pre>		filter_configure();</pre>
		+
		+
		+	[[Category:Pfsense Patches]]

@@ Line 3: / Line 3: @@
 This can cause problems e.g. if your pfSense is hosting LAN services such as a NTP server or UPS daemon.  Consider a scenario e.g. if you have a power cut, your WAN goes offline, pfSense then puts services into a cycle loop, which in turn drops connectivity to the UPS daemon so client machines are unaware of power status and battery level which might prevent automated safe shutdown/hibernation.
-This patch changes the behaviour so services will only get cycled if a gateway comes back online with a different IP address, if its a cycle keeping the existing IP, then it will not cycle all services, services such as OpenVPN should still behave the same as before.
+This patch changes the behaviour so services will only get cycled if a interface comes back online with a different IP address, if its a cycle keeping the existing IP, then it will not cycle all services, services such as OpenVPN should still behave the same as before.
 This is the IPv4 version of the patch, there is also a IPv6 version.

← Older revision		Revision as of 10:41, 5 June 2023
Line 6:		Line 6:

	This is the IPv4 version of the patch, there is also a IPv6 version.		This is the IPv4 version of the patch, there is also a IPv6 version.
		+
		+
		+	----
		+

	Paste the below code into the ''Patch Contents'' box.		Paste the below code into the ''Patch Contents'' box.

@@ Line 17: / Line 17: @@
 Set ''Path Strip Count'' to '0'.
-''Base Directory'' to '/usr/local/www/'.
+''Base Directory'' to '/'.
 <pre>--- /etc/rc.newwanip    2023-04-18 03:05:04.404321000 +0100

@@ Line 1: / Line 1: @@
 Default behaviour on pfSense is to cycle all services if any configured gateways go offline, this can include VPN's and tunnels not just broadband connectivity.
-This can cause problems e.g. if your pfSense is hosting LAN services such as a NTP server or UPS daemon.  Consider a scenario e.g. if you have a power cut, your WAN goes offline, pfSense then puts services into a cycle loops, which in turn drops connectivity to the UPS daemon so client machines are unaware of power status and battery level which might prevent automated safe shutdown/hibernation.
+This can cause problems e.g. if your pfSense is hosting LAN services such as a NTP server or UPS daemon.  Consider a scenario e.g. if you have a power cut, your WAN goes offline, pfSense then puts services into a cycle loop, which in turn drops connectivity to the UPS daemon so client machines are unaware of power status and battery level which might prevent automated safe shutdown/hibernation.
 This patch changes the behaviour so services will only get cycled if a gateway comes back online with a different IP address, if its a cycle keeping the existing IP, then it will not cycle all services, services such as OpenVPN should still behave the same as before.