All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Beers <bbeers@edgeaccess.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: two WANs one LAN
Date: Tue, 20 Apr 2004 13:42:17 +0000	[thread overview]
Message-ID: <408528B9.3070209@edgeaccess.net> (raw)



Bob Beers wrote:

> But I've done something wrong, obviously(?).
> 
> I suspect a typo or other oversight, but haven't found it yet.
> 


Ok, after re-checking the cabling ( <- error here), and
  re-checking the commands (verbatim from the nano.txt) it does work!
  (in my static ethernet setup).  Great stuff!

Will it be the same when I introduce the dynamic ppp0 for IFE1?
The IPE1 will be a NAT'd public IP, but the GWE1 will be
  the P-t-P link.

Also, what steps can be taken to expedite the detection and
  route adjustment?
Is it enough to decrease the sleep time in the ping_daemon?
Are there some /proc/sys/.../whatever that can/should be tweaked?

Thanks for any help.

-- 
Bob Beers


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

             reply	other threads:[~2004-04-20 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 13:42 Bob Beers [this message]
2004-04-21  3:25 ` [LARTC] Re: two WANs one LAN gypsy

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=408528B9.3070209@edgeaccess.net \
    --to=bbeers@edgeaccess.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.