Why put everything on the pfsense firewall if that's what you're thinking. I use pfsense for sipx remote workers and ITSP's, leaving the rest of my traffic on my main firewall. On the sipx boxes, I just point them to their gateway of which ever pfsense they reside on. So far, seems to work very well and I didn't have to change my whole network.
I started with Tony's example, edited to my own needs and it worked right out of the box. Mike On Mon, 12 Jul 2010 16:32:57 -0400, Michael Scheidell wrote: > On 7/12/10 1:54 PM, Tony Graziano wrote: > you could just donwload the > sample config from my blog though... > >> > looks like the 'port forwarding' might not work for a whole network of > different types of hosts behind the pfsense. > this below looks like it will take anything and forwar it out the WAN ip, > and anything coming in the WAN ip and FWD it to those two internal servers. > > this would leave other public servers (private ip behind nat) trying to go > out the same want ip, I think. > > I have 36 different smtp servers, a dns server, 40 web servers,etc. > > even assiging virtual ip's (and I expect the virtual ips are type of > 'other'?) and doing port forwarding, the smtp servers who HAVE to go out > specific ports for RDNS, SPF and other server firewall rules on other > networks. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
