136
20.1 Legacy Series / Re: Permanent VNSTAT database on MFS
« on: February 05, 2020, 09:41:50 am »
Exactly!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
137
20.1 Legacy Series / Re: Permanent VNSTAT database on MFS
« on: February 04, 2020, 04:52:44 pm »
I found others posted to this thread in the past, and got notification about this issue recently.
https://github.com/opnsense/plugins/issues/1061
https://github.com/opnsense/plugins/issues/1061
138
20.1 Legacy Series / Permanent VNSTAT database on MFS
« on: February 04, 2020, 03:30:04 pm »
Hello Opnsense folks,
https://forum.opnsense.org/index.php?topic=9503.msg48562#msg48562
is this something that we can expect to be supported? VNSTAT database to be kept across reboots, when /var is on MFS.
https://forum.opnsense.org/index.php?topic=9503.msg48562#msg48562
is this something that we can expect to be supported? VNSTAT database to be kept across reboots, when /var is on MFS.
139
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: December 19, 2019, 03:30:29 pm »
Thanks for your effort, this one was a really interesting test series.
The reason why I am suspecting the pppoe encapsulation is a serious limiting factor, that the internet is full of articles that all says the same thing: the pppoe is unsuitable for receve-queue distribution. The result is that only 1 cpu core can effectively process the entire pppoe flow, which means the other cores are sitting idle while 1 core is at 100% load. Because the APU2 has very weak single-core CPU processing power, if the above multi-queue receive is deactivated for pppoe, that is a big warning against using this product for 1gbit networks.
But anyway, I am really curious to see the next test results.
As far as I can recall, I could do 600 Mbit/s only from LAN --> WAN direction (e.g. UPLOAD from lan client to internet server), the WAN--> LAN direction (e.g. download from internet server to lan client) was much slower. And all these results were using pure IP between 2 directly connected test PC. When I installed the firewall into my production system, I reconfigured the WAN interface to pppoe, and real world results were lower than the testbench results.
The reason why I am suspecting the pppoe encapsulation is a serious limiting factor, that the internet is full of articles that all says the same thing: the pppoe is unsuitable for receve-queue distribution. The result is that only 1 cpu core can effectively process the entire pppoe flow, which means the other cores are sitting idle while 1 core is at 100% load. Because the APU2 has very weak single-core CPU processing power, if the above multi-queue receive is deactivated for pppoe, that is a big warning against using this product for 1gbit networks.
But anyway, I am really curious to see the next test results.
As far as I can recall, I could do 600 Mbit/s only from LAN --> WAN direction (e.g. UPLOAD from lan client to internet server), the WAN--> LAN direction (e.g. download from internet server to lan client) was much slower. And all these results were using pure IP between 2 directly connected test PC. When I installed the firewall into my production system, I reconfigured the WAN interface to pppoe, and real world results were lower than the testbench results.
140
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: December 18, 2019, 05:10:20 pm »
"Now if your setup requires the APU2 to perform the PPPoE connectivity, that doesn't really impact the transmission speed."
There is a very high chance, that the pppoe session handling and single threaded MPD daemon is the biggest bottleneck on the apu2 to reach the 1 gigabit speed.
There is a very high chance, that the pppoe session handling and single threaded MPD daemon is the biggest bottleneck on the apu2 to reach the 1 gigabit speed.
141
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: December 18, 2019, 03:20:53 pm »
Greatly appreciated your effort. I gave up this topic since a long time, but if you have the energy to go and find the resolution, you have all my support 
!
1 thing I would like to ask you: could you check your results if you emulate PPPoE on the INTERNET interface, instead of plain simple LAN IP protocoll on the WAN interface? As your results will be much much worse under opnsense then what you achieved in this test.
!1 thing I would like to ask you: could you check your results if you emulate PPPoE on the INTERNET interface, instead of plain simple LAN IP protocoll on the WAN interface? As your results will be much much worse under opnsense then what you achieved in this test.
142
19.7 Legacy Series / Re: Unbound custom parameters
« on: August 06, 2019, 02:19:46 pm »
At least please please put some kind of ETA if the "planned to be deprecated" text is already printed on the setup GUI.
143
19.7 Legacy Series / Re: Unbound custom parameters
« on: August 06, 2019, 10:40:44 am »
I have these:
extended-statistics: yes
log-queries:yes
and I dont think there is any other way in Opnsense to use these special options without the "Custom options" input field.
For the record, this was the reason why I opened this thread:
Custom options
This option will be removed in the future due to being insecure by nature. In the mean time only full administrators are allowed to change this setting.
Enter any additional options you would like to add to the Unbound configuration here.
extended-statistics: yes
log-queries:yes
and I dont think there is any other way in Opnsense to use these special options without the "Custom options" input field.
For the record, this was the reason why I opened this thread:
Custom options
This option will be removed in the future due to being insecure by nature. In the mean time only full administrators are allowed to change this setting.
Enter any additional options you would like to add to the Unbound configuration here.
144
19.7 Legacy Series / Re: Smart status now yellow "unknown"
« on: August 06, 2019, 09:31:17 am »
I have exactly the same issue as the rest here: PC-Engines APU2, SATA SSD, showed the SMART status on the dashboard, as green OK or something similar.
Since 19.7, it stays at yellow unknown.
Actually, I am not even sure, the green OK status before can be trusted, as I can imagine it is as similarly misleading, as the gateway Status was on the dashboard: in a not-so-easy-to-spot menu it was set by default as "dont monitor gateway" and the dashboard happily showed green OK status, even if in fact gateway monitoring was plain disabled. Can that be the SMART status is such a red herring, it shows something misleading when in fact the SMART monitoring is simply broken in the background, and does not check anything at all?
Sorry to be such a PITA, its not negative criticism, I am just good at pointing out not-so-easy-to-discover broken things, where others dont find them.
-----------------------------------------------
For reference, here is the SMART all info query output:
smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.2-RELEASE-p11-HBSD amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: SATA SSD
Serial Number: A45E07xxxxxxxxxxxxxxxxxxx
LU WWN Device Id: 0 000000 000000000
Firmware Version: SBFM01.1
User Capacity: 16,013,942,784 bytes [16.0 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: mSATA
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Aug 6 09:24:56 2019 CEST
SMART support is: Available - device has SMART capability.
SMART support is: 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: (65535) seconds.
Offline data collection
capabilities: (0x79) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 30) minutes.
Conveyance self-test routine
recommended polling time: ( 6) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 8177
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 91
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
170 Unknown_Attribute 0x0003 071 071 010 Pre-fail Always - 35
173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 458764
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 52
194 Temperature_Celsius 0x0023 067 067 000 Pre-fail Always - 33 (Min/Max 33/33)
218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 99
241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 78
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 8139 -
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.
Since 19.7, it stays at yellow unknown.
Actually, I am not even sure, the green OK status before can be trusted, as I can imagine it is as similarly misleading, as the gateway Status was on the dashboard: in a not-so-easy-to-spot menu it was set by default as "dont monitor gateway" and the dashboard happily showed green OK status, even if in fact gateway monitoring was plain disabled. Can that be the SMART status is such a red herring, it shows something misleading when in fact the SMART monitoring is simply broken in the background, and does not check anything at all?
Sorry to be such a PITA, its not negative criticism, I am just good at pointing out not-so-easy-to-discover broken things, where others dont find them.
-----------------------------------------------
For reference, here is the SMART all info query output:
smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.2-RELEASE-p11-HBSD amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: SATA SSD
Serial Number: A45E07xxxxxxxxxxxxxxxxxxx
LU WWN Device Id: 0 000000 000000000
Firmware Version: SBFM01.1
User Capacity: 16,013,942,784 bytes [16.0 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: mSATA
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Aug 6 09:24:56 2019 CEST
SMART support is: Available - device has SMART capability.
SMART support is: 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: (65535) seconds.
Offline data collection
capabilities: (0x79) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 30) minutes.
Conveyance self-test routine
recommended polling time: ( 6) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 8177
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 91
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
170 Unknown_Attribute 0x0003 071 071 010 Pre-fail Always - 35
173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 458764
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 52
194 Temperature_Celsius 0x0023 067 067 000 Pre-fail Always - 33 (Min/Max 33/33)
218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 99
241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 78
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 8139 -
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.
145
19.7 Legacy Series / Re: Unbound custom parameters
« on: August 05, 2019, 04:21:49 pm »
That would be a huge steps backwards. Is there any reason why this is the plan?
146
19.7 Legacy Series / Unbound custom parameters
« on: August 05, 2019, 03:33:10 pm »
I found in 19.7 under the Unbound settings that "Custom options" will be deprecated in the future. Can the team share the plans how the not-so-common parameters be still used if "custom options" input box will no longer be available?
147
Hardware and Performance / Re: PCENGINES APU[1-5] Coreboot SeaBIOS Open Firmware
« on: July 17, 2019, 04:18:38 pm »
People (at least 2) started to report extermal PCIe Wifi card issues with 4.9.0.7.
148
Hardware and Performance / Re: Hyperthreading is available in 19.1.x?
« on: July 17, 2019, 04:17:26 pm »
Well, I seem always asking too much...
149
Hardware and Performance / Re: Hyperthreading is available in 19.1.x?
« on: July 13, 2019, 11:41:47 am »
I have read the linked page, but not sure if I understood it fully.
In laymans term,
a) do you think the advertising of CPU feature flag HTT in this specific case is false or correct info?
b) for a 4core CPU should any OS report 4 logical cores or 8?
c) setting sysctl HTT enable/disable should have any effect, or its completely irrelevant, as this CPU is simply a non-HTT architecture?
d) if the OS does not see the SMT parts if this CPU, can the behavior of such CPU be adjusted from OS side, or simply no performance tuning can be set?
In laymans term,
a) do you think the advertising of CPU feature flag HTT in this specific case is false or correct info?
b) for a 4core CPU should any OS report 4 logical cores or 8?
c) setting sysctl HTT enable/disable should have any effect, or its completely irrelevant, as this CPU is simply a non-HTT architecture?
d) if the OS does not see the SMT parts if this CPU, can the behavior of such CPU be adjusted from OS side, or simply no performance tuning can be set?
150
Development and Code Review / Re: APU LEDs Plugin
« on: July 13, 2019, 11:19:41 am »
(Reminder for myself)