Port Forwarding stopped working after upgrading to 2.8.0
-
i just seen a s.m.a.r.t under diagnostics my bad dislexia missed it... ill do those tests and report back too
-
so i ran the test and the results are
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based SSDs Device Model: ADATA SU650 Serial Number: 2I3620089130 LU WWN Device Id: 0 000000 000000000 Firmware Version: V8X01c45 User Capacity: 120,034,123,776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic, zeroed Device is: In smartctl database 7.3/5528 ATA Version is: ACS-3, ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jul 14 13:58:32 2025 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 1) seconds. Offline data collection capabilities: (0x59) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 3) minutes. Extended self-test routine recommended polling time: ( 11) minutes. SCT capabilities: (0x0039) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 100 100 050 - 0 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 9 Power_On_Hours -O--CK 100 100 000 - 54346 12 Power_Cycle_Count -O--CK 100 100 000 - 199 161 Valid_Spare_Block_Cnt -O--CK 100 100 000 - 33 162 Cache_Block_Count -O--CK 100 100 000 - 706277 163 Initial_Bad_Block_Count -O--CK 100 100 000 - 100 164 Total_Erase_Count -O--CK 100 100 000 - 1509 166 Min_Erase_Count -O--CK 100 100 000 - 132 167 Average_Erase_Count -O--CK 100 100 050 - 0 168 Max_Erase_Count_of_Spec -O--CK 100 100 000 - 0 169 Remaining_Lifetime_Perc -O--CK 100 100 000 - 100 171 Unknown_Attribute -O--CK 100 100 000 - 0 172 Unknown_Attribute -O--CK 100 100 000 - 0 174 Unknown_Attribute -O--CK 100 100 000 - 143 175 Program_Fail_Count_Chip -O--CK 100 100 000 - 0 181 Program_Fail_Cnt_Total -O---K 100 100 000 - 733685 187 Reported_Uncorrect -O--CK 100 100 000 - 0 194 Temperature_Celsius -O---K 100 100 030 - 61 195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0 206 Unknown_SSD_Attribute -O--CK 100 100 000 - 1279 207 Unknown_SSD_Attribute -O--CK 100 100 000 - 1572 232 Available_Reservd_Space -O--CK 100 100 000 - 88 241 Host_Writes_32MiB -O--CK 100 100 000 - 30179 242 Host_Reads_32MiB -O--CK 100 100 000 - 947 249 Unkn_SiliconMotion_Attr -O--CK 100 100 000 - 30444 250 Read_Error_Retry_Rate -O--CK 100 100 000 - 36707 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 2 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 5 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x30 GPL,SL R/O 8 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (2 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 0 (0x0000) Device State: Active (0) Current Temperature: 0 Celsius Power Cycle Min/Max Temperature: 28/28 Celsius Lifetime Min/Max Temperature: 0/36 Celsius Specified Max Operating Temperature: 100 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 0 minutes Temperature Logging Interval: 0 minutes Min/Max recommended Temperature: 0/100 Celsius Min/Max Temperature Limit: -10/125 Celsius Temperature History Size (Index): 128 (1) Index Estimated Time Temperature Celsius 2 2025-07-14 11:51 ? - ... ..(124 skipped). .. - 127 2025-07-14 13:56 ? - 0 2025-07-14 13:57 36 ***************** 1 2025-07-14 13:58 37 ****************** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 199 --- Lifetime Power-On Resets 0x01 0x010 4 54346 --- Power-on Hours 0x01 0x018 6 63292007565 --- Logical Sectors Written 0x01 0x020 6 2112800956 --- Number of Write Commands 0x01 0x028 6 1987291263 --- Logical Sectors Read 0x01 0x030 6 12572061 --- Number of Read Commands 0x01 0x038 6 195639257085 --- Date and Time TimeStamp 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 53 --- Resets Between Cmd Acceptance and Completion 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 3842 --- Number of Hardware Resets 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 1 --- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x000a 4 31 Device-to-host register FISes sent due to a COMRESETthe 2nd option logs
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Error Log Version: 1 No Errors LoggedOffline Test
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART off-line routine immediately in off-line mode". Drive command "Execute SMART off-line routine immediately in off-line mode" successful. Testing has begun. Please wait 1 seconds for test to complete. Test will complete after Mon Jul 14 14:00:32 2025 EDT Use smartctl -X to abort test. and then i did the summary smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based SSDs Device Model: ADATA SU650 Serial Number: 2I3620089130 LU WWN Device Id: 0 000000 000000000 Firmware Version: V8X01c45 User Capacity: 120,034,123,776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic, zeroed Device is: In smartctl database 7.3/5528 ATA Version is: ACS-3, ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jul 14 14:02:02 2025 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 1) seconds. Offline data collection capabilities: (0x59) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 3) minutes. Extended self-test routine recommended polling time: ( 11) minutes. SCT capabilities: (0x0039) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 100 100 050 - 0 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 9 Power_On_Hours -O--CK 100 100 000 - 54347 12 Power_Cycle_Count -O--CK 100 100 000 - 199 161 Valid_Spare_Block_Cnt -O--CK 100 100 000 - 33 162 Cache_Block_Count -O--CK 100 100 000 - 706277 163 Initial_Bad_Block_Count -O--CK 100 100 000 - 100 164 Total_Erase_Count -O--CK 100 100 000 - 1509 166 Min_Erase_Count -O--CK 100 100 000 - 132 167 Average_Erase_Count -O--CK 100 100 050 - 0 168 Max_Erase_Count_of_Spec -O--CK 100 100 000 - 0 169 Remaining_Lifetime_Perc -O--CK 100 100 000 - 100 171 Unknown_Attribute -O--CK 100 100 000 - 0 172 Unknown_Attribute -O--CK 100 100 000 - 0 174 Unknown_Attribute -O--CK 100 100 000 - 143 175 Program_Fail_Count_Chip -O--CK 100 100 000 - 0 181 Program_Fail_Cnt_Total -O---K 100 100 000 - 733685 187 Reported_Uncorrect -O--CK 100 100 000 - 0 194 Temperature_Celsius -O---K 100 100 030 - 61 195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0 206 Unknown_SSD_Attribute -O--CK 100 100 000 - 1279 207 Unknown_SSD_Attribute -O--CK 100 100 000 - 1572 232 Available_Reservd_Space -O--CK 100 100 000 - 88 241 Host_Writes_32MiB -O--CK 100 100 000 - 30180 242 Host_Reads_32MiB -O--CK 100 100 000 - 947 249 Unkn_SiliconMotion_Attr -O--CK 100 100 000 - 30444 250 Read_Error_Retry_Rate -O--CK 100 100 000 - 36707 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 2 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 5 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x30 GPL,SL R/O 8 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (2 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 0 (0x0000) Device State: Active (0) Current Temperature: 0 Celsius Power Cycle Min/Max Temperature: 28/28 Celsius Lifetime Min/Max Temperature: 0/37 Celsius Specified Max Operating Temperature: 100 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 0 minutes Temperature Logging Interval: 0 minutes Min/Max recommended Temperature: 0/100 Celsius Min/Max Temperature Limit: -10/125 Celsius Temperature History Size (Index): 128 (2) Index Estimated Time Temperature Celsius 3 2025-07-14 11:55 ? - ... ..(123 skipped). .. - 127 2025-07-14 13:59 ? - 0 2025-07-14 14:00 36 ***************** 1 2025-07-14 14:01 ? - 2 2025-07-14 14:02 38 ******************* SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 199 --- Lifetime Power-On Resets 0x01 0x010 4 54347 --- Power-on Hours 0x01 0x018 6 63292109227 --- Logical Sectors Written 0x01 0x020 6 2112803922 --- Number of Write Commands 0x01 0x028 6 1987291287 --- Logical Sectors Read 0x01 0x030 6 12572064 --- Number of Read Commands 0x01 0x038 6 195639257085 --- Date and Time TimeStamp 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 53 --- Resets Between Cmd Acceptance and Completion 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 3842 --- Number of Hardware Resets 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 1 --- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x000a 4 31 Device-to-host register FISes sent due to a COMRESETso i ran the 4 tests
offline
short
extended
convenyanceconvenyance failed
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Conveyance Self-test functions not supported Sending command: "Execute SMART Conveyance self-test routine immediately in off-line mode". Command "Execute SMART Conveyance self-test routine immediately in off-line mode" failed: Input/output errorthe other three passed
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 54347 - # 2 Short offline Completed without error 00% 54347 - # 3 Short offline Completed without error 00% 54347and the full summary is after running those 4 tests
smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based SSDs Device Model: ADATA SU650 Serial Number: 2I3620089130 LU WWN Device Id: 0 000000 000000000 Firmware Version: V8X01c45 User Capacity: 120,034,123,776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic, zeroed Device is: In smartctl database 7.3/5528 ATA Version is: ACS-3, ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jul 14 14:29:04 2025 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 1) seconds. Offline data collection capabilities: (0x59) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 3) minutes. Extended self-test routine recommended polling time: ( 11) minutes. SCT capabilities: (0x0039) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 100 100 050 - 0 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 9 Power_On_Hours -O--CK 100 100 000 - 54347 12 Power_Cycle_Count -O--CK 100 100 000 - 199 161 Valid_Spare_Block_Cnt -O--CK 100 100 000 - 33 162 Cache_Block_Count -O--CK 100 100 000 - 706277 163 Initial_Bad_Block_Count -O--CK 100 100 000 - 100 164 Total_Erase_Count -O--CK 100 100 000 - 1509 166 Min_Erase_Count -O--CK 100 100 000 - 132 167 Average_Erase_Count -O--CK 100 100 050 - 0 168 Max_Erase_Count_of_Spec -O--CK 100 100 000 - 0 169 Remaining_Lifetime_Perc -O--CK 100 100 000 - 100 171 Unknown_Attribute -O--CK 100 100 000 - 0 172 Unknown_Attribute -O--CK 100 100 000 - 0 174 Unknown_Attribute -O--CK 100 100 000 - 143 175 Program_Fail_Count_Chip -O--CK 100 100 000 - 0 181 Program_Fail_Cnt_Total -O---K 100 100 000 - 733685 187 Reported_Uncorrect -O--CK 100 100 000 - 0 194 Temperature_Celsius -O---K 100 100 030 - 62 195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0 206 Unknown_SSD_Attribute -O--CK 100 100 000 - 1279 207 Unknown_SSD_Attribute -O--CK 100 100 000 - 1572 232 Available_Reservd_Space -O--CK 100 100 000 - 88 241 Host_Writes_32MiB -O--CK 100 100 000 - 30180 242 Host_Reads_32MiB -O--CK 100 100 000 - 947 249 Unkn_SiliconMotion_Attr -O--CK 100 100 000 - 30444 250 Read_Error_Retry_Rate -O--CK 100 100 000 - 36707 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 2 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 5 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x30 GPL,SL R/O 8 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (2 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 54347 - # 2 Short offline Completed without error 00% 54347 - # 3 Short offline Completed without error 00% 54347 - SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 0 (0x0000) Device State: Active (0) Current Temperature: 0 Celsius Power Cycle Min/Max Temperature: 28/28 Celsius Lifetime Min/Max Temperature: 0/39 Celsius Specified Max Operating Temperature: 100 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 0 minutes Temperature Logging Interval: 0 minutes Min/Max recommended Temperature: 0/100 Celsius Min/Max Temperature Limit: -10/125 Celsius Temperature History Size (Index): 128 (4) Index Estimated Time Temperature Celsius 5 2025-07-14 12:22 ? - ... ..(121 skipped). .. - 127 2025-07-14 14:24 ? - 0 2025-07-14 14:25 36 ***************** 1 2025-07-14 14:26 ? - 2 2025-07-14 14:27 ? - 3 2025-07-14 14:28 ? - 4 2025-07-14 14:29 40 ********************* SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 199 --- Lifetime Power-On Resets 0x01 0x010 4 54347 --- Power-on Hours 0x01 0x018 6 63292814528 --- Logical Sectors Written 0x01 0x020 6 2112820776 --- Number of Write Commands 0x01 0x028 6 1987291311 --- Logical Sectors Read 0x01 0x030 6 12572067 --- Number of Read Commands 0x01 0x038 6 195650130499 --- Date and Time TimeStamp 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 53 --- Resets Between Cmd Acceptance and Completion 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 3842 --- Number of Hardware Resets 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 1 --- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x000a 4 31 Device-to-host register FISes sent due to a COMRESETso dunno if it helps anything for boot up it showed 0 errors and such on when it struggles to reboot
-
Mmm, that seems fine.
So I'd look at the logs for the time. Including if there is a suspicious gap in the logs at that point.
-
@stephenw10
ah ok
so in the logs id just look for a gap in time then and i guess any of the sub headings... ill keep an eye out when it happens and report back ..is my current cpu under powered would that be an issue.. and ill hook up a monitor tonight so i can see any console issues especcially when it fails to reboot
does the system logs show stuff prior to a reboot when i reboot .. like does it save or is it all reset at the reboot..
and its definitely not the 10gtek card? as i know i switched to it as you guys on here mentioned dont use the realtek cards not supported..
always something lol but ill keep an eye out when it happens again
-
I would normally expect to see the logs continue and be filled with restarting processes or errors or similar. But a gap in the logs entirely would also be a clue since it implies it either could not log or logs were lost if you're running ram disks for example.
-
@stephenw10
i dont think i running a ram disk i guess thats like a c drive or d drive but in ram?so i was looking at the logs and my desktop is slugish and it cant work homedepot website right it only partially loads websites or it will give me error that something went wrong... can that also be the pfsense acting up giving me issues? i also have a my vpn fail over issue or so could it be causing trouble? i have a vpn fail over i have one for canada 1 for usa but i disabled the one because everytime i try to do something in canada i get this stupid geo location garbage so i disabled the usa one.. as if i just run canada its fine for certain things if i have usa and canada then it gives me issues with geo location...
but here is the logs anyways
and i still have a 3mbs internet connction where i live they still burry lines for rural country folks and maybe by end of year i can get 1gb which i guess is like 1000 or 8000mbsbut can you see in the logs its just acting like crap
and do you think the current comp i have even though below the minium i googled is still ok?Community Edition System Interfaces Firewall Services VPN Status Diagnostics Help StatusSystem LogsSystemGeneral System Firewall DHCP Authentication IPsec PPP PPPoE/L2TP Server OpenVPN NTP Packages Settings General Gateways Routing DNS Resolver Wireless GUI Service OS Boot Last 500 General Log Entries. (Maximum 500) Jul 14 18:55:58 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:55:58 check_reload_status 481 Reloading filter Jul 14 18:55:58 rc.gateway_alarm 30598 >>> Gateway alarm: PIA_TORONTO_VPNV4 (Addr:1.1.1.1 Alarm:0 RTT:53.723ms RTTsd:19.268ms Loss:16%) Jul 14 18:55:58 check_reload_status 481 updating dyndns PIA_TORONTO_VPNV4 Jul 14 18:55:58 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:55:58 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:55:58 check_reload_status 481 Reloading filter Jul 14 18:55:59 rc.gateway_alarm 32354 >>> Gateway alarm: WAN_PPPOE (Addr:10.11.13.49 Alarm:1 RTT:35.038ms RTTsd:28.000ms Loss:21%) Jul 14 18:55:59 check_reload_status 481 updating dyndns WAN_PPPOE Jul 14 18:55:59 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:55:59 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:55:59 check_reload_status 481 Reloading filter Jul 14 18:55:59 php-fpm 434 /rc.dyndns.update: Dynamic DNS (testserver.mine.nu) There was an error trying to determine the public IP for interface - wan (pppoe0 ). Jul 14 18:55:59 php-fpm 50460 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use WAN_PPPOE. Jul 14 18:55:59 php-fpm 66203 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use PIA_TORONTO_VPNV4. Jul 14 18:56:00 php-fpm 434 /rc.dyndns.update: Dynamic DNS (trilliumjam.mine.nu) There was an error trying to determine the public IP for interface - wan (pppoe0 ). Jul 14 18:56:01 php-fpm 434 /rc.dyndns.update: phpDynDNS (mcproductions.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:56:02 php-fpm 434 /rc.dyndns.update: phpDynDNS (mikeshouse.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:56:03 php-fpm 434 /rc.dyndns.update: phpDynDNS (daddyshouse.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:56:04 php-fpm 434 /rc.dyndns.update: phpDynDNS (sierrasmiles.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:56:05 php-fpm 434 /rc.dyndns.update: Dynamic DNS (rocketchat.mine.nu) There was an error trying to determine the public IP for interface - wan (pppoe0 ). Jul 14 18:56:06 php-fpm 434 /rc.dyndns.update: Dynamic DNS () There was an error trying to determine the public IP for interface - wan (pppoe0 ). Jul 14 18:56:07 php-fpm 434 /rc.dyndns.update: Dynamic DNS (daddykins.mine.nu) There was an error trying to determine the public IP for interface - wan (pppoe0 ). Jul 14 18:56:23 rc.gateway_alarm 93983 >>> Gateway alarm: PIA_TORONTO_VPNV4 (Addr:1.1.1.1 Alarm:1 RTT:53.163ms RTTsd:20.127ms Loss:21%) Jul 14 18:56:23 check_reload_status 481 updating dyndns PIA_TORONTO_VPNV4 Jul 14 18:56:23 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:56:23 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:56:23 check_reload_status 481 Reloading filter Jul 14 18:56:24 php-fpm 50460 /rc.dyndns.update: MONITOR: PIA_TORONTO_VPNV4 has packet loss, omitting from routing group VPN_FAIL_OVER Jul 14 18:56:24 php-fpm 50460 1.1.1.1|10.25.112.45|PIA_TORONTO_VPNV4|53.369ms|20.131ms|21%|down|highloss Jul 14 18:56:24 php-fpm 50460 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 50460 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: Omitting gateway from filter ruleset. Group: "VPN_FAIL_OVER" Gateway: "PIA_TORONTO_VPNV4" IP: "10.25.112.1" Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 22748 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use PIA_TORONTO_VPNV4. Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:24 php-fpm 434 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:56 rc.gateway_alarm 56498 >>> Gateway alarm: WAN_PPPOE (Addr:10.11.13.49 Alarm:0 RTT:47.490ms RTTsd:47.482ms Loss:17%) Jul 14 18:56:56 check_reload_status 481 updating dyndns WAN_PPPOE Jul 14 18:56:56 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:56:56 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:56:56 check_reload_status 481 Reloading filter Jul 14 18:56:58 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 26010 /rc.dyndns.update: phpDynDNS (testserver.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: Omitting gateway from filter ruleset. Group: "VPN_FAIL_OVER" Gateway: "PIA_TORONTO_VPNV4" IP: "10.25.112.1" Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 434 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use WAN_PPPOE. Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:58 php-fpm 38292 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:59 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:59 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:59 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:56:59 php-fpm 26010 /rc.dyndns.update: phpDynDNS (trilliumjam.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:00 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:00 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:00 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:00 php-fpm 26010 /rc.dyndns.update: phpDynDNS (mcproductions.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:01 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:01 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:01 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:01 php-fpm 26010 /rc.dyndns.update: phpDynDNS (mikeshouse.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:02 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:02 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:02 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:02 php-fpm 26010 /rc.dyndns.update: phpDynDNS (daddyshouse.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:03 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:03 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:03 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:03 php-fpm 26010 /rc.dyndns.update: phpDynDNS (sierrasmiles.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:04 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:04 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:04 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:04 php-fpm 26010 /rc.dyndns.update: phpDynDNS (rocketchat.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:05 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:05 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:05 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:05 php-fpm 26010 /rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:57:06 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:06 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:06 php-fpm 26010 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:57:06 php-fpm 26010 /rc.dyndns.update: phpDynDNS (daddykins.mine.nu): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jul 14 18:59:01 rc.gateway_alarm 3197 >>> Gateway alarm: PIA_TORONTO_VPNV4 (Addr:1.1.1.1 Alarm:0 RTT:54.534ms RTTsd:20.744ms Loss:17%) Jul 14 18:59:01 check_reload_status 481 updating dyndns PIA_TORONTO_VPNV4 Jul 14 18:59:01 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:59:01 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:59:01 check_reload_status 481 Reloading filter Jul 14 18:59:02 php-fpm 26010 /rc.dyndns.update: MONITOR: PIA_TORONTO_VPNV4 is available now, adding to routing group VPN_FAIL_OVER Jul 14 18:59:02 php-fpm 26010 1.1.1.1|10.25.112.45|PIA_TORONTO_VPNV4|54.514ms|20.649ms|18%|online|loss Jul 14 18:59:02 php-fpm 38292 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use PIA_TORONTO_VPNV4. Jul 14 18:59:12 rc.gateway_alarm 46826 >>> Gateway alarm: PIA_TORONTO_VPNV4 (Addr:1.1.1.1 Alarm:1 RTT:52.162ms RTTsd:16.742ms Loss:21%) Jul 14 18:59:12 check_reload_status 481 updating dyndns PIA_TORONTO_VPNV4 Jul 14 18:59:12 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:59:12 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:59:12 check_reload_status 481 Reloading filter Jul 14 18:59:13 php-fpm 17474 /rc.dyndns.update: MONITOR: PIA_TORONTO_VPNV4 has packet loss, omitting from routing group VPN_FAIL_OVER Jul 14 18:59:13 php-fpm 17474 1.1.1.1|10.25.112.45|PIA_TORONTO_VPNV4|52.165ms|16.768ms|21%|down|highloss Jul 14 18:59:13 php-fpm 17474 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 17474 /rc.dyndns.update: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: Omitting gateway from filter ruleset. Group: "VPN_FAIL_OVER" Gateway: "PIA_TORONTO_VPNV4" IP: "10.25.112.1" Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 22748 /rc.filter_configure_sync: GATEWAYS: Group VPN_FAIL_OVER did not have any gateways up on tier 1! Jul 14 18:59:13 php-fpm 50460 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use PIA_TORONTO_VPNV4. Jul 14 18:59:26 rc.gateway_alarm 71299 >>> Gateway alarm: PIA_TORONTO_VPNV4 (Addr:1.1.1.1 Alarm:0 RTT:53.458ms RTTsd:20.524ms Loss:19%) Jul 14 18:59:26 check_reload_status 481 updating dyndns PIA_TORONTO_VPNV4 Jul 14 18:59:26 check_reload_status 481 Restarting IPsec tunnels Jul 14 18:59:26 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 18:59:26 check_reload_status 481 Reloading filter Jul 14 18:59:27 php-fpm 26010 /rc.dyndns.update: MONITOR: PIA_TORONTO_VPNV4 is available now, adding to routing group VPN_FAIL_OVER Jul 14 18:59:27 php-fpm 26010 1.1.1.1|10.25.112.45|PIA_TORONTO_VPNV4|53.754ms|20.46ms|18%|online|loss Jul 14 18:59:27 php-fpm 38292 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use PIA_TORONTO_VPNV4. Jul 14 19:00:00 php 57588 [pfBlockerNG] Starting cron process. Jul 14 19:00:43 php 57588 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload Jul 14 19:02:44 rc.gateway_alarm 20187 >>> Gateway alarm: WAN_PPPOE (Addr:10.11.13.49 Alarm:1 RTT:30.610ms RTTsd:13.802ms Loss:21%) Jul 14 19:02:44 check_reload_status 481 updating dyndns WAN_PPPOE Jul 14 19:02:44 check_reload_status 481 Restarting IPsec tunnels Jul 14 19:02:44 check_reload_status 481 Restarting OpenVPN tunnels/interfaces Jul 14 19:02:44 check_reload_status 481 Reloading filter -
ok i not able to post my logs right
here is my one drive and i posted it in a text file
log fileand what also drives me crazy is if i google and i goto a link i get this stupid googleservices and it wont let me goto the damn link is there anything in pfsense can fix that problem
constant bs i tell yahere is a screen shot for the vpn gateway fail over
so i used to have both to tier 1 in the past but i watched another video they said
you do Tier 1 and Tier 2 so you have the usa first and if it fails it moves to 2nd one..i also enabled the interface for new york vpn but i still get those gateway errors... do you think its killing the php stalling it from all those errors of the tier 1 no gateway?
as i made this this way so i can switch back and forth from usa to canada if needed but mostly stick on the canada one
-
The logs look like you're seeing packet loss on the PPPoE WAN and then obviously seeing similar loss on all the VPNs that are over the WAN.
That in turn is triggering other processes for each gateway event.The first thing I would do there is set an external monitoring IP on the WAN so you're not reliant on the ISP gateway responding to pings.
Are you routing all traffic via that VPN gateway group?
-
so i have my network split so some IPs go out the VPN and others go out the WAN
so the WAN has a built in monitor IP the 2 vpns i set the monitor ips from setups setting up PIA
and what does the monitor IP actually do?
and what ip should i set it?so you mentioned to change the monitor ip from the isp whats the purpose of that.. for like when i mention it seems to stall out and then i can sometimes ping 1.1.1.1 but i cant ping google.ca or any dns name just ip address..
and here is the screen shot
-
and i dont know why the one vpn says dynamic both should say dynamic in the settings but one replaces the dynamic with an ip
-
@stephenw10
i added some new logsi set the Wan monitor to 1.0.0.1 i couldnt set it to 1.1.1.1 and i lost interent nothing worked.. i could ping 1.1.1.1 from the desktop but i couldnt ping google.ca
i had to reboot pfsense
so i got a log of the wan monitor ip 1.0.0.1 and one after i rebooted same link as i sent ya
-
The gateway monitoring serves two purposes. It generates data for the WAN quality logging in Status > Monitoring so you can see how your WAN varies over time. It is used to detect a connection that has failed (depending how that is defined) so in a gateway group it can be added or removed; like you have with the VPN group.
Since you only have one real WAN you don't need a failover action with that so you could set
Disable Gateway Monitoring Actionon that. That way it won't trigger unnecessary service starts when there is packet loss on it. You need that action on the VPN gateways in order to failover between them but you could set the thresholds higher so 20% packet loss doesn't trigger it if you regularly see that.The NY VPN shows as 'dynamic' because it's not connected. That gateway IP is pushed by the server when it connects.
1.0.0.1 should be valid as a monitoring IP, I would expect that to work fine normally.
How do you have DNS configured? Is it setup to only use the VPN gateways for example? That would explain why you could ping an IP but not resolve anything if the VPN is reconnecting.
Also when you set those monitoring IPs pfSense adds a static route to them via the gateway they're on. So when testing connectivity from a LAN side client you should avoid any of those IPs in order to not get static routed via that.
-
@stephenw10
ok so
1.. i added 2 more logs from last night where it was locking up my desktop to pfsense or internet and seems to be that fail over2... i set the 1.0.0.1 for the wan at the moment and i can try that 20% threshold
3.. i enabled the 2nd vpn for fail over to see if it locks up
3.. i must have a Routing issues on my Desktop i use like 192.168.0.49 for No VPN and 192.168.0.151 to be on the VPN as i have it split vpn and no vpn ips... and i got vlans
now what i mentioned before on my desktop if i try to search on Homedepot.ca and i get error from there site saying something went wrong... now i can test on my ubuntu VM on my dmz vlan 192.168.40.x which uses WAN and it can search fine... so then i went and tested on my laptop i connect to my LAN and search same item on home depot and i get that same error something went wrong... but if i connect laptop which running windows 11 like the desktop then the search works fine... as i thought maybe its a windows 11 vs ubuntu issue but it wasnt
as for DNS this is what i got setup but i dunno if its the Routing Bypass Policy causing the issue?
but here is what i got
and the 103.x.x.x DNS thats i still got in there from nordvpn i can delete those i guess i didnt yet
so i thinking i got couple issues that routing you meentioned that could be killing php or i thinking comp not powerful enough and its just stalling out
but cpu usage at moment is just 7%but here is some screen shots maybe i configured things wrong
and i wish on the DNS page you could set like 1.1.1.1 for WAN interface but then keeps VPN and WAN seperate so there is no vpn leakage but it doesnt work that way.. i do have a no wan egreess toobut here is my screen shots. you probably see something i configured wrong
![pfsense 8.png]
(/assets/uploads/files/1752588584425-pfsense-8.png)oh so when i have 1.1.1.1 1.0.0.1 monitoring ips dont test those ips for pining ping some other ip as it always knows that route there so gives a false postivie i take it
-
i going to try tommorow or later tonight i going to use one of my backup servers with a amd 3700x i think
i going to install pfsense on a ssd and import the current config and then set it to the 2 nics i got in there and test it,. to see if it locks me out too like i been experiencing in case my 1.5 4 core cpu isnt powerful anymore -
so here is searching home depot on the LAN this is with or without behind the vpn
and this here is same search HD on the DMZ network
so definitely i got something configured wrong
-
@stephenw10 said in Port Forwarding stopped working after upgrading to 2.8.0:
1.0.0.1 should be valid as a monitoring IP, I would expect that to work fine normally.
FWIW, Cloudflare appears to have had an ICMP hiccup on the West coast yesterday from approximately 14:50 to 15:50 PT. Both 1.0.0.1 and 1.1.1.1 experienced significant on again / off again loss during that time.
-
@dennypage said in Port Forwarding stopped working after upgrading to 2.8.0:
Cloudflare appears to have had an ICMP hiccup
Yup, good point. That could be causing confusion troubleshooting.
But @comet424 how do you have DNS setup for LAN clients? Are they using pfSense (Unbound) for DNS? If so how is Unbound configured? Forwarding to the DNS servers you have configured? Those will only be available via the VPNs. You should remove the NordVPN servers if you're not using NordVPN.
-
@stephenw10
sorry i ment to get back to you yesterdayso.. if you mean if cloudflare is doing that woth home depot where it shows something wrong thats been going on for a year so i figured it was a vpn issue but when i transfered from nordvpn to pia vpn i still had that issue.. also if i search in google and goto home depot webpage it will load part of the page but it wont display like the prices or anything like that.. also have the same issue with Canadian Tire and some other sites.. i figured it was like a double nat thing or something..
2nd.. my pfsense locked me out again i added another log file to the link when i got back in 10 min after it locked me out well froze me out i wasnt able to ping 192.168.0.1 from the desktop couldnt ssh ... but i got the log file and saved it
but i could ssh in Unraid and i could ssh into pfsense no problem i tried the restart the php-frm that didnt do anything and i couldnt ping google.ca from the shell command but i could ping 1.1.1.1 but weird thing is i couldnt access from my desktop on the 192.168.0.49 ip yet my unraid is on 192.168.0.3 and i could ssh in.. so its like it buggers up the windows dns or whatever wierd but i forgot to test my vm ubuntu on the dmz 192.168.40.x
and i did get a chance to test it on the 8 core cpu gaming motherboard i had stuff to do and didnt get to test it to see if the comp is too slow
but to address your dns stuff
for 192.168.0.x i use 192.168.0.1 as dns
for my IOT 192.168.20.x dns 192.168.20.1
my camera network 192.168.10.x dns 192.168.10.1
my management ip network 192.168.30.x dns 192.168.30.1
my dmz network 192.168.40.x 192.168.40.1now the management port network i disable the internet as i was having issue of files and internet working through it and not the 192.168.0.1 i use the management port network to be able to WAke on Lan as you cant wake on lan Fiber which some of my comps are 10g fiber network
so ya i ended up having to reboot pfsense just to get it working it seems if it stalls or kills php or so its basiclly useless it doesnt come back to working vpn or not vpn clients trying to reconnect my openvpn connections dont wanna re connect and if they do you cant ping crap.. but when you do a reboot its working again..
so i not sure if you can see anything from the logs but its getting frustrating tommorow for sure i going to run pfsense on my gaming comp to see if its crapping out on there too.. cuz its getting stupid like i dunno why DMZ network can access internet fine like home depot displays fine but LAN doesnt
and with the laptop if i connect to the LAN homedepot will give that error something wrong everytime or wont load pages right.. but you connect to the dmz side and it has no issues. as i was figuring it was just the desktop pc issues but no happens same way on 2 comps.. but basiclly my lan and DMZ use the same in the rules you see nothing special... unless the bypass routing is causing issues or of the pf blockNG and if it has to go after the routing bypass policy as i read that has to be first when splitting wan an vpn to go different routes..
sorry if i confusing too i have dyslexia so it sounds right in my head but may confuse people at times.. so bear with me too...
oh ya also i wasnt able to access 192.168.0.1 through firefox as a docker on unraid it locked out the gui but i was still able to ssh from unraid... but once i rebooted and such i could also gui pfsense from the firefox on the unraid.. its weird how i could ssh from unraid gui but not from windows cmd shell when it froze up or so.. like its a windows hater lol
-
i also figure maybe cuz of my 3mb/s internet connection where i supposed to get 5mbit on dsl when it maxes out and bad phone line i get that it stalls out and messes up pfsense and it just craps out pfsense
so that fiber 1gb cant come soon enough sometime between now and the end of the year as maybe it wont crash with the 1gb but that cant solve the home depot example i did thats gotta be something miss configured i got
-
@comet424 said in Port Forwarding stopped working after upgrading to 2.8.0:
so.. if you mean if cloudflare is doing that woth home depot where it shows something wrong
No I meant if you are testing connectivity against 1.1.1.1/1.0.0.1 that might have returned false failures yesterday because Cloudflare was having issues. But it could also have applied to cloudflare proxied sites.
@comet424 said in Port Forwarding stopped working after upgrading to 2.8.0:
but i could ssh in Unraid and i could ssh into pfsense no problem
You couldn't ssh into pfSense directly but you could ssh into Unraid and then ssh into pfSense from there?
That sounds more like either pfSense blocking your IP or you have some routing error or IP conflict perhaps.
