From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb: class 10007 isn't work conserving ?!
Date: Mon, 05 Jul 2004 15:51:03 +0000 [thread overview]
Message-ID: <40E978E7.6030908@wildgooses.com> (raw)
In-Reply-To: <20040702145856.GE630@mabeys.dsl.aros.net>
>Our ISP has given us 5 static IP address plus one router IP address and I
>was wondering if I could get rid of their stupid EN5861 router and set up
>the linux machine to handle all the static addresses and routing. I figured
>I'd have to set up alises for other IP addresses eg ifconfig eth0:0
>xx.xx.xx.193 but once I've done that I've found out I cant use ip route to
>configure it eg ip route add default dev eth0:0 table server. Whats the
>best way to go about this?
>
>Cheers.
>
>By the way I'm running redhat 9 with two adsl connections, on is a
>speedtouch USB modem and the other is the EN5861 router.
>
>
I'm not quite sure why you tagged this on to the end of a thread about
htb classes? As a result many people may not even read your question...?
I have one of those EN5861 router things, and actually I find it pretty
good. The biggest issue is that it's a bit of a timebomb, the
powersupply dies after a few years, and unless you have a spare it's a
bit of a weak link
Do you need to do some particularly advanced routing that's stopping you
just using the en5861?
Good luck
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-07-05 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 14:58 [LARTC] htb: class 10007 isn't work conserving ?! Glen Mabey
2004-07-05 6:18 ` Catalin BOIE
2004-07-05 14:07 ` Chris Bolton
2004-07-05 14:43 ` Glen Mabey
2004-07-05 15:51 ` Ed Wildgoose [this message]
2004-07-06 5:52 ` Catalin BOIE
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=40E978E7.6030908@wildgooses.com \
--to=lists@wildgooses.com \
--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.