#protectli — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #protectli, aggregated by home.social.
-
Awesome news for #opensource #networking professionals and fans:
#Protectli now offers Vaults with #OpenWrt pre‑installed!
This is exactly why open‑source firmware matters. Long‑term updates, transparent security fixes, no forced obsolescence, and full control over your device.
Proprietary routers age out fast.
OpenWrt‑based devices stay useful for years.
https://protectli.com/news/openwrt-preinstalled-on-protectli-vaults/
-
The sweet beeps of success #opnsense #protectli #coreboot #firewall
-
Nutzt hier jemand die VP4630 von Protectli?
Wenn ja dort steht in der Spec DDR4 Ram 2666 Mhz - laufen da eigentlich auch DDR4 Ram mit 2133 Mhz oder sollte man die nicht einbauen? -
Watching jakkuh my dream home datacenter YouTube video…
So many really nice things he is talking about…. But how am I buying TWO Unifi Enterprise Fortress Gateways… $2k each.
My router is #OPNsense on a used #Protectli FW4B.. 150 EUR
-
@bacardi55 I use #Protectli with #OPNsense but for home and <1GB ISP connections, consider the cheap Velocloud, <USD $40
-
I recently got #fidium fiber internet at home. The initial install was done with their modem (fiber terminator?) and one of their “pods” (router + WiFi access point). Anyways, I had immediately switched to my #unifi #edgerouter4 by spoofing the MAC address of their router and it worked great. Then I finally got my refurbished #protectli in the mail with all 2.5gbps Ethernet ports and set it up with #opnsense. Unfortunately, MAC address spoofing didn’t work. It took 1 hour on the phone to fix 😵
-
I recently got #fidium fiber internet at home. The initial install was done with their modem (fiber terminator?) and one of their “pods” (router + WiFi access point). Anyways, I had immediately switched to my #unifi #edgerouter4 by spoofing the MAC address of their router and it worked great. Then I finally got my refurbished #protectli in the mail with all 2.5gbps Ethernet ports and set it up with #opnsense. Unfortunately, MAC address spoofing didn’t work. It took 1 hour on the phone to fix 😵
-
I recently got #fidium fiber internet at home. The initial install was done with their modem (fiber terminator?) and one of their “pods” (router + WiFi access point). Anyways, I had immediately switched to my #unifi #edgerouter4 by spoofing the MAC address of their router and it worked great. Then I finally got my refurbished #protectli in the mail with all 2.5gbps Ethernet ports and set it up with #opnsense. Unfortunately, MAC address spoofing didn’t work. It took 1 hour on the phone to fix 😵
-
This morning I finally replaced the home router. The new one is a Protectli V1211. I imported my OPNsense configuration, then updated to the latest release. If you're reading this post, it's working.
The whole thing was remarkably painless. The only tricky part was that I had to reassign all the interfaces and VLANs to match the new box's hardware.
The old router is on hot standby until the new one has soaked for a few days.
-
@gadgetboy nice hardware ! I use #Protectli hardware to get #Coreboot + TPM out of the box. A bit pricier but worth it IMO. Check this guy's #OPNsense playlists to get started (including Wifi): https://www.youtube.com/@homenetworkguy/playlists
-
Hey fedi #HomeLab peeps, what do you all make of #Protectli appliances. Looking to add a hardware #firewall running #OpenSense, but they have so many configurations. Budget ~$250 at some points would be running non-stop as home office production firewall.
-
Hey fedi #HomeLab peeps, what do you all make of #Protectli appliances. Looking to add a hardware #firewall running #OpenSense, but they have so many configurations. Budget ~$250 at some points would be running non-stop as home office production firewall.
-
Hey fedi #HomeLab peeps, what do you all make of #Protectli appliances. Looking to add a hardware #firewall running #OpenSense, but they have so many configurations. Budget ~$250 at some points would be running non-stop as home office production firewall.
-
New House Projects – Network 2.0
Ok - So, take one of this project didn't go as planned. I don't regret the choices I made, and while I'm very happy with how everything is working today. it's not the setup I had hoped for. So, where did I end up?
Firstly - I ended up ordering a firewall from Protectli, the VP2420, which I ordered with Coreboot BIOS. Performance has been great, it was easy to setup, and the
https://topslakr.com/2025/01/new-house-projects-network-2-0/
-
Ha! Been struggling getting my #live #antenna #TV working right with #Jellyfin tonight so we could watch a live #countdown for #NYE tonight. Unfortunately Jellyfin doesn't have access to a GPU for #transcoding (#VM in a CPU-only #server). Using a dual-core #Protectli device for the antenna ingestion. Neither machine doing well transcoding. Finally figured it out by having #TVHeadend copy the video codec from the antenna and transcoding the audio to #AAC locally. Load is about 20% each, now. :D
-
My #Protectli internet #router died after 8 years of service. #RIP.
It took 3 days for a new unit to arrive. After much struggle, I have recovered my old settings and my #network (including this #Mastodon server) is back.
-
If anyone out there is having issues on a #homelab #Proxmox machines with #Intel NIC's... In my case on a couple of #Lenovo M710q's with #I219-V, an Intel NUC10i3FNB with the same, and a #Protectli VP2420 with 4 * #I225-V. The solution for me so far (and I've not seen any performance impact though I've not _really_ looked hard so don't trust this for production) is popping the below after your 'iface eth0 inet manual' line. In my case of course I'm hanging everything else off a bridge onto that interface (vlans and what have you), or passing the PCI-E device to a VM, so adapt as you need. This came from a site somewhere but I cannot find the source any more.
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for ${IFACE}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for ${IFACE}"
-
If anyone out there is having issues on a #homelab #Proxmox machines with #Intel NIC's... In my case on a couple of #Lenovo M710q's with #I219-V, an Intel NUC10i3FNB with the same, and a #Protectli VP2420 with 4 * #I225-V. The solution for me so far (and I've not seen any performance impact though I've not _really_ looked hard so don't trust this for production) is popping the below after your 'iface eth0 inet manual' line. In my case of course I'm hanging everything else off a bridge onto that interface (vlans and what have you), or passing the PCI-E device to a VM, so adapt as you need. This came from a site somewhere but I cannot find the source any more.
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for ${IFACE}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for ${IFACE}"
-
If anyone out there is having issues on a #homelab #Proxmox machines with #Intel NIC's... In my case on a couple of #Lenovo M710q's with #I219-V, an Intel NUC10i3FNB with the same, and a #Protectli VP2420 with 4 * #I225-V. The solution for me so far (and I've not seen any performance impact though I've not _really_ looked hard so don't trust this for production) is popping the below after your 'iface eth0 inet manual' line. In my case of course I'm hanging everything else off a bridge onto that interface (vlans and what have you), or passing the PCI-E device to a VM, so adapt as you need. This came from a site somewhere but I cannot find the source any more.
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for ${IFACE}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for ${IFACE}"
-
If anyone out there is having issues on a #homelab #Proxmox machines with #Intel NIC's... In my case on a couple of #Lenovo M710q's with #I219-V, an Intel NUC10i3FNB with the same, and a #Protectli VP2420 with 4 * #I225-V. The solution for me so far (and I've not seen any performance impact though I've not _really_ looked hard so don't trust this for production) is popping the below after your 'iface eth0 inet manual' line. In my case of course I'm hanging everything else off a bridge onto that interface (vlans and what have you), or passing the PCI-E device to a VM, so adapt as you need. This came from a site somewhere but I cannot find the source any more.
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for ${IFACE}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for ${IFACE}"
-
If anyone out there is having issues on my #homelab #Proxmox machines with #Intel NIC's... In my case on a couple of #Lenovo M710q's with #I219-V, an Intel NUC10i3FNB with the same, and a #Protectli VP2420 with 4 * #I225-V. The solution for me so far (and I've not seen any performance impact though I've not _really_ looked hard so don't trust this for production) is popping the below after your 'iface eth0 inet manual' line. In my case of course I'm hanging everything else off a bridge onto that interface (vlans and what have you), or passing the PCI-E device to a VM, so adapt as you need. This came from a site somewhere but I cannot find the source any more.
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for ${IFACE}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for ${IFACE}"
-
HardenedBSD and Protectli Partner to Build a Censorship-Resistant Mesh Network #Hardenedbsd #Protectli #Firewall #Unix
https://ostechnix.com/hardenedbsd-and-protectli-partner-to-build-a-censorship-resistant-mesh-network/ -
#Firewall wird auf ein #Protectli #Barebone betrieben.
-
#Firewall wird auf ein #Protectli #Barebone betrieben.
-
-
@torarg What kinds of speeds are you getting through Protectli and which device do you have?
-
Updated #OPNsense from 23.7.12 -> 23.7.12_5 -> 24.1_1 -> 24.1.1
- took 20 minutes on #Protectli FW4B
- 1 automatic reboot
- 1 manual reboot to get internet connectivity back🏷️ #HomeLab
-
Damn, the #Protectli FW4B also only supports 204 pin RAM modules. I only have 260 pin modules left... :(
-
@estevez its a #Protectli FW4B.
- Intel(R) Celeron(R) CPU J3160 @ 1.60GHz (4 cores, 4 threads)
- 4 GB memory
- 32 GB ssd -
@johnbollwitt Been running #OPNsense for a couple of years.
Not in any demanding way (Telus 250M fibre, home network, mix of wired & Ubiquiti U6 Lite access points, about 30 devices) but it's held up well and never been the cause of problems until the hardware died.
Originally QOTOM hardware, now #Protectli -
Owners of #tplink TL-SG105-M2 (5-port 2.5Gb unmanaged switch), be aware that if you attempt to connect (in my case over CAT5e) distances beyond ~15m, you will find that the energy sent down the cable could be enough to temporarily or perhaps permanenetly damage the device at the other end. I am of course only talking about my one here, YMMV. I do not currently have access to the right kit to measure this, but my TP-Link switch was causing my WRT3200ACM ( #OpenWRT v21 ) at the other end of a 20m cable, and when replaced with a 15m, to reset its CPU at random intervals between 15 mins and 6 hours. I thought the WRT was playing up, and was planning to replace this with something 2.5G capable anyway, so moved the project forwards and put a #Protectli Vault Pro VP2420 in replacing the WRT. Roughly 3 hours into this being in production, the network on that port dropped again. Only this time, it didn't come back. The PCI-E device had disapeared from the bus, reboot didn't bring it back. Bit of a show-stopper. Fortunately a complete power-down and cool-off meant the next time it booted the PCI-E device was back (hopefully some kind of poly fuse saved me). Finally realising the switch was the only other thing the same on that cable, I swapped back in a 1Gb Netgear unit. Everything hummed along fine for a few days. I put the 2.5G switch back in, same problem within an hour. Everything on short cables to the 2.5G switch was fine (and running at 2.5G - a QNAP NAS, a WAX206 on #OpenWRT v23, my desktop).
Anyway, this switch is getting a big label on it warning of the danger! Too late to send it back, and I'm not going to ebay it to some poor person who might have the same issue.
I've now put a replacement 2.5G QNAP QSW-2104-2S in its place. Thats been solid for a week.
I don't know if anyone will ever see this for it to be helpful, but I needed to put something on paper.-Edit for spelling and some grammar!
-
Waiting on another #protectli box, the new 2.5g one with wifi. Well, not waiting. They have super fast shipping.
Also ordered some USB fans, but the current boxes are running cool (max 41c) so it is more peace of mind for next summer.
The new patch cables have started arriving. Yay shorter cables.
-
Updated #OPNsense to 23.1.11 in 3 minutes. Needed a reboot.
Works fine so far.
-
Successfully moved all my hardware including this #mastodon instance #proxmox host to our new home.
Updated some IPv6 stuff and… it’s finally running.This instance is now reachable via 1 Gbps down and 500 Mbps up. (Ofcourse other way round from clients perspective).
Also good to see the #Protectli #FW4B running #OPNsense with suricata and some rules can saturate this line.
-
My #protectli #fw4c is #coreboot enabled now. I've used an #ubuntu #liveusb and flashed their image following the instructions at https://github.com/protectli-root/protectli-firmware-updater. The boot from my usb flashdrive took longer than the flashing. It automatically found the proper image to flash. Protectli gear is good gear.
-
@deeds nice pricing, I will just move my existing setup over and see later what to improve. So that is
- #Protectli #FW4B running #OPNsense
- Unifi PoE Switch
- Unifi AP AC Pro for wifiAll connected with 1 gig for now.
I‘m going to wire up all the rooms with Ethernet in the next weeks.
-
I was considering installing #opnsense on a software raid in my #protectli #vault #fw4c. After reading I learned that the #protectli #vault (at least #fw4b and fw4c models) got two #msata ports where one of them is solely for a #wifi module.
-
@dmnelson that sounds like fun 🤩
I always wanted to try something like this with my parents in law, because I already setup a Pi for other stuff at their end years ago. Maybe I should give it a try.Also nice you are running #pfsense. I‘m using this also but in a #protectli #FW4B.