Cannot figure out how to connect to a computer on my network remotely
I have a NAS that I would like to be able to remotely administer from time to time. Before I built my own pfSense router, I could just forward ports so that when I used my DynDNS url (dyn.dns.url:XXXX, where XXXX is the port I need to connect to) I could route it to my NAS.
Like let's say my NAS has the IP address on my network 192.168.1.5, and the service I need to access via webGUI is on port 1024, I used to be able to use dyn.dns.url:1024 to connect from outside my LAN to 192.168.1.5:1024 inside my LAN.
How do I do that with pfSense?
viragomann last edited by
With a port forwarding rule, similar to other routers. NAT > Port Forward
Add a rule with:
interface = WAN
Protocol = TCP
source = any (default)
destination = WAN address
Destination port range = (other) 1024
Redirect target IP = 192.168.1.5
Redirect target port = (other) 1024
Filter rule association = pass
If pfSense is behind another router you have to forward any traffic to pfSense.
Not something I would suggest.. If you want to manage stuff remotely on your network, you should vpn into your network and then manage. Opening up management webgui's and such to the internet at large is not a very good idea!
Is there a guide for setting up a VPN like that?
Here's a related issue. I also have some IP cameras that I use for home security. I can connect to them REMOTELY (like over my phone's LTE network. But I cannot connect to them from within my network.
Let's say I hook my phone up to my wifi. My camera app on the phone is set up to connect to my IP camera server (internal IP 192.168.1.122) through my DynDNS account on port 8000 and 8554. As I said, I can easily connect to them remotely, but why can't I connect to them from inside? I look at my firewall and it says it should be passing any LAN port to any LAN port. What am I doing wrong?
biggsy last edited by
OK, that's taken care of the remote login! Thank you.
That was a remarkably useful guide.
Now, as for the other issue, I seem to have "solved" it by creating two instances of my security cameras, one for "inside" my LAN and one for "outside" my LAN. Seems to work for now, but I'd still like to know what's going on.