From: Stephen Frost <sfrost@snowman.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Netfilter <netfilter@us5.samba.org>
Subject: Re: test13-pre1 changelog
Date: Thu, 14 Dec 2000 18:56:21 -0500 [thread overview]
Message-ID: <20001214185620.P26953@ns> (raw)
In-Reply-To: <20001214184544.O26953@ns> <E146iAI-0000IA-00@the-village.bc.nu>
In-Reply-To: <E146iAI-0000IA-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 14, 2000 at 11:51:56PM +0000
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> > machine? For no apparent reason after 5 days running 2.4.0test12
> > everything going through my firewall (set up using iptables) I got about
> > 100ms time added on to pings and traceroutes. I'll probably reboot the
> > machine tonight and see if that helps.
>
> Before you do that can you see if ifconfig down, rmmod, insmod, ifconfig up
> fixes it.
This go around I compiled everything into the kernel, actually.
If it would be useful I can compile them as modules reboot and then see
what happens...
===# cat /proc/modules
ppp_deflate 39200 0 (autoclean)
bsd_comp 4160 0 (autoclean)
ppp_async 6512 1 (autoclean)
ppp_generic 15232 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 4528 0 (autoclean) [ppp_generic]
===#
I can say that cleaning out all my firewall rules and adding them
back didn't change behaviour any. Also, I'm sure that this was not happening
until today or maybe yesterday. Earlier in the week the machine was doing
fine and I was getting reasonable response times. Now, out *every* interface,
I get something close to 100ms additional time. Also of note, traceroutes
appear to be more lagged than pings, for what that's worth (traceroute using
udp, ping using icmp, dunno if it makes a difference).
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-12-15 0:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 20:06 test13-pre1 changelog David Riley
2000-12-14 20:11 ` Dr. Kelsey Hudson
2000-12-14 20:39 ` Frank Davis
2000-12-14 20:44 ` Jeff Garzik
2000-12-14 22:16 ` Marty Pitts
2000-12-14 23:31 ` Linus Torvalds
2000-12-14 23:45 ` Stephen Frost
2000-12-14 23:51 ` Alan Cox
2000-12-14 23:56 ` Stephen Frost [this message]
2000-12-15 0:06 ` Linus Torvalds
2000-12-15 0:17 ` Stephen Frost
2000-12-14 23:56 ` Linus Torvalds
2000-12-15 0:10 ` Stephen Frost
2000-12-15 0:20 ` Linus Torvalds
2000-12-15 4:58 ` Oliver Xymoron
2000-12-15 14:30 ` Stephen Frost
2000-12-15 15:09 ` Oliver Xymoron
2000-12-15 8:45 ` Pau
2000-12-15 15:37 ` Tom Rini
2000-12-15 17:10 ` Linus Torvalds
2000-12-15 18:04 ` Alan Cox
2000-12-15 18:08 ` Linus Torvalds
2000-12-15 18:22 ` Alexander Viro
2000-12-15 18:32 ` Alan Cox
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=20001214185620.P26953@ns \
--to=sfrost@snowman.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@us5.samba.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox