No need of manual configuration needed, actually I would not recommend that at all. I was referring to using the SSH console to review your raw logs for quicker diagnosis if it indeed was a firewall rule issue.
Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Fri, Jan 9, 2009 at 2:15 AM, Peter Todorov <pmi...@gmail.com> wrote: > Curtus, I am no so familiar with pfsense architecture to do SSh login and > manual rewriting conf files. I have NAT yes it is AON because I have dual > WAN configuration. I have only NAT between external and internal interfaces. > I add some rules to bouth interfacese in the top just for test that has * * > * * * * and * * * * * * . Still I got no ping from DMZ to LAN. > Chris, Do I need to enable NAT between DMZ and LAN? > Thank Peter > > > On Thu, Jan 8, 2009 at 11:36 PM, Chris Buechler <c...@pfsense.org> wrote: > >> 2009/1/8 Curtis LaMasters <curtislamast...@gmail.com>: >> > Sounds like a NAT issue. Manually configure our outbound NAT or tell it >> not >> > to NAT. >> >> Not necessary. Traffic between internal interfaces isn't NATed unless >> you enable AON and configure it to do so. >> >> The firewall rules on the DMZ interface don't allow pings most likely. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: support-unsubscr...@pfsense.com >> For additional commands, e-mail: support-h...@pfsense.com >> >> Commercial support available - https://portal.pfsense.org >> >> > > > -- > честността не е порок >
