Hi Satvinder,
You could try and put some 'outbound nat' rules on the interface that
points to the server more or less like this: source:LAN destination:LAN
translateIP:LAN-ip (assuming the server lives on the LAN..) it should
nat requests to the IP of pfSense.. And allow replies to travel back
I use dynamic DNS hosted by Namecheap.com, which is one of the DDNS
vendors supported by the DDNS feature of pfSense.
For a long time, I have had problems where pfSense appears to have
updated the IP address on the DNS server, but in reality, nothing
changes. I've just resorted to manually upd
Adam, thank you for your time and questions.
On Wed, Aug 6, 2014 at 12:04 PM, Adam Thompson wrote:
> You've made two contradictory statements here:
> 1) you want to know how to *change* a WAN interface, but
> 2) "We're moving it over from another firewall..."
I've got two firewalls, F1 and F2,
Hi,
I have tried having the Virtual Server on a different subnet and created rules
in the firewall, but still doesn’t work. I have tried having all 3 (2 Nodes +
Virtual Server) then creating a NAT for the virtual server bt still doesn’t
work, any help would be greatly appreciated.
Thanks
[http:
You've made two contradictory statements here:
1) you want to know how to *change* a WAN interface, but
2) "We're moving it over from another firewall..."
Which is it?
Why do you need to do things one step at a time? Again, that
contradicts #2, above.
Also, how much downtime is acceptable?
You
Hello!
I need to change the WAN interface address to one that is on another
subnet. I need to end up getting off the 50.31.0.0 network altogether,
ultimately, but need to do so one step at a time. However, I'm
concerned that I don't quite understand the implications of changing
the WAN primary IP
