Bjoern A. Zeeb wrote:
On Fri, 14 Nov 2008, Robert Noland wrote:
Hi,
Also just using gre's without the
underlying ipsec tunnels seems to
work properly.
The reason for this to my knowledge is:
http://www.kame.net/dev/cvsweb2.cgi/kame/freebsd2/sys/netinet/ip_icmp.c#rev1.4
or looking at
I believe I typed/copied it correctly, but I could be wrong,
and it probably is a typo.
The problem started during the install of a new system build using
the Friday AM CVS bits, and I can't get on the system in any
mode.
Thanks
Jim
-- In Response to your message -
On Thu, Nov 13, 2008 at 06:53:41PM -0800, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xin LI wrote:
Hi, Pawel,
We can still reproduce the ZFS crash (threading+heavy I/O load) on a
fresh 7.1-STABLE build, in a few minutes:
/usr/local/bin/iozone -M -e -+u -T -t 128
Hello,
I manage a www (apache), database (postgresql) and e-mail (qmail) with
about 100 Internet domains.
We recently purchased a DELL MD3000i server with data access through
ISCSI protocol.
I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI
(v. 2.1) and SCHED_ULE scheduler.
Paul B. Mahol wrote:
On 11/17/08, Sossi Andrej [EMAIL PROTECTED] wrote:
Hello,
I manage a www (apache), database (postgresql) and e-mail (qmail) with
about 100 Internet domains.
We recently purchased a DELL MD3000i server with data access through
ISCSI protocol.
I installed a new server
On Mon, Nov 17, 2008 at 05:18:33PM +0100, Sossi Andrej wrote:
Hello,
I manage a www (apache), database (postgresql) and e-mail (qmail) with
about 100 Internet domains.
We recently purchased a DELL MD3000i server with data access through
ISCSI protocol.
I installed a new server with FreeBSD
On 11/17/08, Sossi Andrej [EMAIL PROTECTED] wrote:
Hello,
I manage a www (apache), database (postgresql) and e-mail (qmail) with
about 100 Internet domains.
We recently purchased a DELL MD3000i server with data access through
ISCSI protocol.
I installed a new server with FreeBSD 7.0
On 2008-Nov-17 08:56:55 -0500, J. W. Ballantine [EMAIL PROTECTED] wrote:
The problem started during the install of a new system build using
the Friday AM CVS bits, and I can't get on the system in any
mode.
If you try to boot to single-user, do you get the enter shell pathname
prompt? If so,
I believe there may be a regression in the behaviour of ifconfig or
possibly just something I've never experienced before.
Basically when changing the IP of one of our machines, it suddenly
became inaccessible. After some investigation it turned out the machine
was inaccessible from anything
On Mon, Nov 17, 2008 at 07:11:50PM -, Steven Hartland wrote:
I believe there may be a regression in the behaviour of ifconfig or
possibly just something I've never experienced before.
Basically when changing the IP of one of our machines, it suddenly
became inaccessible. After some
- Original Message -
From: Jeremy Chadwick [EMAIL PROTECTED]
I can try to reproduce this if you'd like, on a VMware session.
One case where the default route could be (I haven't checked) removed:
some NIC drivers in the past, when changing the primary IP (first IP
shown in ifconfig for
Bjoern A. Zeeb wrote:
On Fri, 14 Nov 2008, Robert Noland wrote:
Hi,
Also just using gre's without the
underlying ipsec tunnels seems to
work properly.
The reason for this to my knowledge is:
http://www.kame.net/dev/cvsweb2.cgi/kame/freebsd2/sys/netinet/ip_icmp.c#rev1.4
or looking at
On Mon, Nov 17, 2008 at 08:45:43PM -, Steven Hartland wrote:
- Original Message - From: Jeremy Chadwick [EMAIL PROTECTED]
I can try to reproduce this if you'd like, on a VMware session.
One case where the default route could be (I haven't checked) removed:
some NIC drivers in the
Jo Rhett wrote:
The driver logs all useful stuff, and the SEC logfile surfer does a
good job of notifying you quickly. I can send you an SEC
configuration for that if you want.
On Nov 16, 2008, at 10:06 PM, Oliver Lehmann wrote:
Hm - what is SEC?
Simple Event Correlator
This is a bug in my mind, but it's not a regression. FreeBSD has done
this for at least 10 years now. If you are changing the IP of an
interface, you *must* do a semicolon chained command to a route add
default. It's been true for as long as I can remember.
On Nov 17, 2008, at 11:11 AM,
Thanks for the confirmation on that its not a regression Jo. It really
is a nasty little bug so I'll raise a PR for it, hopefully someone
with the power will then fix it :)
Regards
Steve
- Original Message -
From: Jo Rhett [EMAIL PROTECTED]
This is a bug in my mind, but it's
Jeremy Chadwick wrote:
Summary: confirmed. Above two tests show that even if changing the IP
to something else within the same network block, the default route is
removed and not put back.
This is pretty major, if you ask me.
I've encountered similar issues before, and typically just added
Thanks for the confirmation on that its not a regression Jo. It really
is a nasty little bug so I'll raise a PR for it, hopefully someone
with the power will then fix it :)
This leads to the question - what do people *want* with respect to
static routes? I know what *I* want: The static route
18 matches
Mail list logo
