From: Matt Mackall <mpm@selenic.com>
To: Park Lee <parklee_sel@yahoo.com>
Cc: linux-kernel@vger.kernel.org, ipsec-tools-devel@lists.sourceforge.net
Subject: Re: Issue on netconsole vs. Linux kernel oops
Date: Fri, 17 Dec 2004 23:41:37 -0800 [thread overview]
Message-ID: <20041218074137.GA28322@waste.org> (raw)
In-Reply-To: <20041218060134.77655.qmail@web51503.mail.yahoo.com>
On Fri, Dec 17, 2004 at 10:01:34PM -0800, Park Lee wrote:
> On Fri, 17 Dec 2004 at 08:44, Matt Mackall wrote:
> >
> > Netconsole builds very simple IPv4 packets by hand
> > without the use of the rest of the IP stack. This
> > is how it continues to work when the system is
> > crashing. So it will never be able to build IPSEC
> > packets.
> > Nor is it likely to do IPv6 any time soon.
> >
> > You can probably get it to work by using a
> > different IP address for netconsole than you use
> > for IPSEC, and set up the receiving end to
> > recognize packets from that address as normal
> > unencrypted IPv4.
>
> Thank you.
>
> But that will need at least 3 computers(i.e. 2 for
> IPsec, 1 for receiving end), Am I right?
No, you should be able to configure a non-IPSsec interface on the
receiver, possibly at a fourth address.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-12-18 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 12:12 Issue on netconsole vs. Linux kernel oops Park Lee
2004-12-17 16:44 ` Matt Mackall
2004-12-17 17:03 ` Bill Rugolsky Jr.
2004-12-18 6:01 ` Park Lee
2004-12-18 7:41 ` Matt Mackall [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-16 15:00 What's the matter with build-in netconsole? Paulo Marques
2004-12-16 18:48 ` Issue on netconsole vs. Linux kernel oops Park Lee
2004-12-16 18:55 ` Matt Mackall
2004-12-16 19:06 ` linux-os
2004-12-16 19:31 ` Park Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041218074137.GA28322@waste.org \
--to=mpm@selenic.com \
--cc=ipsec-tools-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=parklee_sel@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.