From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Ian Latter <Ian.Latter@mq.edu.au>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Re:RPC patch creates kernel panic
Date: Thu, 01 Apr 2004 17:30:06 -0500 [thread overview]
Message-ID: <1080858606.6759.18.camel@localhost> (raw)
In-Reply-To: <200404012334.i31NYv510767@singularity.tronunltd.com>
I'll have to see what I can dig up. I recall there is a very extensive
document on how Microsoft makes use of DCE somewhere on their public
archives.
Regarding my kernel panics, they were all very simple; they occurred on
boot! As soon as I remove RPC from the kernel, I can boot again - John
On Thu, 2004-04-01 at 18:34, Ian Latter wrote:
> Hello John,
>
>
> Thank you for this report.
>
> The RPC conntrack helper was written to support ONC RPC -
> typically used on Unix hosts - where as Windows uses DCE RPC.
> When I last looked at that module, I tried to find technical
> information on the differences of the two, and was unable to
> find any - but had the impression from what I could find that the
> two weren't compatible.
>
> Whether or not the module recieves valid/invalid traffic, it shouldn't
> crash - and I want to fix that.
>
> However, if you have access to documentation on DCE RPC
> protocol/standards then please forward that/them through, as any
> such documentation would be useful for broadening support.
>
> On the report details; what was typically on both sides of the
> filtering engine (Windows 2000 Server on the server side and
> Windows XP Pro on the client side?) and do you have any idea
> what type of activity was performed at the time of the crash?
> (Ie, is there any way that I can repeat the fault directly?)
>
>
>
> Thanks again for your time and info, John.
>
>
>
>
>
> ----- Original Message -----
> >From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
> >To: <netfilter-devel@lists.netfilter.org>
> >Subject: RPC patch creates kernel panic
> >Date: Thu, 01 Apr 2004 16:03:11 -0500
> >
> > I would imagine the RPC patch developers are well aware of this but I
> > have consistently generated kernel panics when using the RPC patch.
> > This was the case using RedHat with several different kernels > 2.4.18
> > and patch-o-matic-20030107 (I believe).
> >
> > I thought I would give patch-o-matic-20031219 a try on SUSE with kernel
> > 2.4.25 from kernel.org patched with StrongSWAN 2.0.1 (FreeS/WAN
> > successor) to see if it behaved any better. Alas, the same problem.
> >
> > We have neither the skills nor time to contribute code to this patch but
> > it is important for us especially for our support of Microsoft shops
> > with their pervasive use of services spawned off of the port mapper on
> > 135/tcp. If there is anything we can do to help outside of development
> > such as testing, please let us know - John
> > --
> > John A. Sullivan III
> > Chief Technology Officer
> > Nexus Management
> > +1 207-985-7880
> > john.sullivan@nexusmgmt.com
> > ---
> > If you are interested in helping to develop a GPL enterprise class
> > VPN/Firewall/Security device management console, please visit
> > http://iscs.sourceforge.net
> >
> >
> >
>
> --
> Ian Latter
> Internet and Networking Security Officer
> Macquarie University
--
Open Source Development Corporation
Financially Sustainable open source development
http://www.opensourcedevelopmentcorp.com
next prev parent reply other threads:[~2004-04-01 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 23:34 Re:RPC patch creates kernel panic Ian Latter
2004-04-01 22:30 ` John A. Sullivan III [this message]
2004-04-01 23:20 ` John A. Sullivan III
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 23:51 Ian Latter
2004-04-02 0:49 Ian Latter
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=1080858606.6759.18.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=Ian.Latter@mq.edu.au \
--cc=netfilter-devel@lists.netfilter.org \
/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.