PfSense - Auto reboot script when google is unreachable..

whitexp

Very good

Teddy

Hey everyone,
that script is still working properly. But how can i choose, by which interface the ping should be done?

I am having the normal WAN Interface and a VPN interface. If the VPN Connection is lost, PFSense doesn't realize that and is not resetting the connection / interface. So it would be an easy solution, to choose that i want to ping google.com by the VPN Interface.

I am really bad in writing scripts / programming, so does anyone have a solution, like "Ping google.com by interface ovpnc1" or whatever (in a proper programmed way, that commandline is obviously wrong)?

Brgds

Gertjan

@Teddy said in PfSense - Auto reboot script when google is unreachable..:

But how can i choose, by which interface the ping should be done

"ping" has many options.

Choose yours : man ping FreeBSD

Teddy

@Gertjan said in PfSense - Auto reboot script when google is unreachable..:

@Teddy said in PfSense - Auto reboot script when google is unreachable..:

But how can i choose, by which interface the ping should be done

"ping" has many options.

Choose yours : man ping FreeBSD

Thanks for that list. I suggest it is the -I option? I did now several tests, but all the time the ping fails with "ping -I OPT1".

Here is my complete script, that i am using (from another topic, which is closed):

#!/bin/sh

#=====================================================================
# pingtest.sh, v1.0.1
# Created 2009 by Bennett Lee
# Released to public domain
# https://forum.netgate.com/topic/16217/howto-ping-hosts-and-reset-reboot-on-failure/2
# (1) Attempts to ping several hosts to test connectivity.  After
#     first successful ping, script exits.
# (2) If all pings fail, resets interface and retries all pings.
# (3) If all pings fail again after reset, then reboots pfSense.
#
# History
# 1.0.1   Added delay to ensure interface resets (thx ktims).
# 1.0.0   Initial release.
#=====================================================================

#=====================================================================
# USER SETTINGS
#
# Set multiple ping targets separated by space.  Include numeric IPs
# (e.g., remote office, ISP gateway, etc.) for DNS issues which
# reboot will not correct.
ALLDEST="google.com yahoo.com 24.93.40.36 8.8.8.8"
# Interface to reset, usually your WAN
BOUNCE=OPT1

# Log file
LOGFILE=/root/pingtest.log
#=====================================================================

COUNT=1
while [ $COUNT -le 2 ]
do

	for DEST in $ALLDEST
	do
		echo `date +%Y%m%d.%H%M%S` "Pinging $DEST" >> $LOGFILE
		ping -c1 $DEST >/dev/null 2>/dev/null
		if [ $? -eq 0 ]
		then
			echo `date +%Y%m%d.%H%M%S` "Ping $DEST OK." >> $LOGFILE
			exit 0
		fi
	done

	if [ $COUNT -le 1 ]
	then
		echo `date +%Y%m%d.%H%M%S` "All pings failed. Resetting interface $BOUNCE." >> $LOGFILE
		/sbin/ifconfig $BOUNCE down
		# Give interface time to reset before bringing back up
		sleep 10
		/sbin/ifconfig $BOUNCE up
		# Give WAN time to establish connection
		sleep 60
	else
		echo `date +%Y%m%d.%H%M%S` "All pings failed twice. Rebooting..." >> $LOGFILE
		/sbin/shutdown -r now >> $LOGFILE
		exit 1
	fi

	COUNT=`expr $COUNT + 1`
done

I editet in line 34 "ping -c1 $DEST >/dev/null 2>/dev/null" to "ping -I OPT1 -c1 $DEST >/dev/null 2>/dev/null"

Gertjan

More like

ping -S a.b.c.d google.com

where a.b.c.d is the network address of your, for example, WAN.

Teddy

@Gertjan said in PfSense - Auto reboot script when google is unreachable..:

More like
ping -S a.b.c.d google.com
where a.b.c.d is the network address of your, for example, WAN.

Is there any way, to use the interface? Because my VPN IP is always dynamic.

I obviously have the WAN (but that is, because PFSense is connected to another Router) an internal IP (192.168.178.X).
And i have the LAN with 192.168.1.1, the firewall is blocking all traffic from LAN, if the VPN Connection get's lost.

Now, with your advice, i set "ping -S 192.168.1.1" (because: If the connection on VPN is lost, no traffic can pass due to a firewall-rule the LAN (192.168.1.1)...But anyhow the hosts (google.com, Yahoo etc.) can be pinged -> No restart of VPN Interface, but anyway no connection available (Chrome, Firefox show just, that there is no connection to the internet).

A ping in PFSense to all addresses, using every interface, is successfull. Weird behaviour, from which i can't find the problem now.

Shortly:
Ping google.com by LAN (192.168.1.1) is successful. But i have no access to the Internet. So, the VPN Interface must be reset to work properly again. Any ideas?

Gertjan

@Teddy said in PfSense - Auto reboot script when google is unreachable..:

Is there any way, to use the interface? Because my VPN IP is always dynamic.

Yep, easy.
You're scripting, right ?

Have a look at the diag_ping.php page / Diagnostics > Ping.
We can select an interface there, and the PHP gets the IP address.

@Teddy said in PfSense - Auto reboot script when google is unreachable..:

Any ideas?

Use the VPN interface ?

Teddy

@Gertjan
Yes, i am using a script from another user here in the board! ;)
And i can't really follow. That diag_ping.php i am using always for check, if a ping is possible. But how to connect it with my above mentioned script?

I need an IP-address, to add it in the script, right? But the VPN interface IP is not static, it is dynamic.
First it was 10.247.202.214, now after the reboot it is for example 10.246.201.107

Brig

I realise this is an old topic, but should this still work?

Teddy

@brig

Old but gold!
Still works really properly under 2.4.5!

Brig

@teddy Not working for me on 2.5 sadly

I have added one of my wan IPs in line

counting=$(ping -s M.Y.I.P -c $COUNT $myHost | grep 'received' | awk -F',' '{ print $2 }' | awk '{ print $1 }')

is that correct?

unfortunately I've no idea how to troubleshoot as I'm coming from the switching side of networking, so unless something just works when it comes to things like this it's a steep learning curve ha.

Teddy

@brig

Edit: My fault, I am using another script, here it is:
https://forum.netgate.com/topic/16217/howto-ping-hosts-and-reset-reboot-on-failure

This works for me, maybe try that?
It is pinging several times -> On success nothing happens
No succes -> Reboot interface
Still no success -> Reboot whole PFSense

Can end in a bootloop, if you really have no connection for several hours, but fixes itself, as soon as it has connection again and can ping.

Here is my config:

#!/bin/sh

#=====================================================================
# pingtest.sh, v1.0.1
# Created 2009 by Bennett Lee
# Released to public domain
# https://forum.netgate.com/topic/16217/howto-ping-hosts-and-reset-reboot-on-failure/2
# (1) Attempts to ping several hosts to test connectivity.  After
#     first successful ping, script exits.
# (2) If all pings fail, resets interface and retries all pings.
# (3) If all pings fail again after reset, then reboots pfSense.
#
# History
# 1.0.1   Added delay to ensure interface resets (thx ktims).
# 1.0.0   Initial release.
#=====================================================================

#=====================================================================
# USER SETTINGS
#
# Set multiple ping targets separated by space.  Include numeric IPs
# (e.g., remote office, ISP gateway, etc.) for DNS issues which
# reboot will not correct.
ALLDEST="google.com yahoo.com 24.93.40.36 8.8.8.8"
# Interface to reset, usually your WAN
BOUNCE=ovpnc1
BOUNCE=ovpnc3
BOUNCE=vmx3

# Log file
LOGFILE=/root/pingtest.log
#=====================================================================

COUNT=1
while [ $COUNT -le 2 ]
do

	for DEST in $ALLDEST
	do
		#echo `date +%Y%m%d.%H%M%S` "Pinging $DEST" >> $LOGFILE
		ping -c1 $DEST >/dev/null 2>/dev/null
		if [ $? -eq 0 ]
		then
			#echo `date +%Y%m%d.%H%M%S` "Ping $DEST OK." >> $LOGFILE
			exit 0
		fi
	done

	if [ $COUNT -le 1 ]
	then
		echo `date +%Y%m%d.%H%M%S` "All pings failed. Resetting interface $BOUNCE." >> $LOGFILE
		/sbin/ifconfig $BOUNCE down
		# Give interface time to reset before bringing back up
		sleep 10
		/sbin/ifconfig $BOUNCE up
		# Give WAN time to establish connection
		sleep 60
	else
		echo `date +%Y%m%d.%H%M%S` "All pings failed twice. Rebooting..." >> $LOGFILE
		/sbin/shutdown -r now >> $LOGFILE
		exit 1
	fi

	COUNT=`expr $COUNT + 1`
done

Better post your whole config-file you are using for it. And the names of your interfaces (Interfaces -> Assignments -> WAN vmx1 or onvp1 whatever...They have a special name, also depending on the used hardware.

In general, the only lines you have to edit are in this part:

#=====================================================================
# USER SETTINGS
#
# Set multiple ping targets separated by space.  Include numeric IPs
# (e.g., remote office, ISP gateway, etc.) for DNS issues which
# reboot will not correct.
ALLDEST="google.com yahoo.com 24.93.40.36 8.8.8.8"
# Interface to reset, usually your WAN
BOUNCE=ovpnc1
BOUNCE=ovpnc3
BOUNCE=vmx3

# Log file
LOGFILE=/root/pingtest.log
#=====================================================================

Alldest you can use google.com 8.8.8.8, all public IP addresses, which have a nearly 100% Uptime.
Behind bounce you need to put the interfaces name (which I mentioned above...so NOT WAN, you need to use the "technical" name, like int1 or whatever it is for your hardware.

If it still doesn't work, post your whole script-code you used for it and then we can check, what's going on.

Brig

@teddy The above works a treat! Thanks a lot for taking the time to reply.
For whatever reason my router drops the wan connection every couple of weeks, always whenever I'm out so can't manually reboot. This will solve that issue so thanks again.

Teddy

@brig

You're welcome! Works really properly.

Just don't forget the Cron-Job, switch off the test-log (otherwise your disk will run full) and when you ever have to restore from your config-file, you need to set it up again!

That script is not included in the backup-file! ;)

Enjoy it, the curve is steep, but PFSense is great!

linuxstyl

@Teddy thanks that's what I was looking for and it works in version 2.7.2