{"id":2273,"date":"2021-07-04T12:23:51","date_gmt":"2021-07-04T16:23:51","guid":{"rendered":"http:\/\/matthannan.net\/blog\/?p=2273"},"modified":"2021-07-04T15:30:20","modified_gmt":"2021-07-04T19:30:20","slug":"tp-link-is-no-cisco-vlan-configuration","status":"publish","type":"post","link":"https:\/\/matthannan.net\/blog\/tp-link-is-no-cisco-vlan-configuration\/","title":{"rendered":"TP-Link is no Cisco: VLAN configuration"},"content":{"rendered":"\n
\"\"<\/a><\/figure><\/div>\n\n\n\n

On the surface, my TP-Link T2600G-28TS<\/a> v3 managed switch appears to have everything that I would expect to have for some intermediate networking in the home. Most of my complaints with the device, to date, have been minor, such as the idle time-out having a max of 120 seconds. So annoying. But, for the most part, it has been quietly doing its job, almost without issue, for a couple of years now. <\/p>\n\n\n\n

I recently replaced my Verizon G1100 FiOS router<\/a> with a pfSense<\/a> router built out of an old PC. The specs are wonderful for a router on a 300Mbps ISP link, but it is so old that the CPU does not support AES-NI<\/a>. Not a big deal, as I am not planning on building any VPNs any time soon. I was going to use OPNsense<\/a> for this router, but there are far more resources available on how to configure pfSense, including this awesome video by Tom Lawrence:<\/p>\n\n\n\n

\n