From: papyrus papyruslet@volny.cz
To: lartc@vger.kernel.org
Subject: [LARTC] IP tunneling
Date: Sun, 15 Oct 2000 21:50:02 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216783@msgid-missing> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="iso-8859-1", Size: 2596 bytes --]
Hi,
I have a problem with GRE tunneling. I read Advanced-Routing HOWTO
about this and I did all as is written in this documentation. Even the
same example is here which I need for my project.
I want create (by means of GRE tunneling or IP in IP tunneling) virtual
private network VPN - in first phase without IPsec in other phase with
IPsec.
I have two local networks distant apart with two routers. Both routers
have registered IP addresses (I have only two registered IP addresses and many
computers in local netwoks which I connected to Internet); first router connects
one local network to Internet and second router connects other local network
to Internet. Computers in both networks have the access to Internet over
routers because I configured IP-Masquerade. Now I want solve the access of
computer from my first local network to computers from my second local network.
So I have network
A:
network 192.168.1.0
netmask 255.255.255.0
router 192.168.1.1 (eth1)
router is connected to Internet over eth0 - 145.35.162.44 netmask is /21
and network
B:
network 192.168.2.0
netmask 255.255.255.0
router 192.168.2.1 (eth1)
router is connected to Internet over eth0 - 145.35.160.94 netmask is /21
I wrote this two scripts (I use RedHat 6.1 on both routers with kernel 2.2.12)
file rc.ipip on router A
#!/bin/sh
PATH=/sbin:/usr/sbin
echo installing modul...
modprobe ip_gre
echo setting tunl0...
ip tunnel add neta mode gre remote 145.35.160.94 local 145.35.162.44 ttl 255
echo adding network ariel2...
ip addr add 192.168.1.1 dev neta
ip route add 192.168.2.0/24 dev neta
in file rc.local
.
.
.
/etc/rc.d/rc.ipip
file rc.ipip on router B
#!/bin/sh
PATH=/sbin:/usr/sbin
echo installing modul...
modprobe ip_gre
echo setting tunl0...
ip tunnel add netb mode gre remote 145.35.162.44 local 145.35.160.94 ttl 255
echo adding nework ariel...
ip addr add 192.168.2.1 dev netb
ip route add 192.168.1.0/24 dev netb
in file rc.local
.
.
.
/etc/rc.d/rc.ipip
...it's so easy...but
When I start these scripts the error come:
RTNETLINK answers: Networking is out of work
Where did I make mistake?
---------------------------------------------
And second thing...
When I tried to take in work IP in IP tunneling I didn't know where to find
modul new_tunnel because this modul is'n in my distribution of RedHat. I haven't
problem with modul ipip.
I would be very happy if somebody could help me.
thanks,
Vilem Musil
....sorry for my english
[-- Attachment #2: Type: text/html, Size: 5363 bytes --]
next reply other threads:[~2000-10-15 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-15 21:50 papyrus [this message]
2000-10-15 23:10 ` [LARTC] IP tunneling bert
2005-04-26 10:53 ` [LARTC] IP Tunneling phonic
2005-04-27 5:25 ` Taylor, Grant
2005-04-27 7:38 ` phonic
2005-04-27 8:22 ` Taylor, Grant
2005-04-27 10:45 ` Dan Martin
2005-04-27 10:53 ` phonic
2005-04-27 11:02 ` phonic
2005-04-27 11:13 ` phonic
2005-04-27 18:19 ` Damjan
2005-04-27 18:32 ` phonic
2005-04-28 1:58 ` Taylor, Grant
2005-04-28 11:14 ` Damjan
2005-04-28 16:46 ` Taylor, Grant
2005-04-29 2:22 ` Dan Martin
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-98373938216783@msgid-missing \
--to=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.