Nope but I passed thru a USB Zigbee radio just fine to my HAOS VM on one.
I'm sure a USB cell modem should work.
CWWK/Topton/... Nxxx quad NIC router
- Thread starter Becks0815
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I'm sure a USB cell modem should work.
I had a CT w/ docker and wg-easy already but thought it would be better integration in OPNsense w/ plugin and wg interface. In the end I did as you suggested, kept the CT and just configured port forwarding. It took me two days because of changing IP of my docker CT (it didn't identify by MAC) and some misconfiguration on the OPNsense side. However, it is working "perfectly splendid" now. As you say, QR code config is so convenient that even if it is only for my phone it is worth it!
Regarding IPv6 I did as you recommended as well. I am still beginner in networking and it would be a unnecessary complication. I turned it off.
I've also turned off Unbound that was on by default and every logging option I could find. I still have ~130k writes/s which I think is the reason my NVMe drive is running hot. I've ran out of options what to turn off
Even after reboot I see no change. I've allocated all 4 cpu cores to OPNsense. They are mostly idle and spent most of their time in C10. But every so often they wake up and I see some C6 states and 28% cpu usage for a second (had 7% w/ one core allocated before). Since it is not doing much I might lower the CPU count again and see if my power consumption improves somewhat. I am at 12W idle now while I had 9W before the OPNsense was doing anything. I know it is not worth my time but I want to try to improve it anyway.Here is a collections of links that I've used
tteck.github.io
Proxmox VE Tools -> Proxmox VE Post Install
----should help with the writes on the NVME, the main culprit is High Availability in Promox
github.com
Used: Node temperature view
Not used: Nag screen deactivation, because the subscription nag screen is already in the first link
www.derekseaman.com
Tested in Win10 even if the tutorial is for Win11, and it works, the downside.... more heat due to the igpu utilization in Windows and after each Proxmox kernel update if have to recompile. In theory it should work also for Jellyfin
Proxmox VE Helper-Scripts | Scripts for Streamlining Your Homelab with Proxmox VE
Scripts for Streamlining Your Homelab with Proxmox VE
----should help with the writes on the NVME, the main culprit is High Availability in Promox
GitHub - Meliox/PVE-mods: Proxmox modifications
Proxmox modifications. Contribute to Meliox/PVE-mods development by creating an account on GitHub.
github.com
Not used: Nag screen deactivation, because the subscription nag screen is already in the first link
Proxmox VE 8.1: Windows 11 vGPU (VT-d) Passthrough with Intel Alder Lake - Derek Seaman's Tech Blog
Using Proxmox 8.x and want to share your Intel 12th Gen (Alder Lake) GPU with several VMs? Totally refreshed for Proxmox 8.1, check out my new guide for Windows 11 Pro VMs.
www.derekseaman.com
Tested in Win10 even if the tutorial is for Win11, and it works, the downside.... more heat due to the igpu utilization in Windows and after each Proxmox kernel update if have to recompile. In theory it should work also for Jellyfin
I saw disabling ethernets in BIOS, don't remember which n100 variant was used, but some had these options
In the Bios, PCIe settings. Disable one or more lanes and check what is no more working. This can be a NIC or a nvme drive.
I suspected it will end up that way... I presume lanes 1-4 are the main NVMe (seeing that they are bonded in the BIOS of mine), so guess I'll start at the higher ones
The other thing that bother me is SSD temperatures. I got a Crucial P3 and sensors show it goes up to the low 70C...
Memory issues, please help and report ;-) thanks in advance.
I have the 305 V2 from HUNSN and another local got the same motherboard from TopTon. Both of them have issues with the Crucial 48G RAM module CT48G56C46S5. It al looks stable for 9 days and then out of the blue the units crashes during PVE backups from the high speed 4x NVMe to the lower speed 1x NVMe. The crashes are always during the backup window, call it the high load window. There is an original fan on the bottom and a big fan on top, heat could not be a real issue....at least not from chassis perspective, might be specific memory heat?
Did some tests with memtest and this memory fails sometimes, with a fan it fails less and I got green passes. Noticed the crashes it is still failing, so I'm looking for others who experience the same? Any one having the same V2 box (picture below, check USB ports) N305 and also memory errors.
Or no memory errors and the N305 V2 please report too, including your so-dimm model ;-)
Many thanks, its hard to troubleshoot this.
Temps during a "the" backup job which crashed the unit at night, now by day simulated to get it into the crash state.
I have the 305 V2 from HUNSN and another local got the same motherboard from TopTon. Both of them have issues with the Crucial 48G RAM module CT48G56C46S5. It al looks stable for 9 days and then out of the blue the units crashes during PVE backups from the high speed 4x NVMe to the lower speed 1x NVMe. The crashes are always during the backup window, call it the high load window. There is an original fan on the bottom and a big fan on top, heat could not be a real issue....at least not from chassis perspective, might be specific memory heat?
Did some tests with memtest and this memory fails sometimes, with a fan it fails less and I got green passes. Noticed the crashes it is still failing, so I'm looking for others who experience the same? Any one having the same V2 box (picture below, check USB ports) N305 and also memory errors.
Or no memory errors and the N305 V2 please report too, including your so-dimm model ;-)
Many thanks, its hard to troubleshoot this.
Temps during a "the" backup job which crashed the unit at night, now by day simulated to get it into the crash state.
Code:
root@pve:~# sensors
nvme-pci-0600
Adapter: PCI adapter
Composite: +48.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +48.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +56.9°C (low = -273.1°C, high = +65261.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +27.8°C (crit = +119.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +48.0°C (high = +105.0°C, crit = +105.0°C)
Core 0: +37.0°C (high = +105.0°C, crit = +105.0°C)
Core 1: +37.0°C (high = +105.0°C, crit = +105.0°C)
Core 2: +37.0°C (high = +105.0°C, crit = +105.0°C)
Core 3: +37.0°C (high = +105.0°C, crit = +105.0°C)
Core 4: +48.0°C (high = +105.0°C, crit = +105.0°C)
Core 5: +48.0°C (high = +105.0°C, crit = +105.0°C)
Core 6: +48.0°C (high = +105.0°C, crit = +105.0°C)
Core 7: +48.0°C (high = +105.0°C, crit = +105.0°C)
nvme-pci-0100
Adapter: PCI adapter
Composite: +46.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +46.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +62.9°C (low = -273.1°C, high = +65261.8°C)Goodmorning see my last post also RAM issues with the V2 board, only diff is you have a N100 and I have an N305. Could you please share which RAM you swapped for which RAM? Could you also tag me in the future, because I thought it was solved and 9 days later it crashed again. I'm really thinking: is it the board or the memory.
CT48G56C46S5 48G is not compatible with the N305 V2 with 8 USB ports.
CT32G48C40S5 32G is perfectly compatible with the N305 V2 with 8 USB ports.
Proven on a local forum in my home country with 4 different boxes and 4 different 48G memory modules. The new N305 V2 with 8 USB ports (2x 3.x USB and 6x 2.0USB) is not compatible with the 48G module of Crucial.
Yes it boot, and you are able to run proxmox but then out of the blue the box start crashing in the upcoming 10 days. Did some extensive test, and 3 other users, and all of us getting memory errors when running the box for several hours with the 48G SO-DIMM CT48G56C46S5. Memory temps reaching out to 137degrees Celsius...and causing issues.
Quite hard to diagnose, because the box need to reach his maximum temperatures, even with the bottom fan it crashes during the backup window while it is saving the VM's to another disk. For now the strange crashes I had with the 48G module are gone with the 32G module. Let's monitor for the upcoming days.
CT32G48C40S5 32G is perfectly compatible with the N305 V2 with 8 USB ports.
Proven on a local forum in my home country with 4 different boxes and 4 different 48G memory modules. The new N305 V2 with 8 USB ports (2x 3.x USB and 6x 2.0USB) is not compatible with the 48G module of Crucial.
Yes it boot, and you are able to run proxmox but then out of the blue the box start crashing in the upcoming 10 days. Did some extensive test, and 3 other users, and all of us getting memory errors when running the box for several hours with the 48G SO-DIMM CT48G56C46S5. Memory temps reaching out to 137degrees Celsius...and causing issues.
Quite hard to diagnose, because the box need to reach his maximum temperatures, even with the bottom fan it crashes during the backup window while it is saving the VM's to another disk. For now the strange crashes I had with the 48G module are gone with the 32G module. Let's monitor for the upcoming days.
Last edited:
Is it safe right now to buy one of these N100 CWWK boxes with the 4x NVMe support if we do truly want to use all 4 NVMe ports? I want to build a hybrid NAS/virt box using one. Some of the earlier posts aren't super promising about the NVMe actually working correctly.
Hmm.
I am *extremely* new to the Prox Eco (for what that's worth), but if you could give me a rough set of steps-to-recreate, I would be willing (I have the time).
I have not seen temps >~42C, but I have a Noctua 12x12 sitting on top.
----CWWK-C; n305; AL-4L-V2; 3TB/48GiB (Crucial CT48G56C46S5.M16B1)
I have the n305 and running out with 5 nvmes works fine for me.
The RAM that failed was SK hynix 16gb DDR5. I'm not sure which model number but in my original post you can see the barcode and maybe match it to something.
The RAM that works is Patriot 16GB DDR5 PSD516G480081S.
The only concern I read about is the for the NVMe slots 2,3,4 are not working with ASPM power saving. Thats because they re-use a WiFi PCIe slot which somehow works different.
It's quite easy, make a bootable USB stick with the memory test below. This memory test is way better than the embedded one from Proxmox (the blue screen). With all the multicore load this memory test below gives, its easier to detect problems.
Did you experience any strange shutdowns? Without the real life outages, I would have never noticed this memory issues with this module. Its that the box switches off during the backup window of proxmox where it is zipping and copying files between both NVMe's
closed source memtest86
Last edited:
I've run the official memtest before. Not used the Prox one
No strange shutdowns. Just getting Prox running without pulling my remaining hair out has been the challenge (hardware takes it fine, but I just don't "get" it, yet (let-alone getting things to a point where I can do backups)).
I just have the h-board with two nvme's
Yes, that's the one.
I'm not getting this, where is the H located? Dit you run the tests for 4 passes, until you noticed the green passmark/finshed sign?
It's just an h-shaped break-out board (came with the unit) that moves the A+E slot over, and enables another 2280 nvme m.2 (@PCIe3-x1), leaving the main nvme m.2 (@PCIe3-x4) un-blocked.). My example, here (did subsequently switch from the Inland's to the SkH P31s):
It seems that I am (unfortunately) highly allergic to Proxmox, so I can only expose myself to it for short periods of time before I go batsh* crazy . . . I am seeking other pathways (sp. libvirt, et al.).