All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David A. Bandel" <david@pananix.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Tunnel problem
Date: Sun, 18 Mar 2001 02:23:35 +0000	[thread overview]
Message-ID: <marc-lartc-98488235413926@msgid-missing> (raw)

Ladies and Gentlemen (and others ;-) ),

I recently opened an office in a new location and moved part of the
network with me.  Because it takes so long to get some services
installed (frame relay), I am using a connection from another ISP. 
However, for the short time I'll be on that ISP, I don't want to change
all the DNS back and forth.  So I've built a gre tunnel based on the
information in the HOW-TO.  Here's where I run into a problem.

Main network:
209.127/16

relocated network:
209.127.112.0/25

Everything works great as far as tunneling traffic from the main network
to the relocated network.  Unfortunately, the relocated network is
connected to 200.46/16.  What I need is to tunnel the default gateway
back through the main network.  Reason: some connections realize that
traffic coming from my relocate network is coming via an invalid route
and is filtered.

I've tried everything I can think of to tunnel 0/0 back to the main
network, but to no avail.  The command:
ip route add 0/0 dev netmain
fails miserably.

Any suggestions on how to tunnel the default route?

Thanx,

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/

             reply	other threads:[~2001-03-18  2:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-18  2:23 David A. Bandel [this message]
2001-03-18  2:41 ` [LARTC] Tunnel problem Guy Van Den Bergh
2001-03-18 15:03 ` Guy Van Den Bergh
2001-03-18 20:17 ` David A. Bandel
2001-03-19  0:04 ` Guy Van Den Bergh

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-98488235413926@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 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.