All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darryl Miles <lartc-list@the-morg.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] track tunnel connections
Date: Sat, 06 Dec 2003 02:06:07 +0000	[thread overview]
Message-ID: <marc-lartc-107067701703440@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107065669616779@msgid-missing>

petrch@regnet.cz wrote:

>I have this:
>
>publicIP(server)-netA--internet(netC)--netB--172.26.3.0/24
>
>I have tunnel between netA and netB. The tunnel is
>for manage some network devices what are using
>private IP from network 172.26.3.0/24.
>Now if I ping from publicIP (it could be server
>with nagios). Echo request
>packet is routed through tunnel and reaches 172.26.3.1(device)
>but echo reply is routed via default route on netB gateway
>and NATed out to internet.
>
>Question: Could I somehow discover that echo request traveled
>by tunnel so reply should take same way?
>  
>

What tunneling technology are you using (IPIP, GRE, VPN 
(ESP/AH/PPTP/...) ) ?  

Normally you'd configure the tunnel endpoint routers at both sites to 
have recipriocal routing entries for each others subnet.  Also configure 
on the endpoint hosts a black hole routing entry with a higher metric 
than the tunnel, so that "Network Unreachables" are correctly returned 
in the event the tunnel is not configured / down.  This is also one 
measure you can use to stop tunneled data from accidentally escaping 
onto the Internet.

But your subnets need to be correctly configured around the endpoint 
router so no discovery of the route is necessary by the hosts on the subnet.


So I ask: Does your network topology really need to be able to discover 
tunnel(s) ?   Routing protocols exist for this very application, but 
they generally are to allow two routers to discover each others routes, 
not for hosts to discover routes.  Its not clear if the issue of route 
discovery is really your problem or just the subnets aren't configured 
correctly ?


Darryl


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

  reply	other threads:[~2003-12-06  2:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 20:30 [LARTC] track tunnel connections petrch
2003-12-06  2:06 ` Darryl Miles [this message]
2003-12-06  8:30 ` petrch
2003-12-06 18:29 ` Darryl Miles

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-107067701703440@msgid-missing \
    --to=lartc-list@the-morg.org \
    --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.