Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Diogo Nuno P. Gomes" <dgomes@av.it.pt>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Redundant Internet connections [Updated]
Date: Wed, 15 Oct 2003 17:41:32 +0000	[thread overview]
Message-ID: <marc-lartc-106629479112431@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106606308103921@msgid-missing>

Why not google for it ;) ?

First hit should take you here -> http://www.scyld.com/diag/

Check you linux distribution, most of then come with mii-tools package
already.

=Diogo Gomes
email: dgomes@av.it.pt
homepage: http://sweet.ua.pt/~etdgomes
Eng. Computadores e Telematica - Instituto Telecomunicacoes (Aveiro)


-----Original Message-----
From: Seth J. Blank [mailto:sblank@cms-forex.com]
Sent: quarta-feira, 15 de Outubro de 2003 18:28
To: dgomes@av.it.pt
Subject: Re: [LARTC] Redundant Internet connections [Updated]


I'm not aware of mii tools, could you give me more information on them?

Thanks a lot,
Seth

Diogo Nuno P. Gomes wrote:

>Hi!
>
>This might seam of topic but why don't you use mii tools to ifdown eth0
>if the cord is unplugged ?
>
>=Diogo Gomes
>email: dgomes@av.it.pt
>homepage: http://sweet.ua.pt/~etdgomes
>Eng. Computadores e Telematica - Instituto Telecomunicacoes (Aveiro)
>
>
>-----Original Message-----
>From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
>On Behalf Of Seth J. Blank
>Sent: quarta-feira, 15 de Outubro de 2003 17:48
>To: lartc@mailman.ds9a.nl
>Subject: Re: [LARTC] Redundant Internet connections [Updated]
>
>
>Another weird piece of information to add.
>
>If I ifdown eth0, everything starts being routed over eth1. But if I
>just yank the cord out of eth0, the system sits there trying to route
>over eth0. This persists for much longer than the 60 seconds it should
>take, max, for the kernel to update the routing tables.
>
>And it's still confusing me why the traffic isn't being split evenly
>between eth0 and eth1 (iptraf shows everything going over eth0, no
>traffic at all on eth1).
>
>Thank you all so much for your help,
>Seth
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
>




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

  parent reply	other threads:[~2003-10-15 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 16:24 [LARTC] Redundant Internet connections [Updated] Seth J. Blank
2003-10-13 17:58 ` Robert Kurjata
2003-10-14 16:56 ` Seth J. Blank
2003-10-15  1:27 ` gypsy
2003-10-15 16:12 ` Seth J. Blank
2003-10-15 16:47 ` Seth J. Blank
2003-10-15 17:41 ` Diogo Nuno P. Gomes [this message]
2003-10-15 22:01 ` Seth J. Blank

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-106629479112431@msgid-missing \
    --to=dgomes@av.it.pt \
    --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