Sai, It was whatever the default was...auto, I think. 

Curtis 

----- Original Message ----- 
From: "sai" <[EMAIL PROTECTED]> 
To: support@pfsense.com 
Sent: Tuesday, April 8, 2008 1:30:56 AM (GMT-0500) America/New_York 
Subject: Re: [pfSense Support] SOLVED - Strange problem 

curtis, what was the previous setting? 

sai 



On 4/8/08, Curtis Maurand < [EMAIL PROTECTED] > wrote: 


The problem turned out to be packet state maintenance. I set it to "Keep State" 
for all of my rules having to do with NAT and tunnels and it solved all of the 
problems. It was one of those "duh." moments. :-) 

Its kind of interesting that Windows 2000, 2000 Server, XP and 2003 Server 
didn't seem to care about the setting. 

Thank you to all who had suggestions on these two problems. 

Sincerely, 
Curtis Maurand 


----- Original Message ----- 
From: "RB" < [EMAIL PROTECTED] > 
To: support@pfsense.com 
Sent: Tuesday, March 18, 2008 2:15:34 PM (GMT-0500) America/New_York 
Subject: Re: [pfSense Support] Strange problem 

On 3/18/08, Curtis Maurand < [EMAIL PROTECTED] > wrote: 
> Like I said, it works fine on the same hardware if I run Windows, but not if 
> I run Linux. I've used IE and firefox on Windows, IE, firefox, epiphany and 
> konqueror on Linux. I wish I had a MAC to test with. :-( 

I have one, and it works fine on my various networks. 

OS and hardware likely aren't the issue here. Have you done something 
like 'export http_proxy=" http://foobar:8080 "' in your profile on the 
Linux box, or set up a port redirect with iptables, or any one of the 
other thousands of ways to muck with your http traffic on a Linux 
client? Have you tried using wget, curl, or lynx? 

Try the tcpdump from your pfSense system; it'll be the most immediate 
and apparent. If you see appropriate traffic (which at the moment I 
honestly doubt you will), then there's something really strange with 
your pfSense setup. Otherwise, you know it's something on the client. 

--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 


Reply via email to