Core 170 testing: IPSec/alias-IP failiure

we use 3 public (red) alias IPs with our IPFire. Two of them are used only for ipsec-n2n-connenctions. The third one is used for a web server in orange. After upgrading to core 170 (development) the two alias-IPs for ipsec seemed ‘dead’: no answer to ping, no open ports, no ipsec-connection established. IPSec-log told : ‘error writing to socket: Network is unreachable’. - The webserver on alias-IP #3 was working properly.

Because this is a production machine, we had to roll back to core 169 immediately and unfortunately have no further information on this case.

a bug report is filed.

1 Like