From: routing <route@irax.com>
To: lartc@vger.kernel.org
Subject: [LARTC] routing question
Date: Mon, 01 Nov 2004 14:51:48 +0000 [thread overview]
Message-ID: <41864D84.1030501@irax.com> (raw)
In-Reply-To: <marc-lartc-105489071823469@msgid-missing>
So far I have been used to using linux to provide simple routing from my
network to others using commands such as ip route add 192.168.1.0/24 via
192.168.0.4 etc and it has all worked perfectly.
I also use smoothwall GPL to provice vpn services, however I have hit on
a problem and am not at all clear on the way in which to proceed.
I now need to provide a route to services, the access to these is
provided by a router on a network on the far end of a VPN. the
computers on the remote network can see the service I need to access,
however when I try to provice a route to that system using a router on
the remoted network by issuing a command such as 192.168.5.0/24 via
192.168.15.6 in the router at 192.168.0.4 I get the following :-
RTNETLINK answers: Network is unreachable.
My question is , what way of providing access to this route do I need to
follow, Is it GRE tunnels (not the best option as I don't have enough
information on the remote router configurations and am not able to
change their settings). Do I have to use new routing tables or is
there something else I must do to get this working?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-01 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 9:07 [LARTC] Routing question Alex Schaft
2003-06-06 9:23 ` Leigh Waldie
2003-06-06 10:08 ` Leigh Waldie
2004-11-01 14:51 ` routing [this message]
2004-11-01 16:16 ` [LARTC] routing question routing
2004-11-01 17:18 ` Rene Gallati
2006-09-05 19:08 ` [LARTC] Routing question John Fulton
2006-09-07 6:42 ` Leigh Sharpe
2007-04-05 16:58 ` [LARTC] Routing Question Fernando Blankleder
2007-04-06 19:56 ` Fw: " Fernando Blankleder
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=41864D84.1030501@irax.com \
--to=route@irax.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.