Current version:
FreeNAS-11.2-U5
(Build Date: Jun 24, 2019 18:41)
Two zpools:
Pool A = Encrypted SSD for running jails and VMs
Pool B = Encrypted ZFS RAIDZ2 as large storage
Almost daily my ISP seems to force a WAN IP readdress change, it is never the same each day, which directly impacts my Freenas server. I'm forced to go into Freenas to unlock the encrypted pools then allowing storage to be accessed, jails can start, VMs can start. Some jail and VMs do run over a policy routed VPNs, based on jail/VM source IP.
I'm not sure if this is by design? I only changed ISP broadband service last week and it has restarted 4 times. My previous ISP kept the same WAN IP, stayed mainly stagnant.
There's nothing in dmesg logs that shows a serious error, failure, kernel panic or other for last reboot.
Thoughts?
FreeNAS-11.2-U5
(Build Date: Jun 24, 2019 18:41)
Two zpools:
Pool A = Encrypted SSD for running jails and VMs
Pool B = Encrypted ZFS RAIDZ2 as large storage
Almost daily my ISP seems to force a WAN IP readdress change, it is never the same each day, which directly impacts my Freenas server. I'm forced to go into Freenas to unlock the encrypted pools then allowing storage to be accessed, jails can start, VMs can start. Some jail and VMs do run over a policy routed VPNs, based on jail/VM source IP.
I'm not sure if this is by design? I only changed ISP broadband service last week and it has restarted 4 times. My previous ISP kept the same WAN IP, stayed mainly stagnant.
There's nothing in dmesg logs that shows a serious error, failure, kernel panic or other for last reboot.
Thoughts?