Date: Tue, 16 Jul 2002 22:09:09 -0600 (MDT) From: "Duncan Patton a Campbell is Dhu" <campbell@neotext.ca> To: freebsd@ec.rr.com Cc: freebsd-questions@FreeBSD.ORG Subject: Dynamic Rules with IPFW Message-ID: <200207170409.g6H499a24140@localhost.neotext.ca>
next in thread | raw e-mail | index | archive | help
Date: Tue, 16 Jul 2002 22:09:09 -0600
Message-Id: <20020717040909.M40939@babayaga.neotext.ca>
X-Mailer: Open WebMail 1.70 20020712
X-OriginatingIP: 127.0.0.1 (campbell)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
I use no check-states, just keep-state, and only
for DNS, soo,
${fwcmd} add pass tcp from any to ${myip} 443 setup
${fwcmd} add pass tcp from any to ${myip} 25 setup
${fwcmd} add pass tcp from any to ${myip} 22 setup
${fwcmd} add pass tcp from any to ${myip} 80 setup
${fwcmd} add pass esp from any to any
This passess https, smtp, ssh and http. Seems to stay
up. Do you need to deny established links for some
reason?
Duncan Patton a Campbell is Duibh ;-)
you wrote:
I use Dynamic rulesets with IPFW:
ipfw add check-state
ipfw add deny tcp from any to any established
ipfw add allow tcp from my-net to any setup keep-state
But I also have services I need anyone on the net to get to,
without me making a
connection first from " my-net ". I allow such services with:
allow tcp from any to my-net 25,80,443 setup in via xl0
keep-state
This works fine for 25,80, and 443. However, when I apply the
same rule for SSH,
and login to my box remotely, about 10 minutes later, the
connection just dies,
and it dies with every connection. Removing the keep-state
option for ssh effec
tively closes 22 obviously. Would check-state be a better
option here?
Michael
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207170409.g6H499a24140>