If further configuration is needed, what is the recommended methodology? I have seen mention of NAT and firewall rules.Should bridging allow LAN and Wi-Fi to talk to each other without further configuration?.I have stumbled across several posts on the pfSense forum, and various SE's, asking for help getting bridging to work, and there are several questions here, all/most of which have answers with "Yeah, I got it working" but as a pfSense and BSD n00b, I am having a hard time making heads or tails out of their answers or instructions. My intent was a down and dirty, quick test to get things up and running. If I am successful with this test, I will eventually purpose build a machine to different specs and re-architect things. The Wi-Fi is simply for me to manage the single machine on the LAN, not some major thoroughfare of traffic. I would like for them to talk to each other too. LAN and Wi-Fi can grab DHCP addresses from pfSense, and go out the VPN. I also set up the WAN to route to a commercial OpenVPN provider. The built in Ethernet port is the WAN (re0), I installed a USB Ethernet adapter (ue0), and bridged ue0 and the Wi-Fi (ath0). I discovered pfSense a week or so ago and set up a laptop with 2.2.6 to test it out on. I found more chatter about pfSense here than on the Network Engineering SE, so I figured this would be a good place to ask for help. However, I was not able to make use of the answers, and I didn't realize, but I don't have enough rep here to comment to bump them to get answers (I do elsewhere though). The auto-suggessted topics by Server Fault were very relevant. This is a test, and there is 1 machine behind pfSense that I wish to manage, and Wi-Fi makes that easy. EDIT: Why would I want to do such a thing?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |