Core Update 204 has been released for Testing.
https://www.ipfire.org/blog/ipfire-2-29-core-update-204-is-available-for-testing
Please take the opportunity to evaluate it and raise any bugs if issues are found
Reporting a bug
Also feel free to report if no problems are found.
Upgrade from 203 to 204 aarch64.
Everything works fine: VPN (openvpn, wireguard), DNS Firewall, Wlan, etc.
Wireguard – If the imported configuration file contains an IPv6 interface address (e.g. ProtonVPN), an error occurs
Oops, something went wrong...
The name is already in use
[Interface]
PrivateKey =
Address = 10.2.0.2/32, 2a07:b944::2:2/128
Once the IPv6 address has been removed, the import and connection proceed without any problems
[Interface]
PrivateKey =
Address = 10.2.0.2/32
Regards
IPFire WireGuard + NordVPN
I’m afraid that, at the moment, importing the NordVPN configuration file results in an error
[Interface]
PrivateKey =
Address = 10.5.0.2/16
DNS = 103.86.96.100
[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0
Endpoint = oslo.no.wg.nordhold.net:51820
PersistentKeepalive = 25
Following a test update to 10.5.0.2/32, the import is successful with no visible errors, but the connection fails
My second test for CU204 (VMs Test Platform):
Backup CU203 - Install CU204 Development Build: master/ff46d1ea ISO + Restore Backup
All work fine: DNS over TLS, URLFilter (toulouse blacklist), DNS Firewall, Wiregard, OpenVPN, Captive portal
Only error in /var/log/message on reboot
(Same issue declared yet for CU205 here 14052 – Knot Resolver on IPFire Core Update 205 crashes when it is shut down.)
Oct 3 18:55:48 ipfireTest supervisord: received SIGTERM indicating exit request
Oct 3 18:55:48 ipfireTest supervisord: waiting for cache-gc, kresd0, kresd1, kresd2, kresd3, manager to die
Oct 3 18:55:49 ipfireTest knot_resolver.manager.server: Received SIGINT, triggering graceful shutdown
Oct 3 18:55:49 ipfireTest supervisord: ignoring ready notification from unregistered PID=1890
Oct 3 18:55:49 ipfireTest knot_resolver.manager.server: Stopping API service...
Oct 3 18:55:49 ipfireTest knot_resolver.manager.server: Stopping kresd manager...
Oct 3 18:55:49 ipfireTest knot_resolver.manager.server: The manager run for 1226 seconds...
Oct 3 18:55:49 ipfireTest supervisord: stopped: manager (exit status 0)
Oct 3 18:55:49 ipfireTest supervisord: stopped: kresd1 (terminated by SIGSEGV)
Oct 3 18:55:49 ipfireTest kernel: kresd[1899]: segfault at 4c7a88 ip 000000000042622e sp 00007ffff9ca0160 error 4 in kresd[2622e,409000+2e000] likely on CPU 0 (core 0, socket 0)
Oct 3 18:55:49 ipfireTest kernel: Code: 41 55 41 54 4c 8d 25 31 39 02 00 55 48 89 fd 53 48 83 ec 28 8b 87 7c 01 00 00 89 54 24 04 48 c1 e0 04 48 89 4c 24 18 4c 01 e0 <4c> 8b 78 08 4c 39 fe 0f 83 8d 00 00 00 4c 8b 28 48 8d 44 24 18 48
Oct 3 18:55:49 ipfireTest kernel: kresd[1897]: segfault at 4c24a8 ip 000000000042622e sp 00007fffadadb1c0 error 4 in kresd[2622e,409000+2e000] likely on CPU 1 (core 1, socket 0)
Oct 3 18:55:49 ipfireTest kernel: Code: 41 55 41 54 4c 8d 25 31 39 02 00 55 48 89 fd 53 48 83 ec 28 8b 87 7c 01 00 00 89 54 24 04 48 c1 e0 04 48 89 4c 24 18 4c 01 e0 <4c> 8b 78 08 4c 39 fe 0f 83 8d 00 00 00 4c 8b 28 48 8d 44 24 18 48
Oct 3 18:55:49 ipfireTest kernel: kresd[1898]: segfault at 4c94e8 ip 000000000042622e sp 00007fff04c991d0 error 4 in kresd[2622e,409000+2e000] likely on CPU 2 (core 2, socket 0)
Oct 3 18:55:49 ipfireTest kernel: Code: 41 55 41 54 4c 8d 25 31 39 02 00 55 48 89 fd 53 48 83 ec 28 8b 87 7c 01 00 00 89 54 24 04 48 c1 e0 04 48 89 4c 24 18 4c 01 e0 <4c> 8b 78 08 4c 39 fe 0f 83 8d 00 00 00 4c 8b 28 48 8d 44 24 18 48
Oct 3 18:55:49 ipfireTest kernel: kresd[1896]: segfault at 4c70c8 ip 000000000042622e sp 00007fffc8ed02c0 error 4 in kresd[2622e,409000+2e000] likely on CPU 0 (core 0, socket 0)
Oct 3 18:55:49 ipfireTest kernel: Code: 41 55 41 54 4c 8d 25 31 39 02 00 55 48 89 fd 53 48 83 ec 28 8b 87 7c 01 00 00 89 54 24 04 48 c1 e0 04 48 89 4c 24 18 4c 01 e0 <4c> 8b 78 08 4c 39 fe 0f 83 8d 00 00 00 4c 8b 28 48 8d 44 24 18 48
Oct 3 18:55:49 ipfireTest supervisord: stopped: kresd2 (terminated by SIGSEGV)
Oct 3 18:55:49 ipfireTest supervisord: stopped: kresd3 (terminated by SIGSEGV)
Oct 3 18:55:49 ipfireTest supervisord: stopped: kresd0 (terminated by SIGSEGV)
Oct 3 18:55:49 ipfireTest supervisord: stopped: cache-gc (exit status 0)
A client connection is not and never has been supported by IPFire for WireGuard or OpenVPN. This is not something specific to CU204.
https://community.ipfire.org/t/ipfire-connection-to-nordvpn-via-wireguard-openvpn/16175/6
It has been tested and works with ProtonVPN 
https://community.ipfire.org/t/protonvpn-and-wireguard/
You were there too, Adolf. 
Warm regards.
I just tested the CU204 Development Build: master/ff46d1ea
On my N100 + RPi4 test machines with keepalived.
No upgrade CU203 to CU204 problems detected.
Another testing build has been released (master/88a55eb) which should have fixed the segfault.
Thanks,
A G
Test CU204 Development Build: master/88a55eb0
DNS Ko, see log messages errors
Oct 6 16:06:11 ipfireTest kresd[9994]: [system] assertion "(data->session->transport.type == SESSION2_TRANSPORT_IO && data->session->transport.io.handle == handle)" failed in on_session2_handle_close@../daemon/session2.c:1780
Oct 6 16:06:11 ipfireTest supervisord: exited: kresd0 (terminated by SIGABRT; not expected)
Test Last CU204 Development Build: master/aefdb657
Install and upgrade, no more errors.