On 8/14/06, Charles Lacroix <[EMAIL PROTECTED]> wrote:
On Monday 14 August 2006 09:42, Cristiano Deana wrote:
> 2006/8/14, Charles Lacroix <[EMAIL PROTECTED]>:
> > i was wondering which icmp type packets people accepted on there
> > production servers.
>
Just echo (echo-req) from anywhere. p
On Monday 14 August 2006 18:39, Scott Ullrich wrote:
> I am testing out CARP on RELENG_6 as of yesterday and I am seeing a
> panic when attempting to destory a CARP interface:
>
> # ifconfig carp0 delete
> # ifconfig carp0 destroy
> # panic: thread 100049(ifconfig):0 holds carp_if but isn't blocked
Hello!
I am testing out CARP on RELENG_6 as of yesterday and I am seeing a
panic when attempting to destory a CARP interface:
# ifconfig carp0 delete
# ifconfig carp0 destroy
# panic: thread 100049(ifconfig):0 holds carp_if but isn't blocked on a lock
KDB: enter: panic
[thread pid 12 tid 14
On Monday 14 August 2006 09:42, Cristiano Deana wrote:
> 2006/8/14, Charles Lacroix <[EMAIL PROTECTED]>:
> > i was wondering which icmp type packets people accepted on there
> > production servers.
>
> did you read firewall(7) ?
I just checked it and it's talking about ipfw, i searched the man pag
2006/8/14, Charles Lacroix <[EMAIL PROTECTED]>:
i was wondering which icmp type packets people accepted on there
production servers.
did you read firewall(7) ?
--
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
freebsd-p
Hi,
i was wondering which icmp type packets people accepted on there production
servers. I would just like to have feedback on this to see what people do
about these. At the moment i allow all of the icmp type traffic but i wanted
to disable some of the less used types.
Thanks
Charles
--
Char
Bill, I stand corrected. Please forgive my imperfections. I only studied
and restudied this material 10 hours a day for 4 days. I must be blind!
Again, forgive me for not being as perfect as I should be, and for
missing this point. You are quite right to criticise me, and I accept
your judgment
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
o kern/82271 pf [pf] cbq scheduler cause bad latency
f kern/86072 pf [pf] Packet Filter rule
