Hi all,
When my OpenBSD 3.5 System tries to load the PF ruleset it shows the
following error.
/etc/pf.conf:22: could not parse host specification no IP address
found for dc0:172.16.0.0/12
the 22nd line of my pf.conf is this.
nat on $ext_if from $int_if:172.16.0.0/12 to any - $ext_if
this is
Hi,
playing with pftop and src-track I discovered that every connection from my
home network to my OpenBSD 3.5-stable server on the internet doesn't get
closed. PF always shows the FIN_WAIT_2:FIN_WAIT_2 status.
This means that if I use telnet to any open port and then I close the
connection
Sounds like a valid option, but I am sure they would rather just
hire a hardcore microsoft person and then just use the cisco
support to fix whatever problems they have.
Someone should start a PF pay for support program =)
Take money and give management people the warm fuzzy feelings.
I wish I
On 20/09/2004, M Raju [EMAIL PROTECTED] wrote To [EMAIL PROTECTED]:
Anyone running OpenBSD PF as the primary firewall for large mid-large
orgranizations? If so what type of hardware, setup, etc. Just
curious..
case 1: replace PIX by OpenBSD on a 1.1ghz el-cheapo-19 PC --
doubled that
On Sep 23, 2004, at 9:29 AM, Michael Clark wrote:
If I was not here they would have no one to work on it.
Awesome logic. Why does the company do anything at all, then?
Well, it can be a telling point. For my part, I alleviated my Managing
Director's concerns about implementing OBSD + pf
Siju George wrote:
Hi all,
When my OpenBSD 3.5 System tries to load the PF ruleset it shows the
following error.
/etc/pf.conf:22: could not parse host specification no IP address
found for dc0:172.16.0.0/12
the 22nd line of my pf.conf is this.
nat on $ext_if from $int_if:172.16.0.0/12 to any -
Thankyou somuch Cedric, Its working now! I greatly appreciate your help!
God bless you
siju
This is geeky, but a thing of beuty. I'm not a big fan of AMD,
but I got instant wood looking at the pictures of the soon-to-
be-out Iwill ZMAXdp:
http://www.amdboard.com/iwill_zmaxdp.html
I have a OpenBSD 3.5 with 3 external interfaces (WAN) and with squid
twirling.
xl0 - 200.x.x.x (default route)
rl0 - 192.168.254.253 (dsl)
rl1 - 192.168.254.254 (dsl)
He would like to make squid to leave for the interface rl1 the same
being that this twirling in this exactly gateway with
On Saturday 25 September 2004 15:30, Mike Frantzen wrote:
This means that if I use telnet to any open port and then I close the
connection PF will keep the connection in FIN_WAIT_2 status until the
time limit expires.
TCP goes into a 2msl time wait state after the connection closes in case
This means that if I use telnet to any open port and then I close the
connection PF will keep the connection in FIN_WAIT_2 status until the time
limit expires. This is a behaviour that you don't note without the src-track
option because the server will keep accepting new connections...
The
adding on to cedric's answer
you may also want to add ( ) around interface if this outside interface
gets address via DHCP
nat on $ext_if from $int_if:network to any - ($ext_if)
--
clint
Cryptek, Inc.
Cedric Berger wrote:
Siju George wrote:
Hi all,
When my OpenBSD 3.5 System tries to load
On Sat, 25 Sep 2004 13:41:40 -0300, Gustavo [EMAIL PROTECTED] wrote:
I have a OpenBSD 3.5 with 3 external interfaces (WAN) and with squid
twirling.
Can anybody translate squid twirling ?
xl0 - 200.x.x.x (default route)
rl0 - 192.168.254.253 (dsl)
rl1 - 192.168.254.254 (dsl)
He would
TCP goes into a 2msl time wait state after the connection closes in case
a segment got delayed in the network. That is how TCP works.
This explains the TIME_WAIT:TIME_WAIT status, but what about FIN_WAIT_2 ?
The TCP state labels in PF can not perfectly follow the RFC flow
diagram. PF has
14 matches
Mail list logo
