Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "David A. Bandel" <david@pananix.com>
To: lartc@vger.kernel.org
Subject: Re: [Fwd: Re: [LARTC] Tunnel problem]
Date: Fri, 30 Mar 2001 12:23:25 +0000	[thread overview]
Message-ID: <marc-lartc-98596350622501@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98491757823136@msgid-missing>

bert hubert wrote:
> 
> On Sun, Mar 18, 2001 at 07:11:58AM -0500, David A. Bandel wrote:
> > Ooops.  Forgot to check the addresses and send back to the list :-(
> >
> >
> > Guy Van Den Bergh wrote:
> > >
> > > Have you tried to set a default route to the IP address of the tunnel
> > > interface at the main network:
> > > ip route add default via a.b.c.d
> > > where a.b.c.d is the IP address you gave to the tunnel interface at the
> > > main network end.
> >
> > RTNETLINK answers: Network is unreachable
> >
> > This is the same answer when I try to set the default route via the
> > tunnel name.
> 
> Has this problem been solved yet?

Unfortunately, no.  Fortunately, only a very few sites are affected by
the disparate route problem (and the RFCs provide that packets may not
return by the same route).  I'm just waiting for a frame relay line and
I'll close the tunnel, but I was hoping for a solution to this in the
meantime.

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto

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

      parent reply	other threads:[~2001-03-30 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-18 12:11 [Fwd: Re: [LARTC] Tunnel problem] David A. Bandel
2001-03-24 21:43 ` bert hubert
2001-03-30 12:23 ` David A. Bandel [this message]

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-98596350622501@msgid-missing \
    --to=david@pananix.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