2.4.5 on Hyper-v network issues
-
Hi i have a carp setup and both VM's had to be rebuilt using the 2.4.5 iso, as after an upgrade the network just constantly drops out to the point I cannot console to the VM. I still have the issue on one of the two VM's how is it best to provide feedback and necessary log files. It worked fine on 2.4.4 p3
Its seems to happen whenever there is a change and it needs to do a xmlrpc sync, it just drops everything.
Last 50 General Log Entries. (Maximum 50)
Apr 15 15:35:02 php-fpm 71141 /xmlrpc.php: Beginning configuration backup to https://acb.netgate.com/save Apr 15 15:35:02 check_reload_status Syncing firewall Apr 15 15:34:26 php-fpm 28965 /xmlrpc.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1586961266] unbound[87551:0] error: bind: address already in use [1586961266] unbound[87551:0] fatal error: could not open ports' Apr 15 15:34:22 php-cgi servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver) Apr 15 15:34:21 check_reload_status Reloading filter Apr 15 15:34:21 check_reload_status Restarting OpenVPN tunnels/interfaces Apr 15 15:34:21 check_reload_status Restarting ipsec tunnels Apr 15 15:34:21 check_reload_status updating dyndns WANGW Apr 15 15:34:21 rc.gateway_alarm 58758 >>> Gateway alarm: WANGW (Addr:x.x.x.xAlarm:1 RTT:5944.953ms RTTsd:11889.176ms Loss:0%) Apr 15 15:33:41 php-fpm 28965 /xmlrpc.php: Resyncing OpenVPN instances. Apr 15 15:33:41 check_reload_status Reloading filter Apr 15 15:33:41 php-fpm 28965 /xmlrpc.php: Configuring CARP settings finalize... Apr 15 15:33:41 php-fpm 28965 /xmlrpc.php: pfsync done in 30 seconds. Apr 15 15:33:09 php-fpm 60687 /rc.carpbackup: HA cluster member "(10.10.10.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 1 Apr 15 15:33:09 php-fpm 55553 /rc.carpbackup: HA cluster member "(192.168.11.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 8 Apr 15 15:33:09 php-fpm 255 /rc.carpbackup: HA cluster member "(192.168.8.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 7 Apr 15 15:33:09 php-fpm 28965 /xmlrpc.php: waiting for pfsync... Apr 15 15:33:09 php-fpm 60687 /rc.carpbackup: HA cluster member "(10.10.10.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 1 Apr 15 15:33:09 php-fpm 56446 /rc.carpbackup: HA cluster member "(192.168.8.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 7 Apr 15 15:33:09 php-fpm 99662 /rc.carpbackup: HA cluster member "(192.168.11.1@hn1): (LAN)" has resumed CARP state "BACKUP" for vhid 8 Apr 15 15:33:09 php-fpm 255 /rc.carpbackup: HA cluster member "(194.66.190.201@hn0): (WAN)" has resumed CARP state "BACKUP" for vhid 6 Apr 15 15:33:09 php-fpm 55553 /rc.carpbackup: HA cluster member "(194.66.190.201@hn0): (WAN)" has resumed CARP state "BACKUP" for vhid 6 Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 kernel carp: 1@hn1: BACKUP -> INIT (hardware interface up) Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel carp: 8@hn1: BACKUP -> INIT (hardware interface up) Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel carp: 7@hn1: BACKUP -> INIT (hardware interface up) Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn1: 3 Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 kernel carp: 6@hn0: BACKUP -> INIT (hardware interface up) Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn0: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn0: 3 Apr 15 15:33:08 kernel ifa_maintain_loopback_route: deletion failed for interface hn0: 3 Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 kernel carp: 1@hn1: INIT -> BACKUP (initialization complete) Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 kernel carp: 8@hn1: INIT -> BACKUP (initialization complete) Apr 15 15:33:08 check_reload_status Carp backup event Apr 15 15:33:08 kernel carp: 7@hn1: INIT -> BACKUP (initialization complete) Apr 15 15:33:08 check_reload_status Carp backup event Last 50 Gateways Log Entries. (Maximum 50) Apr 15 15:36:44 dpinger WANGW 194.66.190.254: Alarm latency 6149988us stddev 12299249us loss 0% Apr 15 15:36:10 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:34:13 dpinger WANGW 194.66.190.254: Alarm latency 5944953us stddev 11889176us loss 0% Apr 15 15:33:41 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:30:29 dpinger WANGW 194.66.190.254: Clear latency 387us stddev 269us loss 0% Apr 15 15:27:30 dpinger WANGW 194.66.190.254: Alarm latency 949995us stddev 2511752us loss 20% Apr 15 15:27:21 dpinger WANGW 194.66.190.254: Alarm latency 1266517us stddev 2830392us loss 14% Apr 15 15:27:15 dpinger WANGW 194.66.190.254: Alarm latency 814us stddev 747us loss 33% Apr 15 15:26:40 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:24:45 dpinger WANGW 194.66.190.254: Clear latency 408us stddev 544us loss 0% Apr 15 15:22:46 dpinger WANGW 194.66.190.254: Alarm latency 5990450us stddev 11979194us loss 0% Apr 15 15:22:14 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:21:15 dpinger WANGW 194.66.190.254: Alarm latency 5983841us stddev 11966806us loss 0% Apr 15 15:20:42 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:11:10 dpinger WANGW 194.66.190.254: Clear latency 313585us stddev 2793287us loss 0% Apr 15 15:06:02 dpinger WANGW 194.66.190.254: Alarm latency 815431us stddev 4681888us loss 0% Apr 15 15:05:15 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 15:00:49 dpinger WANGW 194.66.190.254: Clear latency 363us stddev 53us loss 0% Apr 15 14:58:55 dpinger WANGW 194.66.190.254: Alarm latency 656974us stddev 3936149us loss 0% Apr 15 14:58:23 dpinger WANGW 194.66.190.254: Clear latency 409464us stddev 2902165us loss 0% Apr 15 14:56:48 dpinger WANGW 194.66.190.254: Alarm latency 5617898us stddev 11235079us loss 0% Apr 15 14:56:17 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 14:55:17 dpinger WANGW 194.66.190.254: Alarm latency 5490632us stddev 10980559us loss 0% Apr 15 14:54:47 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 15 00:11:20 dpinger WANGW 194.66.190.254: Clear latency 370us stddev 35us loss 0% Apr 15 00:09:32 dpinger WANGW 194.66.190.254: Alarm latency 524703us stddev 3626696us loss 0% Apr 14 19:46:44 dpinger WANGW 194.66.190.254: Clear latency 353us stddev 46us loss 0% Apr 14 19:44:50 dpinger WANGW 194.66.190.254: Alarm latency 5528570us stddev 11056380us loss 0% Apr 14 19:44:20 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 14 19:43:32 dpinger WANGW 194.66.190.254: Alarm latency 1553223us stddev 5145106us loss 6% Apr 14 19:42:09 dpinger WANGW 194.66.190.254: Alarm latency 1379664us stddev 2758629us loss 16% Apr 14 19:42:04 dpinger WANGW 194.66.190.254: Alarm latency 350us stddev 50us loss 33% Apr 14 19:41:33 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 13 19:46:34 dpinger WANGW 194.66.190.254: Clear latency 347us stddev 56us loss 0% Apr 13 19:44:41 dpinger WANGW 194.66.190.254: Alarm latency 5295015us stddev 10589275us loss 0% Apr 13 19:44:11 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 13 19:42:42 dpinger WANGW 194.66.190.254: Alarm latency 5321686us stddev 10642625us loss 0% Apr 13 19:42:13 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 13 00:12:40 dpinger WANGW 194.66.190.254: Clear latency 461us stddev 401us loss 0% Apr 13 00:10:50 dpinger WANGW 194.66.190.254: Alarm latency 555825us stddev 3840999us loss 0% Apr 12 20:39:22 dpinger WANGW 194.66.190.254: Clear latency 324749us stddev 1454433us loss 0% Apr 12 20:38:56 dpinger WANGW 194.66.190.254: Alarm latency 513089us stddev 1722205us loss 0% Apr 12 20:38:39 dpinger WANGW 194.66.190.254: Alarm latency 1338669us stddev 1338321us loss 0% Apr 12 20:38:37 dpinger WANGW 194.66.190.254: Alarm latency 0us stddev 0us loss 100% Apr 12 20:38:35 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Apr 12 20:38:28 dpinger WANGW 194.66.190.254: Clear latency 358295us stddev 1612919us loss 0% Apr 12 20:37:53 dpinger WANGW 194.66.190.254: Alarm latency 1292525us stddev 2889292us loss 0% Apr 12 20:37:42 dpinger WANGW 194.66.190.254: Alarm latency 1551267us stddev 3101767us loss 0% Apr 12 20:37:35 dpinger WANGW 194.66.190.254: Alarm latency 371us stddev 16us loss 25% Apr 12 20:37:31 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.66.190.254 bind_addr 194.66.190.225 identifier "WANGW " Last 50 Routing Log Entries. (Maximum 50) Apr 15 15:37:59 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:37:52 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:37:43 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:37:33 radvd 68378 resuming normal operation Apr 15 15:37:33 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:37:33 radvd 68378 attempting to reread config file Apr 15 15:37:23 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:52 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:43 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:27 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:20 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:11 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:36:05 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:56 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:49 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:40 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:34 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:24 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:14 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:04 radvd 68378 resuming normal operation Apr 15 15:35:04 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:04 radvd 68378 attempting to reread config file Apr 15 15:35:02 radvd 68378 resuming normal operation Apr 15 15:35:02 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:35:02 radvd 68378 attempting to reread config file Apr 15 15:34:59 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:34:53 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:34:36 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:34:26 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:34:21 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:34:13 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:40 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:30 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:20 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:15 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:08 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:33:00 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:54 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:47 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:38 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:31 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:23 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:16 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:11 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:32:02 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:31:55 radvd 68378 sendmsg: Can't assign requested address Apr 15 15:31:45 radvd 68378 sendmsg: Can't assign requested address Last 50 DNS Resolver Log Entries. (Maximum 50) Apr 15 15:38:17 unbound 86608:0 info: start of service (unbound 1.9.6). Apr 15 15:38:16 unbound 86608:0 notice: init module 0: iterator Apr 15 15:37:32 filterdns Adding Action: pf table: XN_wslc_Server host: wslc.walsall.gov.uk Apr 15 15:37:32 filterdns merge_config: configuration reload Apr 15 15:36:51 filterdns Adding Action: pf table: XN_wslc_Server host: wslc.walsall.gov.uk Apr 15 15:36:51 filterdns merge_config: configuration reload Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 11: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 11: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 10: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 10: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 9: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 9: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 8: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 8: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 7: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 7: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 6: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 6: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 5: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 5: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: 0.004096 0.008192 1 Apr 15 15:36:10 unbound 79108:0 info: lower(secs) upper(secs) recursions Apr 15 15:36:10 unbound 79108:0 info: [25%]=0 median[50%]=0 [75%]=0 Apr 15 15:36:10 unbound 79108:0 info: histogram of recursion processing times Apr 15 15:36:10 unbound 79108:0 info: average recursion processing time 0.007776 sec Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 4: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 4: 1 queries, 0 answers from cache, 1 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: 0.065536 0.131072 3 Apr 15 15:36:10 unbound 79108:0 info: 0.008192 0.016384 3 Apr 15 15:36:10 unbound 79108:0 info: 0.004096 0.008192 3 Apr 15 15:36:10 unbound 79108:0 info: lower(secs) upper(secs) recursions Apr 15 15:36:10 unbound 79108:0 info: [25%]=0.007168 median[50%]=0.012288 [75%]=0.08192 Apr 15 15:36:10 unbound 79108:0 info: histogram of recursion processing times Apr 15 15:36:10 unbound 79108:0 info: average recursion processing time 0.035902 sec Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 2: requestlist max 4 avg 2.88889 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 2: 12 queries, 3 answers from cache, 9 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Apr 15 15:36:10 unbound 79108:0 info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Apr 15 15:36:10 unbound 79108:0 info: service stopped (unbound 1.9.6). Apr 15 15:35:48 unbound 79108:0 info: start of service (unbound 1.9.6). Apr 15 15:35:47 unbound 79108:0 notice: init module 0: iterator Apr 15 15:35:01 filterdns Adding Action: pf table: XN_wslc_Server host: 123.doman.com Apr 15 15:35:01 filterdns merge_config: configuration reload Apr 15 15:34:23 filterdns Adding Action: pf table: XN_wslc_Server host: 123.doman.com Apr 15 15:34:23 filterdns merge_config: configuration reload Apr 15 15:33:41 unbound 71461:0 info: server stats for thread 11: requestlist max 0 avg 0 exceeded 0 jostled 0 -
Try 1 CPU core?
see https://forum.netgate.com/topic/151819/2-4-5-high-latency-and-packet-loss-not-in-a-vm/ and other recent posts.
edit: yes I'm aware the subject says "not in a VM" :) There are however other similar posts about 2.4.5. -
This seems to be the same issue as many posts widely reporting serious issues with 2.4.5
Ignore the titles, but if you read these threads you'll see similar problems to what you are describing;
https://forum.netgate.com/topic/151698/upgrade-ha-cluster-2-4-4-p3-to-2-4-5-persistent-carp-maintenance-mode-causes-gateway-instability
https://forum.netgate.com/topic/151819/2-4-5-high-latency-and-packet-loss-not-in-a-vm
https://forum.netgate.com/topic/151690/increased-memory-and-cpu-spikes-causing-latency-outage-with-2-4-5
-
Yeah, it's almost certainly all the same root cause. We are working to find and resolve that.
For some reason it seems to affect Hyper-V especially badly.Going to 1 CPU core will likely work around it, at obvious expense, until we do.
Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.