ate that is expected
from the server. So whether it is bad or not, it has to match what the
firewall was expecting or the host is considered down and taken out of
rotation.
Kevin
On Mon, Feb 9, 2009 at 4:15 PM, Stuart Henderson wrote:
> On 2009-02-09, kevin thompson wrote:
> > Is there
ont seem to be showing
up anywhere.
# pfctl -sn
rdr-anchor "relayd/*" all
# pfctl -sr
anchor "relayd/*" all
pass in on bge0 proto tcp from any to (bge0) port = https flags S/SA
keep state
Shouldn't there be a folder called /etc/relayd that would have some
files in it? I don't have that. Does anyone have any thoughts on what
I'm missing here?
Kevin Thompson
I posted a couple weeks ago about my relayd configuration and how it seemed
that it was not relaying traffic. Since then I have been trying to simply
the configuration and make *something* work. I was successful in getting
relayd to listen on port 80 and forward traffic to a group of other web
se
up an http relay and assumed that setting up an https relay was
almost the same. I'll try using a regular tcp relay. Thank you.
Kevin
On Mon, Feb 9, 2009 at 3:15 PM, Stuart Henderson wrote:
> On 2009-02-09, kevin thompson wrote:
> > Is there something in my configuration file t
I'm a lurker on this mailing list, and I'm no master of pf, but I think the
problem is that your block statement comes before all of your pass
statements. In most firewall configurations, rules are processed until one
matches and then no others are processed. So if the first rule that matches
you
5 matches
Mail list logo
