Cannot access pfSense on WAN
-
Hello!
i made a new firewall rule as i found on a guide, but there are so many options and i can't figure out which one i am doing wrong, what it can be?
![pfSENSE firewall MAIN.jpg](/public/imported_attachments/1/pfSENSE firewall MAIN.jpg)
![pfSENSE firewall MAIN.jpg_thumb](/public/imported_attachments/1/pfSENSE firewall MAIN.jpg_thumb)
![pfSENSE new firewall rule.jpg](/public/imported_attachments/1/pfSENSE new firewall rule.jpg)
![pfSENSE new firewall rule.jpg_thumb](/public/imported_attachments/1/pfSENSE new firewall rule.jpg_thumb) -
Errr… Neither the source, nor the destionation are routable. (Plus, the destination should be "WAN Address" but if that's in RFC1918 space, it will never work anywhere from internet.)
-
So how i do it? I just would like to access the machine hosting pfSENSE from a laptop which is connected to the same access point by wi-fi, while pfSense it's connected to the access point by wire.
-
I just would like to access the machine hosting pfSENSE from a laptop which is connected to the same access point by wi-fi, while pfSense it's connected to the access point by wire.
Huh?! You have it the other way round. pfSense obviously should be in front of the AP!!! (And the AP connected via some of its LAN ports to pfSense, with DHCP disabled.)
-
I made it somehow a few years back, but now i am restarting from scratch….i know it might sound unusual, but i want to access the pfSense control's interface from wi-fi, i don't want every single IP address connected to my wi-fi to have access to it, but only the IP address leased to my personal laptop.
Maybe i will just try to grant access to "any" and then protect it with a password. -
Yeah, so whitelist only the IPs you want to have access to "This Firewall" destination on the interface where WiFi AP is connected. (Need to redo the setup the other way round first, as previously posted.)
-
….. but i want to access the pfSense control's interface from wi-fi, i don't want every single IP address connected to my wi-fi to have access to it, but only the IP address leased to my personal laptop.
Maybe i will just try to grant access to "any" and then protect it with a password.pfSense is always protected by a password.
Re-enforce the access by instructing the DHCP server on pfSense to give your device (laptop) a 'fixed lease (IP)'. Then, use this IP to allow access to the GUI, locking out the rest. All this happens on LAN, of course.
When you're conformable with it - and you'll be doing as I did: had a good laugh when you look at the images you posted above, try accessing the GUI pfSense from WAN.