spl147
-
Posts
485 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by spl147
-
-
Set min fan speed to 10 instead of 1.5
-
7 hours ago, whc said:
How do one go about and do that?
Google my friend, google
-
15 hours ago, Gee1 said:
can u create more FAN profiles? EG instead FAN1234 do FAN1 FAN2 FAN3 FAN4
Nope
-
SM H11SSL here.. FAN Controll dosnt work. Temperature and RPMs are shown correct. CPU FAN is on FANA but spinns allways at max. Dont know what the user / password for my BMC is
UPDATE: ok figured out it only works with PWM Fans. § Pin FANs dosnt work
Oh my…. -
Nice find sir, how to implement it to the IPMI plugin?
First step would be to try them from the command line to see if they actually work! -
23 hours ago, whc said:
Is i possible to get this plugin working to control fans according to HDD temperature on GIGABYTE MJ11-EC1-OT, running BMC and not IPMI. I can see all statistics, including HDD temp, but in the setting of this plugins I can not control the fans at all, only monitor RPM and HDD temps.
a little googling forund this:
For fan settings we have below information:
Below IPMI command format for fan control.
Set Fan Control 0x3c 0x16
Byte1: 0x02
Byte2: FAN_NO
Byte3: Duty1
Byte4: Duty2
Byte5: Duty3
Byte6: Temp1
Byte7: Temp2
Byte8: Temp3
Get Fan Control 0x3c 0x16
Byte1: 0x03
Byte2: FAN_NO
Ex. Get fan 1 status $ Ipmitool -I lanplus -H 192.168.50.43 -U admin -P admin raw 0x3c 0x16 0x03 0x01
– 01 0a 32 64 14 50 5f
Ex. Set fan 1 $ipmitool -I lanplus -H 192.168,50.43 -U admin -P admin raw 0x3c 0x16 0x02 0x01 0x14 0x32 0x64 0x14 0x50 0x5f
- 01 14 32 64 14 50 5f
-
You have the wrong fan selected
-
5 hours ago, J05u said:
So I left without temp monitoring, not perfect.
Should of made sure the board you were gonna use was supported first!
-
2 hours ago, Sptz87 said:
I have an issue with auto fan. It looks like upon boot it's not detecting anything. I've set the fans I want to control to 100% in the bios PWM. When I run a "Detect" it detects it correctly, I set my values. If I reboot it shows 0% yet its running at 100%
If I go back to Auto Fan and try to change any value and save this happens and it also goes missing from System Temp plugin.
Any idea what's up? This is using the IT87 driver on a gigabyte board
whats the output of sensors detect?
-
On 2/20/2024 at 9:03 PM, J05u said:
I am lost trying to get CPU temp to run on Gigabyte 550i Aorus pro, CPU Ryzen 5600G
So far I have K10 and it87 drivers running
This is my sensors detect
# sensors-detect version 3.6.0 # System: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX [Default string] # Kernel: 6.1.64-Unraid x86_64 # Processor: AMD Ryzen 5 5600G with Radeon Graphics (25/80/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): yes Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found unknown chip with ID 0x8688 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): yes Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): yes Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 1 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 2 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 1 (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.This is what I have from sensors. Really just CPU is missing, or CPU is single k10 temp sensor?
Can you help me please to fix this issue?
did you actually read the output? the answers you seek are in the output!
Trying family `ITE'... Yes
Found unknown chip with ID 0x8688
Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.
-
10 minutes ago, Kilrah said:
That's just system info, it's not because it knows it's there that it can use it.
ok, thanks
-
But the container still sees All the servers memory:
-
is --memory=1G not correct to limit memory usage by a docker?
im getting this error:
--memory=1G 'oznu/homebridge'
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
-
1 hour ago, Manni01 said:
Thanks for your work, sounds great but how do we download/install your forked version? When I follow your link on GitHub, the readme says not to download the Zip, but the links to the s3sleep plugin (like all the others) returns a 404 error.
https://raw.githubusercontent.com/chriss158/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg
-
1
-
-
1 hour ago, The Transplant said:
I got the hard drive temp into the green. I am going to try tweaking it a little to see if I can get fan noise down a bit. It is sitting in the back of my office.
I don't know actually what the operating temps of my drives are - have to open up the box and check the model numbers - will do that but for now just going with an average range.
One question - I have 6 mechanical drives and 2 SSD. If I reduced the number of mechanical drives by using less bigger drives would that have much impact on heat? Thanks.
2024-02-04 19:28:18 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 19:31:19 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-04 19:58:27 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 20:01:28 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-04 20:16:32 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 20:19:33 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-04 20:40:40 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 20:43:41 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-04 22:44:17 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 22:47:18 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-04 23:26:29 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-04 23:29:30 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 00:17:43 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 00:20:44 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 00:32:48 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 00:35:49 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 00:50:53 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 00:53:54 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 01:05:57 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 01:08:58 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 01:21:02 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 01:24:02 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 01:48:09 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 01:51:10 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 01:54:11 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 01:57:12 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 02:06:15 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 02:09:15 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 02:27:21 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 02:30:22 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 02:33:22 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 02:36:23 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 02:45:26 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 02:48:27 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:00:30 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:03:31 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:12:34 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:15:34 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:18:35 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:21:36 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:24:37 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:30:39 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:36:41 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:42:43 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:51:46 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 03:54:47 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 03:57:48 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:03:50 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 04:09:52 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:12:53 Fan:Temp, FAN123456(50%):HDD Temp(47C) 2024-02-05 04:15:54 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:24:57 Fan:Temp, FAN123456(50%):HDD Temp(47C) 2024-02-05 04:30:59 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:37:01 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 04:40:01 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:43:02 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 04:49:04 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:52:05 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 04:55:06 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 04:58:07 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:01:08 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:07:10 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:13:11 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:16:12 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:19:13 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:22:14 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:25:15 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:28:15 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:31:16 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:37:19 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:43:20 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:46:21 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:49:22 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 05:55:24 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 05:58:25 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 06:04:27 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 06:10:28 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 06:13:29 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 06:19:31 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 06:25:33 Fan:Temp, FAN123456(50%):HDD Temp(47C) 2024-02-05 06:37:36 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 06:40:37 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 06:46:39 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 06:49:40 Fan:Temp, FAN123456(50%):HDD Temp(45C) 2024-02-05 06:58:42 Fan:Temp, FAN123456(47%):HDD Temp(44C) 2024-02-05 07:01:43 Fan:Temp, FAN123456(50%):HDD Temp(45C)model numbers are in the UI:
-
Edit: Solved by resetting the BMC and then restarting fan control
I am also having problems with all my fans running at full speed after upgrading the BIOS and BMC firmware of my Supermicro board today. I already tried stoping and starting fan control, adjusted the minimum fan speed and also did a system reboot. Fan thresholds have been adjusted to match the low rpm of my Noctua fans.
This is the fan log:
2024-02-03 18:37:39 Starting Fan Control2024-02-03 18:37:39 Board: Supermicro Board Model: X11SCH-LN4F2024-02-03 18:37:39 SM Board selection: 112024-02-03 18:37:39 Setting fans to full speed2024-02-03 18:37:49 Fan:Temp, FAN1234(33%):CPU Temp(30C), FANA(28%):HDD Temp(Spundown)2024-02-03 18:41:50 fan control config file updated, reloading settings2024-02-03 18:41:50 Fan:Temp, FAN1234(41%):CPU Temp(29C), FANA(31%):HDD Temp(31C)2024-02-03 18:41:51 Stopping Fan Control2024-02-03 18:41:51 Setting fans to auto2024-02-03 18:41:56 Starting Fan Control2024-02-03 18:41:56 Board: Supermicro Board Model: X11SCH-LN4F2024-02-03 18:41:56 SM Board selection: 112024-02-03 18:41:56 Setting fans to full speed2024-02-03 18:42:06 Fan:Temp, FAN1234(41%):CPU Temp(28C), FANA(31%):HDD Temp(31C)
And these are my settings:
http://upload.forums.unraid.net/live/monthly_2024_02/345731802_Bildschirmfoto2024-02-03um18_49_55.thumb.png.e5989b6ca4cfadf2eadc12a9b4687086.png
http://upload.forums.unraid.net/live/monthly_2024_02/355274572_Bildschirmfoto2024-02-03um18_46_59.thumb.png.1a112952a198e54ab551c0de80da47d0.png
Cpu fan should not be controlled by this plugin, and your hdd fan shows 0, i think your config is wrong, check your physical fan header labels -
59 minutes ago, The Transplant said:
Here you go:
80c for high? are you crazy? look up the specs for your drives. most are 55-60c MAX!
i use 30c for low and 55c for high
then once your drives come back down to normal temps, play with max fan speed to keep drives around 40-42c
-
1
-
-
I think I am getting the hang of this. I did make some adjustments and I do see the HHD temp going up slightly but the fans are running slower.
I guess the question is what is acceptable in terms of temps for the drives? Thanks.
2024-01-31 14:57:31 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 15:03:32 Fan:Temp, FAN123456(27%):HDD Temp(50C)
2024-01-31 15:24:38 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 15:30:40 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 16:00:49 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 16:06:51 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 16:27:57 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 16:33:59 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 17:04:07 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 17:10:09 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 17:40:18 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 17:46:20 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 18:13:27 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 18:16:28 Fan:Temp, FAN123456(27%):HDD Temp(51C)
2024-01-31 19:01:42 Fan:Temp, FAN123456(28%):HDD Temp(52C)
2024-01-31 19:07:44 Fan:Temp, FAN123456(27%):HDD Temp(50C)
2024-01-31 20:32:49 fan control config file updated, reloading settings
2024-02-01 00:00:52 Fan:Temp, FAN123456(29%):HDD Temp(54C)
2024-02-01 00:03:52 Fan:Temp, FAN123456(27%):HDD Temp(52C)
2024-02-01 10:28:45 fan control config file updated, reloading settings
2024-02-01 10:28:45 Fan:Temp, FAN123456(10%):HDD Temp(51C)
2024-02-01 10:37:48 Fan:Temp, FAN123456(17%):HDD Temp(56C)
2024-02-01 10:46:50 Fan:Temp, FAN123456(14%):HDD Temp(54C)
2024-02-01 10:49:51 Fan:Temp, FAN123456(17%):HDD Temp(56C)
2024-02-01 10:53:12 fan control config file updated, reloading settings
2024-02-01 11:04:56 fan control config file updated, reloading settings
2024-02-01 11:04:56 Fan:Temp, FAN123456(14%):HDD Temp(54C)
2024-02-01 11:08:57 Fan:Temp, FAN123456(17%):HDD Temp(56C)
2024-02-01 11:18:00 Fan:Temp, FAN123456(14%):HDD Temp(54C)
2024-02-01 11:21:00 Fan:Temp, FAN123456(17%):HDD Temp(56C)
http://upload.forums.unraid.net/live/monthly_2024_02/image.thumb.png.0d4ead56d580d0fddb673f778ff2b99a.png
54c is really high! Post a pic of the fan setting page -
21 hours ago, Arubial said:
I just discovered this plug-in this morning after migrating to a Supermicro X10DRU-i+ a couple months ago.
I think I have everything configured properly, but only 2 of the fans are spinning down. I have 4 fans total, the stock ones from SuperMicro. My sensors report the last two fans are on FAN7 and FAN8, which is what I selected, but I cannot get them to spin down at all.
Thats just for display in the footer
Supermicro boards i believe only use the 1st 4 headers
20c is way to low for the low threshold. your hdds will never get that cold, so fans will always be spinning closer to max i would use 30-35c
-
11 hours ago, The Transplant said:
I set my fan minimum % to 1.3 and yet the lowest I ever see the fans go is 5250. Since I am not sure what the ratio between temp and fan speed is, I am curious if this is the lowest they will go? Thanks.
what are your fan settings set to?
post the impifan log (link is at the bottom of the fan control page)
-
2 minutes ago, The Transplant said:
Thanks, I tried that but the fans are still spinning at 17760 RPM. Is there something else I should be doing? Thanks
you have not configured the fans at all!
here is mine:
-
4 hours ago, diste66 said:
Is there a handy guide somebody could link on how to use the Fan Auto Control plugin?
I've been playing around with it but I haven't been able to really figure out the relationship between the different variables.
For context I have an all nvme nas, the fan is loud as hell, hence why I'm looking into the plugin. Playing with the plugin I was able to turn off the fan completely which is actually fine for the most part the thing does not overheat, but I'd want it to turn on if things did get hot.
And frankly the fan RPM that result from me going up or down in the temp thresholds or pwm values seem pretty random to me. Any help would be appreciated
it's quite simple really:
Min PWM Value = the slowest you want to spin the fans when at or below LOW Temp Threshold ( play with this to find your prefered cooling/noise ratio)
LOW Temp Threshold = temp in witch the fans will spin down to Min PWM Value (temps the nVME drives idle at)
HIGH Temp Threshold = temp in witch the fans will spin up to 100% (max operating temp)
Refresh Interval = time in mins. to check drive temps (1 Min.)
fan speed changes are auto calculated based on min PWM value and LOW and HIGH thresholds
just a FYI nVME drives have much different max temp the HDD's, google you nvme to see
-
i just installed the OpenVPN-AIO-Client on 6.12.6 and got this in the log:
and the container does not start
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [15:53:23.766594] STUBBY: Stubby version: Stubby 0.3.0 [15:53:23.769075] STUBBY: Read config from file /config/stubby/stubby.yml /nftables.rules:11:38-42: Error: syntax error, unexpected sport add rule ip filter INPUT tcp4-client sport counter accept ^^^^^ /nftables.rules:18:39-43: Error: syntax error, unexpected dport add rule ip filter OUTPUT tcp4-client dport counter accept ^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT tcp sport 853 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT tcp dport 853 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT tcp sport 53 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT tcp dport 53 counter accept ^^^^^^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter INPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter OUTPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter INPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter OUTPUT handle ^ Error: Could not process rule: No such file or directory add rule ip filter INPUT ip saddr 127.2.2.2 tcp sport 53 ct state established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT ip daddr 127.2.2.2 tcp dport 53 ct state new,established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT ip saddr 127.2.2.2 udp sport 53 ct state established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT ip daddr 127.2.2.2 udp dport 53 ct state new,established counter accept ^^^^^^ [info] Creation complete [info] stubby fixed. [info] danted fixed. [info] tinyproxy fixed. [info] torsocks fixed. [info] privoxy fixed. [info] Initialisation complete [info] Run stubby in background on port 53 [warn] Your ISP public IP is 99.35.193.151 [info] Setting up nftables rules... [info] Flusing ruleset [info] Added route 10.172.69.0/24 via 172.17.0.1 dev eth0 [info] Apply rules [info] Quick block test. Expected result is time out. Actual result is 99.35.193.151 [info] All rules created [info] Setting up OpenVPN tunnel... [info] Create tunnel device [info] Allow DnS for openvpn to lookup VPN server [info] Connecting to VPN on port with proto tcp4-client... [info] Your VPN public IP is 99.35.193.151 [info] Block DnS to force traffic through tunnel [info] Change DNS servers to 127.2.2.2 [info] Adding 127.2.2.2 to /etc/resolv.conf [info] Allowing DNS lookups (tcp, udp port 53) to server '127.2.2.2' [info] Tunnel created [info] Enabling healthcheck... [info] Healthcheck enabled [info] Runing apps... ** Press ANY KEY to close this window ** -
Sure I can look at adding option for the modprobe, is it specific to Dell Models as I dont want to load if not required.
Im pretty sure all, but i can not test. Maybe just have a button to load/unload
Dynamix - V6 Plugins
in Plugin Support
Posted
I agree documentation is horrendous. Yes install system temp, click detect then save then load if not already loaded, the in autofan click detect