Need some routing assistance with pfSense, DMZ and WebSite
-
@ILO_EWS said in Need some routing assistance with pfSense, DMZ and WebSite:
As the pfsense is connected to my ISP router, all traffic from 443 are redirected to port 443 on PfSense IP.
As long as that's true it should work.
-
@stephenw10 if that was true then he would see that traffic hit his pfsense wan, be it he had any ports working or not via sniff.
-
@johnpoz
So in this case, do you think that the problem is on the configuration of my ISP routeur ?
Best regards -
@ILO_EWS go to like can you see me . org and send some traffic to 443 while you're doing a packet capture on pfsense for your wan IP and port 443 do you see anything with destination of pfsense IP to 443..
if pfsense doesn't see inbound to its 443 then no it can not forward anything.. Also that any any rule isn't right.. When you create your port forward it should auto create your wan firewall rule to allow 443 to your host your forwarding to IP.
-
@johnpoz said in Need some routing assistance with pfSense, DMZ and WebSite:
go to like can you see me . org and send some traffic to 443 while you're doing a packet capture on pfsense for your wan IP and port 443 do you see anything with destination of pfsense IP to 443..
if pfsense doesn't see inbound to its 443 then no it can not forward anything.. Also that any any rule isn't right.. When you create your port forward it should auto create your wan firewall rule to allow 443 to your host your forwarding to IP.
When I launch a test on this website, this error appear
Error: I could not see your service on 82.66.xxx.xxx on port (443)
Reason: Connection timed outBest regards
-
@ILO_EWS but that doesn't tell you if even got to pfsense.. You need to do a packet capture to see if it even got to pfsense, or yeah no duh its not going to work and yeah it would time out.
edit: example... I don't have anything listening on 666, no forwards, etc.. but if I send traffic pfsense still sees it.. And yeah since no answer it would time out
edit: what does your router in front of pfsense show for its wan, for all we know its a cgnat IP and no forwards are ever going to work.
-
Yup, the result is not important. The test is that the traffic arrives at the pfSense WAN. So in the pcap as suggested or openning states in the state table.
-
@ILO_EWS
and @stephenw10 :
Something did come on :
The first rule - that should have been removed by now - clearly shows TCP traffic was entering = coming from the Internet.
With that first rule removed, the second and third now have chance to work.so I presumed : no cgnat horrors.
When testing, the counters "0/0 B" should not stay at 0/0. 0/0 means nothing arrivd at the WAN interface that matches the rule.
For fast NAT, or whatever, testing, no need to packet capture, or look at the state table : look at your firewall rues, and see if they get used/applied.Also, ISP router, the one in front of pfSEnse, can have DMZ look alike options.
Don't use them.
Handle incoming incoming connection the old classic way :
You have to NAT a port (for your web server who lives at the network called DMZ) on pfSense.
You have to do the same thing on the ISP router : NAT that port to the pfSense WAN IP. -
@Gertjan said in Need some routing assistance with pfSense, DMZ and WebSite:
so I presumed : no cgnat horrors.
While that a good observation - you don't know what else on that transit network between his router and pfsense could be sending traffic.. He has removed the block rfc1918 so that could be traffic from pretty much anything.
I agree that rule shouldn't be there for sure.
-
@johnpoz
Excuse me but in what part of pfsense configuration could i sée this traffic.
Indeed, i dont found something liké that.
Best regards -
@johnpoz said in Need some routing assistance with pfSense, DMZ and WebSite:
rfc1918
In défaut configuration i never has a rules with rfc1918, may I add one ?
Best regards -
@ILO_EWS the wan interface out of the box would always have a block rfc1918 rule.. Maybe they changed something that if your wan was rfc1918 to not add it, but unlikely - and there would be normally the block bogon rule as well..
So either that isn't your wan interface actually, and you renamed it to wan? But wan interfaces default to have a block rfc1918 and bogon.
You must of turned them off??
you don't really need those, especially if your behind a nat already - but odd that they are not listed? Packet capture would be under the diagnostic menu
-
@johnpoz As my web server is on DMZ area, does I check DMZ interface or WAN interface ?
Best regards -
@ILO_EWS traffic comes into the wan - that is what is connected to the internet.. Then pfsense would port forwarded it to the IP you set to forward to on your dmz..
If the traffic never hits your wan, kind of hard to forward it to your IP in your dmz.
This an example of a port forward.. You should have a port forward rule
Which would by default create the firewall rule you need
So the port forward says any tcp traffic on port 23040, send it to my plex server that is on 192.168.9.10 on port 32400
The firewall rule allows this.. The only difference really in mine is that I limit what IPs can be forwarded to IPs that are in my pfb_allowPFb alias, which is the IPs that check if plex is available, both from plex check, and my own checks to notify me if plex goes down. And your IP also has to be a listed US ip.. All of my users are in the US.
But traffic never hits my wan ip, pfsense could never forward this. You will notice have forwarded 6.22GB of traffic through this rule since the last time those counters were reset.
If when you do a packet capture on pfsense - and do say a test from that can you see me site and you never see anything hit pfsense wan interface how could it ever forward it?
here via a packet capture I can see on my wan traffic come in on port 23040, and in my case an answer back - but if that traffic never comes in on 23040 pfsense could never forwarded it to be answered.
