Slow Speeds
-
@KOM thanks will do
-
i don't understand why you installed windows and a vm to run pfsense and added a modem/router later, was not working on day 2 ? so now do you have a double nat situation ?
-
@kiokoman day 2 was the i5 and pfsense directly on it. So the setup was modem>pfsense>access point
I needed to access the web GUI remotely so I installed windows and then pfsense in the virtual box.
Thanks
-
hell no, man, you don't need windows or teamviewer to access it remotely, you just need to configure openvpn or ssh + tunnel with putty to access it
-
@kiokoman i red on it and looked at YouTube videos but it seemed like people had access to black and white interface not the web GUI. For this reason I though it wasn’t possible to access remotely to the web GUI.
-
of course it's possible
i will suggest you to go back to day 2 asap
after that you can ask for specifical instruction on howto access the webgui from remote -
Either way will work depending on your use case. In my virtual lab, I use a vm to control pfSense from the LAN side, which is separate from my real LAN ( real LAN acts as the lab's WAN). In production, I would use OpenVPN to connect securely and then access WebGUI via the OpenVPN server interface.
-
@KOM do you experience slow downs? Is it okay if my router between the modem and host is in AP mode or I have to change something on it ?
-
No, I don't have any speed issues. I've had issues in the past with VMXNET3 NICs, though. Perhaps try again with Intel e1000? I'd also pay attention to speed and duplex settings, which can really cause all sorts of problems. That old PC might have crappy NICs in it, likely Realtek which are known to be iffy at best. You might benefit form picking up a real Intel or Broadcom card and using that. Your wifi router should be put in AP mode (disable WAN, disable DHCP server, connect LAN port to LAN switch) and run it behind pfSense.
-
@KOM ok thanks will try that
