mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: christophe.leroy5@capway.com
To: Patrick Kursawe <kursawe@zaphod.anachem.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: ipip tunnel - route complains!
Date: Wed, 23 Dec 1998 16:33:54 +0100	[thread overview]
Message-ID: <199812231531.QAA17905@wanadoo.fr> (raw)

>Hi,

>it looks like I can't get ipip tunneling to work. I use kernel 2.1.131 >and
>net-tools 1.49. I asked for help a few days ago and someone told >me to
>upgrade to the newest net-tools. Done. Still the same problem:


>Short version of what I tried:

>ifconfig tunl0 192.168.1.44 netmask 255.255.255.255 up
>route add -net 192.168.1.0 netmask 255.255.255.0 gw >134.147.2.1 dev tunl0
>SIOCADDRT: Network is unreachable

One solution to get it work quite correctly with nothing else:
route add -host 134.147.2.1 gw your_router
ifconfig tunl0 192.168.1.44 netmask 255.255.255.255 pointopoint 
134.147.2.1
route add -net 192.168.1.0 netmask 255.255.255.0 gw 134.147.2.1 
tunl0

as 134.147.2.1 has been declared pointopoint, it can be a gateway
as you have a host route via eth0 before route via tunl0 it works.
So this solution works, but is not the good one.

Second solution is:
 
- Get iproute2 package from ftp.inr.ac.ru/ip-routing
- Do on each side:
       ip tunnel add tunl1 mode ipip local your_eth0_ip remote 
rmt_eth0_ip
       ifconfig tunl1 this_side_tunnel_ip
 
dont know why, it doesnt work with tunl0

Both solutions works, the last one is hower the good one, 

christophe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~1998-12-23 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199812231531.QAA17905@wanadoo.fr \
    --to=christophe.leroy5@capway.com \
    --cc=kursawe@zaphod.anachem.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.rutgers.edu \
    /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

all inboxes | Powered by JetHome®