New to pfsense
-
Please post screen shots if your Firewall rules.
Have you tried connecting to the internal machine with its internal IP address? If you can access your resources internally with their IP addresses, don't beat yourself up if NAT Reflection isn't working properly. I run internal DNS and don't use NAT Reflection because some of the systems I use and how I use them work more efficiently with internal DNS.
-
Hi Tim.
Unfortunately, using DNS will not work. Once again, the program is hard coded in as an IP address. I can't change this. So, I need to figure out why just higher ports don't work with NAT reflection. NAT reflection works great for lower ports such as HTTP (80), HTTPS (443), SMTP (25), POP3 (110), and FTP (21). Just isn't working for higher ports. This isn't a firewall issue. This is a NAT Reflection glitch. My question is, is there a way around this?
Thanks
-
To re-produce the problem, you can setup either a Telnet, FTP, or HTTP on port 9987 internally and try to access it with your internal IP and it won't work.
I think you must have left something out here because I am absolutely confident that if I setup up a web server on my internal network that runs on port 9987 and then tried to access it directly from the same network at http://192.168.1.34:9987 it would work.
Presumably it's the client half of your program that can only use IPs directly?
One thing that occurs to me is that the server program itself may be configured to always use an external gateway of some sort such that it is unable to route back to internal address.
Steve
-
Hi Steve.. Sorry, maybe I didn't make it real clear. I am using my external address to access it. So, with your same test, lets say your external IP address is 60.54.1.23… From internal on another client, you would want to access http://60.54.1.23:9987 and it will fail.
Also note, that it works fine if you are outside your internal network. This is why I am thinking it is not a firewall issue as it works from outside the network!
Thank you.
-
Forgive me for not completely understanding, but you have a server that lives on your internal network with a local (internal) IP address. And you have clients that access that server with a hard-coded IP address and port using an external IP address. And you cannot change the IP address of these clients or any other networking information? Seems odd that in this day and age people would set something up like that, but that's IMHO.
If you want to host a Teamspeak server internally and make it accessible from internal and external IP addresses, I can help you with that. I've done that countless times, and I authored the "How To" post in the forums for Mac users.
-
Ah, OK.
I agree with Tim that not being able to use a URL instead of an IP seems quite archaic. ;)
You could setup a manual port forward for that on the LAN interface. I don't know why NAT reflection wouldn't take care of that for you though. You can specifically disable it for each port forward, I assume you haven't done that?Steve
-
Ah, OK.
I agree with Tim that not being able to use a URL instead of an IP seems quite archaic. ;)
You could setup a manual port forward for that on the LAN interface. I don't know why NAT reflection wouldn't take care of that for you though. You can specifically disable it for each port forward, I assume you haven't done that?Steve
No. I haven't done that.
As far as creating a forward on the LAN side, I have tried putting in the NAT Port Forward rule as you show in your example. This also didn't solve the problem :( I even tried setting "NAT Reflection" in the rule to "enable" and still nothing :( Any other recommendations? By looking at that, it really seems like it would work :(…
Thanks for all your help!
-
Forgive me for not completely understanding, but you have a server that lives on your internal network with a local (internal) IP address. And you have clients that access that server with a hard-coded IP address and port using an external IP address. And you cannot change the IP address of these clients or any other networking information? Seems odd that in this day and age people would set something up like that, but that's IMHO.
If you want to host a Teamspeak server internally and make it accessible from internal and external IP addresses, I can help you with that. I've done that countless times, and I authored the "How To" post in the forums for Mac users.
TS is not a prob I can use the internal IP and port for it I can even use internal DNS as someone said above option 2 split DNS that file for the TS prob, the prob is I am working on a project that has to use the out side IP DNS is not an option and the IP is hard coded into the client exe file witch is used both inside and outside my network but I will also like to know Y only the higher IP's are giving me prob 25,110,443,80 they all seem to work for the most part anyway even if someone has a work around I will be fine with that just let me know I am working on 2 projects 1 I have no control over it can't use DNS local but the second one I might I will check into it and see what I can do since I have full control over it i'll see what I can do thanks
Sincerely
tbarlow -
This thread might help; long shot though. http://forum.pfsense.org/index.php/topic,61201.0.html
Can you post your NAT and Firewall rules? Screen shots will speak volumes.
-
I think that option (in the linked thread) only applies to 1:1 NAT. It's interesting though.
Steve
-
Hi Steve.
Did you happen to see my screenshot? Did it look like I was doing that correctly? Because it didn't work either :(
Any other thoughts?
-
Hmm, I'm not sure if you should have NAT reflection enabled on that internal port forward or not. :-
With changes like this, especially if you have already been trying various connections, you may have to clear the state table to force the new rules to take effect.Steve
-
Steve - I cleared state and no change :(
After I cleared state and tried again, I looked in state to see what it says for that port. I am attaching that.
Do we have any other recommendations??? :(
Thanks