Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: James Sneeringer <james+lartc@vincentsystems.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work conservi
Date: Mon, 05 Jul 2004 19:21:34 +0000	[thread overview]
Message-ID: <20040705192134.GA16152@valjean.si.ocslink.com> (raw)
In-Reply-To: <200407051616.i65GGcx94225@smtp.shellnet.co.uk>

On Mon, Jul 05, 2004 at 05:14:20PM +0100, Chris Bolton wrote:
> No I am using the EN5861, just that we have two ADSL lines and only one
> EN5861 and rather than buying another I'd like to use linux to do the same
> job as the en5861, if you know what I mean.

You can, but since you have two ADSL lines, you'll need two ADSL devices of
some kind, whether it's a pair of 5861s, or a 5861 and an ADSL port adapter
(external modem, PCI card, whatever) that Linux supports.

The simplest solution will be to have the same setup for both lines.  Either
use two 5861s, or get two ADSL adapters that Linux can talk to.

> So far I've set up ppp0:0 which I've assigned one of the static ip addresses
> supplied to us by our ISP but when I try and route through it i.e. ip route
> add default dev ppp0:0 table T1 then it returns the error no such device,
> which it's quite right there isn't.  If I route through it using the ip
> address of ppp0:0 i.e ip route add default via x.x.x.193 table T1 then it
> does work but anything that goes through it ends up using the IP address of
> ppp0.

So both lines were supplied by the same ISP?

> So how can I set up the linux box to use these static IP addresses in the
> same way I can with the EN5861?

If you want to remove the 5861 from the picture entirely, you'll need to
replace it with some sort of ADSL adapter.  You can't just plug a DSL line
into an ethernet card.

> I hope I'd made myself clear, it's hard trying to explain something when
> your not to sure exactly what your talking about.  Anyway any help with be
> gladly received.

It would help if you could draw a diagram of your network so we could get a
better idea of what yo're trying to do.

-James

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

  reply	other threads:[~2004-07-05 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 16:14 [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work conserving ? Chris Bolton
2004-07-05 19:21 ` James Sneeringer [this message]
2004-07-06  7:22 ` FW: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work conservi Chris Bolton
2004-07-06 10:33 ` FW: [LARTC] Static ip addresses/aliases previously (my mistake) Ed Wildgoose
2004-07-06 12:54 ` FW: FW: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work cons Chris Bolton
2004-07-06 15:07 ` FW: FW: [LARTC] Static ip addresses/aliases previously (my mistake) Ed Wildgoose
2004-07-06 15:52 ` FW: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work cons James Sneeringer
2004-07-06 16:15 ` FW: " Chris Bolton

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=20040705192134.GA16152@valjean.si.ocslink.com \
    --to=james+lartc@vincentsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox