Hello,
It seems that in your case pfSence equipment initiates IPsec connection to RUT955 and that RUT955 have Public Dynamic IP address.
In this case, you would not be able to force router's to re-establish IPsec tunnel any faster, since it would take some time for RUT955 to inform DDNS service provider and then pfSence router to acquire new IP address and re-initiate the connection.
I.e. this is not a an issue with RUT955 itself, which could be debugged or resolved. Re-connection delay is inevitable since your pfSence equipment is trying to connect to device, which IP changes overtime and needs to be updated/reacquired periodically.
Nonetheless, you can try playing with RUT955 through SSH (e.g. using Putty software for Windows):
- SSH login: root
- SSH password: <your router's password>
- With "ipsec status" SSH command you can see all active tunnels (including established ones and the ones, which are still "connecting")
- With "logread" command you can see all router's logs form the past and with "logread -f" command you can see all future router's logs. These logs contains whole router's information. In them, you will find DDNS update logs and IPsec logs (which will appear when pfSence router will reach RUT955. You will also see periodic IPsec tunnel keep alive exchanges)