This is how some of the cheaper home routers are able to provide multiple physical ports while still using single controller (eth0) By default, you will see two VLAN IDs – 1 and 2 pre-configured for LAN and WAN ports respectively.Now, head over to Network > Switch menu to configure VLAN.Make sure you press “Save & Apply” after making the changes. Delete the WAN and WAN6 interfaces such that you are only left with the LAN interface.Head over to Network > Interfaces, you will see one or more “WAN” interfaces like shown below, Log onto OpenWrt dashboard, preferably by connecting your work computer to the router through a cable.Removing WAN interfaces here because once ready, your WiFi router will no longer act as a “router” but just as a Wireless Access Point and WAN/internet interface configuration would be handled from within pfSense. A patch cable to connect computer to the wireless routerĪssuming you have OpenWrt flashed on your WiFi router, the first thing that you would do is remove WAN interfaces from the router and setup VLAN tags for the LAN and WAN ports.A VLAN capable WiFi router with OpenWrt support (check OpenWrt Table of Hardware to figure this out for your model), I am using TP-Link Archer C20.A computer with x86 CPU and a network port, I am using Asus X555YA that has AMD A6-7310 APU.
Some of this will become more obvious as you follow through my steps. Here is schematic of the setup, Using wireless router as managed switch for pfSense And I will mark the WAN port W1 on my WiFi router as another access port with a different VLAN tag ID.
I will mark the other L2 and 元 LAN ports as access port under single VLAN tag ID. The general idea here is simple, I will connect my laptop to my WiFi router through LAN port L1. If your home WiFi router has more than one port, it most likely supports VLAN capability and can be used as a managed switch WiFi routers typically have one WAN/”internet” port and 4 LAN ports – is there a way I could utilize my cheap WiFi Router as managed switch ? Turns out I can! Now I did not have a managed switch lying around, but I had a WiFi router. One popular, and obvious, solution for single NIC pfSense box design involves using an external switch to “expand” number of available ethernet ports. One may argue that I could use laptop’s wireless card for WiFi access – but anyone who has tried running hostapd on FreeBSD knows that you could barely go beyond a few Mbps of speed.
That meant that I could only connect my “internet”/WAN cable coming from my ISP, I had no second port to connect my WiFi router for wireless access. I had an old laptop that I could use to install pfSense on, but as is case with any laptop – the laptop only had single network interface. I really wanted to try out pfSense while I had lots of ARM based single-board computers such as Raspberry Pi, Rock Pi E lying around – I did not have a spare x86 machine to host pfSense on – as pfSense does not support ARM CPU (yet).
0 kommentar(er)
