From 192.168.3.40 can you ping 64.233.169.104, if not what does
tracert -d 64.233.169.104 show (this is MS Windows variant of
traceroute tool)?
Can you do the same from pfSense itself?
Eugene.
Hi Eugene,
Sorry for this other "out of thread" response. I think my provider is
too agressive for spam filtering and that the mailing list traffic
simply doesn't goes through.
Anyway, i'm a telecom engineer and i can tell your that pfSense seems
to have a real problem (or maybe my config, we never know).
I've done static routing, OSPF, etc on the past (Cisco, etc) and i know
what i'm doing. I'm not a pfSense expert though. I mean, sometimes i
find it difficult to understand certain way of doing things in pfSense.
I can ping from 192.168.3.40 to any host on 192.168.0.0/24 subnet
(pfSense LAN interface segment). I can ping pfSense interface
(192.168.0.222) but i cannot ping anything on the internet. Tracert
"dies" past the L3 switch. And yes, pfSense can ping anything.
As i previously said, i explicitely permitted all traffic on the LAN
interface. I have manual NAT and i defined a rule for 192.168.3.0/24.
There are no access lists on the Layer 3 switch.
I simulated a similar setup here in my lab with mOnOwall and it works
well.
Thanks for your help.
Guy Boisvert
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
