All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Rogers <jrog@sunbeach.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Shaping on multiple interfaces results in losing the box
Date: Thu, 09 Jan 2003 14:45:16 +0000	[thread overview]
Message-ID: <marc-lartc-104212362110035@msgid-missing> (raw)

Hi, I'm using the latest HTB patch on a custom 2.4.18 kernel. The
kernels either include freeswan 1.98b or super-freeswan 1.99.

When i attempt to shape on 1 interface .... no problem. I can do this to
any interface on the linux box including.

The minute I add the second set of shaping commands to another ethernet
interface I lose the box.

I normally set the box to reboot in a certain time when i'm running
these scripts however the box does not reboot and is rendered
unaccessible unless I'm on site.

I also as a precaution allow the script to sleep for a period of time
after which it clears the shaping from the interfaces ... it doesn't
take. 

I recently tried this in house on 2 test systems. However using kernel
2.4.20 with HTB etc enabled and installed super-freeswan 1.99 as
packaged by Ken Bantoft. As with the machines I lost ... freeswan is not
active. I atempted to shape 2 of the 4 interfaces on the machines ... IT
WORKED.

Problem is the machines in the field are currently live. I can't bring
them down until after hours or late on weekends. And I would have no one
there to reset the systems.

Any ideas as to why this is happening and or how to stop this?

-- 
Corey Rogers <jrog@sunbeach.net>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-01-09 14:45 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-104212362110035@msgid-missing \
    --to=jrog@sunbeach.net \
    --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.