I caused some damage.
I caused some damage.
It was around 11 pm last night when I decided to link two ports on my PFsense router for a 2gb uplink to the rest of my home LAN. Driven by curiosity and a sense of "why not," I accessed the web interface only to discover my plan wouldn’t support just three interfaces. The challenge was assigning the LAN port without losing access to the config panel. Then came the clever solution: using a USB Ethernet dongle to keep working while I set up the aggregation. I enabled LACP, but got caught in a snag—my 16-port unmanaged switch wouldn’t handle the protocol. The plan went sideways; I risked losing everything if I switched the new interface later and had to reinstall from backup. Eventually, I found a VGA cable (the one OptiPlex uses for PFSense) but couldn’t locate it. I remembered leaving it at my dad’s office, about 10 miles away. That night, I realized I might have permanently damaged the network. The next day, after work, I managed to fix it—though not without frustration. In short, avoid major tweaks to an already complex setup, especially when you’re still trying to squeeze more bandwidth from a tired router.
Files exchanged across devices on the same network travel through the switch, verifying the destination MAC address against its database. If a match is found, it forwards the data directly to the intended device, skipping the router. Network traffic typically reaches the router only when: A. Data targets another network B. A specific service needs a default gateway. SAMBA manages SMB on Linux, meaning during an SMB transfer, linking the connection between router and switch would genuinely boost bandwidth for client internet access (provided the link exceeds 1Gbit) or connects to another private network.
It's quite accurate. *conceals itself in a corner and whispers in pain*
Unfortunately LACP needs client network interface and switch capabilities. Most modern smart switches offer this, allowing you to use affordable 1G switches with LACP features. Smart switches also provide VLAN tagging and possibly QoS, which can be useful for testing. It's a valuable skill to acquire, but I’d avoid making live changes remotely while learning. We’ve all experienced it—made a mistake, lost SSH access, and had to drive 80 miles just to fix it because of time pressure. I realized my mistake immediately after saving the configuration and losing access to the device, with no one nearby to help. It was a real face-palm moment followed by panic.
I think the best approach would be to connect the LACP interface and the USB port together. This way, even if LACP fails, you can still use the USB connection. Looking back now, you should be able to revert the LACP settings without a full reinstall. You can modify or simply swap out the configuration file located at /conf/config.xml using your backup. I went through something similar when installing a 4-port Ethernet card and setting up a bridge. It’s important to plan carefully to keep connectivity intact while making changes. It’s easy to mess up if you act quickly or if the router interface updates unexpectedly (as seen on OpenWRT). Without the VGA cable, you’re in a good spot unless your motherboard supports a serial port and you have a compatible client.