From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] gre tunnel question again
Date: Fri, 17 May 2002 07:16:25 +0000 [thread overview]
Message-ID: <marc-lartc-102161984802567@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102161000829774@msgid-missing>
On Thu, 16 May 2002, Vikas B. Wadhwani wrote:
> This question adds on to the GRE tunnel query that I
> asked earlier.
>
> For the GRE tunnel to work, do I need to configure
> tunnels in both directions.
You need to configure the tunnel on both endpoints, as both
endpoints have to cooperate to provide the tunnel.
So, if you have machine A with IP address 172.16.8.1 and machine B with IP
address 172.16.16.1 then you would for example use
ip tunnel add abtun mode gre remote 172.16.16.1 local 172.16.8.1
ip addr add 192.168.0.1 peer 192.168.0.2 dev abtun
ip link set abtun up
on machine A and
ip tunnel add abtun mode gre remote 172.16.8.1 local 172.16.16.1
ip addr add 192.168.0.2 peer 192.168.0.1 dev abtun
ip link set abtun up
on machine B to get the tunnel up and running. Then you should be able to
ping the endpoints on the other side, if the GRE encapsulated packets are
not being firewalled somewhere along the way.
Note that routing is at another level in the protocol stack.
Doei, Arthur.
--
/\ / | arthurvl@sci.kun.nl | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-17 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 4:32 [LARTC] gre tunnel question again Vikas B. Wadhwani
2002-05-17 7:16 ` Arthur van Leeuwen [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-102161984802567@msgid-missing \
--to=arthurvl@sci.kun.nl \
--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