> If I understand well, you can't ping any thing from your gate so it 
> is not 
> a ipnat problem. 
> What does ifconfig -a gives you and netstat -a ? 
> Maybe try to ping 127.0.0.1 first and then your private IP 
> (192.168.xx.xx) 
> Try to stop ipfilter and the ping google.com 
 
I can ping 127.0.0.1 just fine, and it's fast, where as, if I ping 
192.168.131.5 or 24.xx.208.46 it takes a long time to get going but 
eventually does. I tried turning off ipfilter using ipf -FS and then 
ipf -D but still could not ping anything on the inet. 
 
% ifconfig -a 
rtk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 
	address: 00:30:bd:2c:be:df 
	media: Ethernet autoselect (none) 
	status: active 
	inet: 24.xx.208.46 netmask 0xfffffffc broadcast 24.xx.208.47 
 
tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 
	address: 00:04:5a:4f:81:4d 
	media: Ethernet autoselect (none) 
	status: active 
	inet: 192.168.131.5 netmask 0xffffff00 broadcast 
192.168.131.255 
 
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33220 
	inet 127.0.0.1 netmask 0xff000000 
 
ppp0: flags=8010<POINTTOPOINT,MULTICAST> mtu 1500 
PPP1: flags=8010<POINTTOPOINT,MULTICAST> mtu 1500 
 
thanks for all your input Jean-Christophe. 
--  
 _  
( ) ASCII ribbon campaign   Mark Thomas  
 X  against HTML e-mail     www.theswamp.org  
/ \