From: Jesper Kold-Hansen <candyman@cs.auc.dk>
To: lartc@vger.kernel.org
Subject: [LARTC] BW trottle follow up.
Date: Wed, 08 Jan 2003 11:15:39 +0000 [thread overview]
Message-ID: <marc-lartc-104202460407598@msgid-missing> (raw)
I have seen and resived a few messages where ppl want to know what my
script looks like and routing tables look like.
Well it should be said that the connection refused problems, accures
BEFORE i run the script also. Therefore it must be either a kernel problem
when it get's patched, or something the kernel does og set in eg. the
routing tables.
But I garantee that it is not the script.
Btw. I have also tryed with a 2.4.20 (no patched) kernel. Same problem.
Candyman
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-01-08 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-104202460407598@msgid-missing \
--to=candyman@cs.auc.dk \
--cc=lartc@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 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.