From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "bert hubert" <ahu@ds9a.nl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: How to debug very strange packet delivery problem?
Date: Fri, 4 Jan 2002 22:20:47 -0700 [thread overview]
Message-ID: <00c601c195a8$bb5c7e90$6caaa8c0@kevin> (raw)
In-Reply-To: <005001c194d9$b5793c40$6caaa8c0@kevin> <20020105000001.A26152@outpost.ds9a.nl>
I haven't tried an _older_ kernel yet, but did have the same problem on
2.4.17 and 2.4.17-rc1. I'll try something older tomorrow and see what
happens.
----- Original Message -----
From: "bert hubert" <ahu@ds9a.nl>
To: "Kevin P. Fleming" <kevin@labsysgrp.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, January 04, 2002 4:00 PM
Subject: Re: How to debug very strange packet delivery problem?
> On Thu, Jan 03, 2002 at 09:38:50PM -0700, Kevin P. Fleming wrote:
> > I've got a machine that is just driving me nuts here... it's a RedHat
7.2
> > machine, upgraded to a 2.4.17 kernel (no kernel patches, just standard
> > kernel). The machine has an ethernet interface for it's local network,
and a
> > ppp interface (using RedHat's pppd-2.4.1 RPM) to connect it to the
corporate
> > WAN.
>
> Does your problem depend on kernel version?
>
> Regards,
>
> bert
>
> --
> http://www.PowerDNS.com Versatile DNS Software & Services
> http://www.tk the dot in .tk
> Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
> Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
>
>
>
next prev parent reply other threads:[~2002-01-05 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 4:38 How to debug very strange packet delivery problem? Kevin P. Fleming
2002-01-04 23:00 ` bert hubert
2002-01-05 5:20 ` Kevin P. Fleming [this message]
2002-01-05 15:20 ` Mika Liljeberg
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 23:17 Manfred Spraul
2002-01-05 5:21 ` Kevin P. Fleming
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='00c601c195a8$bb5c7e90$6caaa8c0@kevin' \
--to=kevin@labsysgrp.com \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox