I got the following output from ipfw show in my daily security run output
email.
+++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005
+00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1
+0252218 784 deny tcp from any to any in via sis1 setup
+65530 0 0 deny ip
On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote:
The only explanation I have is that the packets arrived between the
time when the machine started accepting incoming packets and when
the rules were loaded in /etc/rc.d/ipfw.
You just explained this yourself.
One solution to this small
Hi all,
Just installed 6.0-STABLE/amd64 (cvsup from within the last day)
onto a K8 Sempron with IPSEC compiled in and I get a kernel panic
when I try to run racoon. Anyone else seen this?
Unfortunately the usual ways I know how to debug don't work:
* kgdb /path/to/kernel.debug
The message Mail System Error - Returned Mail from MAILER-DAEMON, sent on
12/12/2005 15:55 was quarantined because it contained either an executable
file, a batch file or a screen saver file. All of these types of attachments
are considered security risks. Please consult your mail administrator
On Sun, Dec 11, 2005 at 06:22:40PM +, Gavin Atkinson wrote:
G I'm trying to use puc(4) under RELENG_6 to attach the two serial ports on
G a PCI card I have, but it's not working. It also fails under 6.0-RELEASE,
G I don't have the ability to test earlier versions.
G
G The card is
I'm about to start installing a whole new set of machines for production
use with 6.0 on them. Normally I would just use -RELEASE, but as this is
a dot-nought release I was wondering if there is anything vital which
has been commited to stable, and if I should therefore sun the machines
under
Pete French wrote:
I havent seen anything go past which I regard as
critical, though somebody did make a mention of some arp problem
being fixed, which I could find a reference to the original
problem for.
The ARP problem is not in -RELEASE, it was introduced in -STABLE and
fixed a day
On 12/12/05, Graham Menhennitt [EMAIL PROTECTED] wrote:
I got the following output from ipfw show in my daily security run output
email.
+++ /tmp/security.yri47lgA Mon Dec 12 03:01:45 2005
+00522 3530 1204158 deny ip from 10.0.0.0/8 to any via sis1
+0252218 784 deny tcp from
The ARP problem is not in -RELEASE, it was introduced in -STABLE and
fixed a day later.
Ah, O.K. thanks
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On Mon, 12 Dec 2005 16:03:59 +0100, Pete French
[EMAIL PROTECTED] wrote:
I'm about to start installing a whole new set of machines for production
use with 6.0 on them. Normally I would just use -RELEASE, but as this is
a dot-nought release I was wondering if there is anything vital which
has
Hi,
I have 3 machines running 6.0-RELEASE, and recently 2 of them started
freezing once a day or so. There are no error messages on the console or
in the system logs.
The first one I put in production about a month ago and it was working
flawlessly until it got some load and now it started
The load I'm talking about is less than moderate (less that 2.0 with
plenty of CPU idle time). The freezing thing also does not appear to
happen at peak times (I have rrdtool based CPU load graphs).
Both machines have (almost) identical motherboards:
Intel SE7520JR2SCSID2 and SE7520JR2ATAD2
On Mon, 12 Dec 2005 22:15:55 +0100, Atanas [EMAIL PROTECTED] wrote:
Hi,
I have 3 machines running 6.0-RELEASE, and recently 2 of them started
freezing once a day or so. There are no error messages on the console or
in the system logs.
What happens if you set one of these sysctl values to 0?
On Mon, 2005-Dec-12 13:15:55 -0800, Atanas wrote:
I have 3 machines running 6.0-RELEASE, and recently 2 of them started
freezing once a day or so. There are no error messages on the console or
in the system logs.
The first one I put in production about a month ago and it was working
flawlessly
Claus Guttesen said the following on 12/12/05 13:23:
Both machines boot with ACPI and hyperthreading enabled.
Try to disable HTT in bios.
I think that I already achieved that by simply disabling the acpi module
from device.hints, and it had no effect to the problem.
It seldom gives you
Ronald Klop said the following on 12/12/05 13:27:
What happens if you set one of these sysctl values to 0? (This disables
SMP changes from 5.4 to 6.0.)
debug.mpsafevfs: 1
debug.mpsafenet: 1
debug.mpsafevm: 1
Thanks for the suggestion!
I just did so and rebooted both machines, so we'll see.
I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up twice
in the past few days. never once had it happen with 5.x. everything locks,
no keyboard response, no mouse, and after several minutes it reboots itself,
and savecore starts up during boot.. and again, it's not during
Peter Jeremy said the following on 12/12/05 13:40:
Define freezing: Does it respond to pings? Can you switch VTYs?
Do the num-lock/caps-lock LEDs respond? Do some processes seem to
freeze before others?
I used the word freeze instead of crash, because the latter often
gets associated with
On Mon, 2005-Dec-12 22:21:52 -0400, fredthetree wrote:
I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up twice
in the past few days. never once had it happen with 5.x. everything locks,
no keyboard response, no mouse, and after several minutes it reboots itself,
and savecore
Atanas said the following on 12/12/05 15:43:
Ronald Klop said the following on 12/12/05 13:27:
What happens if you set one of these sysctl values to 0? (This
disables SMP changes from 5.4 to 6.0.)
debug.mpsafevfs: 1
debug.mpsafenet: 1
debug.mpsafevm: 1
Thanks for the suggestion!
I just
Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET)
From: Trond Endrest?l [EMAIL PROTECTED]
Subject: Re: puzzling ipfw show output
To: FreeBSD stable freebsd-stable@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
On Mon, 12 Dec 2005 19:09+1100, Graham
On Mon, 12 Dec 2005 22:03-0800, James Long wrote:
Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET)
From: Trond Endrest?l [EMAIL PROTECTED]
Subject: Re: puzzling ipfw show output
To: FreeBSD stable freebsd-stable@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: TEXT/PLAIN;
Dear All,
one of my 6.0-STABLE box always panic once a day.
here's the dump:
lapi# kgdb kernel.debug vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB
Trond Endrestøl wrote:
On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote:
The only explanation I have is that the packets arrived between the
time when the machine started accepting incoming packets and when
the rules were loaded in /etc/rc.d/ipfw.
You just explained this
24 matches
Mail list logo
