Route a wan ip to a lan ip

KOM

Here are two screens that show a port forward defined and WAN rules to allow the traffic. Note that the aliases such as WWW, cloud point to private IP addresses, not public.

1.png_thumb

2.png_thumb

johnpoz

"directly in subnet of the ISP with ip (192.168.17.3)"

Dude can you do a simple sniff on your pfsense wan… Then go to canyouseeme.org and test to port 80... Do you see the traffic to 80??

canyouseeme.jpg_thumb

Alucardko

@KOM:

Here are two screens that show a port forward defined and WAN rules to allow the traffic. Note that the aliases such as WWW, cloud point to private IP addresses, not public.

WWW and cloud, are ip's in your Pfsense Lan ?

@johnpoz:

"directly in subnet of the ISP with ip (192.168.17.3)"

Dude can you do a simple sniff on your pfsense wan… Then go to canyouseeme.org and test to port 80... Do you see the traffic to 80??

this show me in that page, Error: I could not see your service on x.x.x.211 on port (80)
Reason: Connection timed out

But I discovered something, the public IP that shows me is correct, the one assigned to 192.168.17.3
Modify message

KOM

WWW and cloud, are ip's in your Pfsense Lan ?

It's a DMZ, but yes it's a LAN.

johnpoz

"this show me in that page, Error: I could not see your service on x.x.x.211 on port (80)"

Ok did you sniff on your wan while you were doing this??? Did you see the packets get to your wan?? Like I showed you in my pic?? If yes, then you have something wrong in pfsense configuration, or something on client behind pfsense.

I you did not see these packets then there is nothng you can do in pfsense to make it work.. Pfsense can only forward traffic that gets to it.. If it doesn't get there then pfsense can not forward it..

Also since your behind a NAT and using a rfc1918 address, that your isp is forwarding this traffic to a rfc1918 address you have on your wan. You have to make sure you uncheck the block rfc1918 network rule on your wan interface.. Or no no matter how many forwards you setup it will not work because that rule would block that traffic since its inbound to your wan via dest rfc1918 address.

Alucardko

I do a lot of configurations and doenst work, then after the lunch time, I test again and it works -.-,Does it take time to apply the settings? Now I do not know what the solution was

KOM

No idea what you have done but I am glad it's working for you now.

Alucardko

@KOM:

No idea what you have done but I am glad it's working for you now.

I find whats was wrong, I explain you, in my IPS subnet I have 2 gateways (one with 100mbps, and the other 3mbps) only the gateway with 3mbps has the public ip, then I put that gateway in the WAN configuration, but this dont work, I had to put the gateway in the routing section as default, then, can you explain me, the difference between put the gateway in the Wan configuration and in the routing section?

PD: thanks for all you help

KOM

in my IPS subnet I have 2 gateways

This would have been good to know right from the start.

can you explain me, the difference between put the gateway in the Wan configuration and in the routing section?

We don't know what you have done, but each WAN needs a default gateway. You either pick one of the two, or create a gateway group with the two and weight them accordingly.

https://doc.pfsense.org/index.php/Multi-WAN

Alucardko

@KOM:

in my IPS subnet I have 2 gateways

This would have been good to know right from the start.

can you explain me, the difference between put the gateway in the Wan configuration and in the routing section?

We don't know what you have done, but each WAN needs a default gateway. You either pick one of the two, or create a gateway group with the two and weight them accordingly.

https://doc.pfsense.org/index.php/Multi-WAN

Well thanks for your help, now this post can be closed