Enable internet access from LAN
-
Ok it looks like your port forward for that server is listing at 104.x.x.5 but you are trying to open 104.x.x.35.
Is that just a typo? Correct it if so.If it's a VIP on the WAN then try to open that IP.
Steve
-
@stephenw10
I have 2 servers, one is web sever has external IP 104.190.X.X.5 and internal 192.168.1.5, second is mail server has external IP 104.X.X.35 with internal IP 192.168.1.5, I want both be behind pfsense and accessible from outside through port forwarding
yes I have virtual IPs
sorry, what do you mean by opening that IP?
do you mean set a LAN rule with destionation address =104.x.x.5 ? -
@maale
Sorry, I mean a WAN rule -
I mean try to open the page by IP address directly rather than URL which would need to resolve.
Both those IPs look like they should work though assuming the server can respond.
Check the pfSense state table in Diag > States while you;re testing. You should see the states on WAN and LAN complete with NAT on WAN.
Steve
-
So what is your actual IP of your pfsense wan? You have vips of .5 and .35 - what is the actual IP?
Have you gone through the troubleshooting doc I Linked too - finding the issue with port forwarding is 2 minutes work tops!!! do a sniff do you see the traffic on your wan or not? Sniff on lan - do you see it send the traffic on?
For all you know the traffic is being forwarded and your system your forwarding to firewall is blocking the traffic - very common!!!
-
@johnpoz
Thanks!The problem was that the routing environment doesnot support Virtual IPs.
All traffic should be hit the pfsense WAN IP at 104.x.x.10 .So, I have set an external DNS with an IP 104.x.x.25 with my domain and records www.x.av for web server and mail.x.av for mail server, with port forward rules.
Now from an external machine 104.x.x.15 using the domain www.x.av I can access the web server, but using the domain mail.x.av, this directs me to the same webpage for the web server but not for the mail server. Is NAT reflection what I need to do? -
@maale said in Enable internet access from LAN:
routing environment doesnot support Virtual IPs.
Huh - that makes no sense at all.
Is NAT reflection what I need to do?
No its not... if you want host.domain.tld to get sent to X, and other.domain.tld to get send to Y behind pfsense then you need to use multiple wan IP, vips or not... Or you need to hit different ports in your url, or you need to setup a reverse proxy to know that host.domain.tld goes to X and that other.domain.tld goes to Y.. Look at the HA proxy package.
-
@johnpoz
I mean the lab routing environment.
ok I look for the HA package -
Lab routing environment or real routing environment... Has zero to do with anything - an IP address that is in same network, has zero to do with routing...
-
Mmm, that.
Why can you not use multiple IPs on WAN? What VIP type were you trying to use? Use IPAlias if you were not.
Steve
-
Maybe he meant their virtual environment that pfsense is running on? Maybe issues with vips in some VM setups, where you might have to do some promiscuous setting. But if VM, he could just create some new virtual interfaces and since he is using dhcp in this network.. He could have 3 different wan interfaces using 3 different IPs and then port forward..
-
@johnpoz
I am trying to install the HA proxy package, but I cannot see any packages listed. could you please let me know why? I can connect to www.pfsense.org successfully. And I have installed bind package before, but now a I cannot find available packages
-
That because your pfsense install can not resolve most likely, since you prob installed bind and F'd it up..
Go to diagnostic menu, dns - lookup up something.. what does it show..
You connecting to something is completely different than pfsense resolving something.. What is your client using for dns, what is pfsense?
-
@johnpoz
I am using the pfsense DNS resolver and other 2 external DNS servers. diagnostic menu, dns - lookup google.com, gave no response from 127.0.0.1 but response from one of my external servers with google's IP address. -
@maale said in Enable internet access from LAN:
I am using the pfsense DNS resolver and other 2 external DNS servers
Not how it works - you are either resolving, or your using external dns via forwarding..
Your resolver is not working most likely because whatever network pfsense is on is prob blocking direct dns queries - and only allows access to googledns or whatever.
So change to forwarder mode..
-
@johnpoz
Thanks so much, now I can see the available package list -
@johnpoz
Because I am using the same domain name for my internal and external services, I have used the bind9 package to set split DNS as follows and it works fine to resolve inside LAN and outside. All services from outside have pfsense WAN address.
This is first zone file for internal addresses.
This is the second zone for external addresses.
I also have set a NAT rule with destination= 127.0.0.1 port 53 in the LAN and WAN interfaces. So that split DNS works fine.
Because all services have pfsense WAN address I used the squid reverse proxy package with the web and mail servers at 192.168.1.5 and 192.168.1.35. I want www.x.av goes to the internal web server at 192.168.1.5 port 80. And https://mail.x.av goes to the mail server at 192.168.1.35 port 443 and 143.
. I set a WAN rule with source any destion :this firewall port 80 so that the traffic goes to the squid reverse proxy. That doesnot work for me, from outside I cannot access any of the two servers! Could you please let me know what is wrong with this setting?
Thanks. -
You don't need bind to do split dns... And its at best problematic use the same domain internally as you do externally..
-
@johnpoz
so I can use the pfsense resolver and add hostoverides e.g www.x.av IP 104.x.x.10 ? or it is better to built an exteral dns for external quiries? -
What boxes exactly are going to be using pfsense as their dns? Your saying your going to make it the authoritative ns for your domain on the public internet? BAD IDEA!!
If your going to do that, then you would for sure have to setup different views..
