the ipnrs used to build the tunnel should be the real ipnrs.
(A) ifconfig eth0 A.1
(A) route add default gw A.254
(A) ifconfig tunl0 A.1 pointopoint B.1
(A) route add -host 192.168.0.1 tunl0
(B) ifconfig eth0 B.1
(B) route add default gw B.254
(B) ifconfig tunl0 B.1 pointopoint A.1
(B) route add -host 192.168.1.1 tunl0
if you now do a
ping 192.168.0.1
from machine A you should see something like this with tcpdump:
15:35:59.643196 A.1 > 192.168.0.1: icmp: echo request (gre encap)
-----
of course you won't get a reply until you cfg machine B with ip address
192.168.0.1, like:
(B) ifconfig eth0:1 192.168.1.1
Eric.
-----Original Message-----
From: Andreas Jellinghaus
[mailto:[EMAIL PROTECTED]]
Sent: Friday, October 15, 1999 11:50 AM
To: [EMAIL PROTECTED]
Subject: ip tunnel setup ?
two machines A and B with ip addresses A.1 and B.1 and gateways A.254 and
B.254.
both kernel 2.2.12. i thought i could build a tunnel A<-> with the tunnel
ip addreses 192.168.0.1 for A and 192.168.1.1 for B. i tried this config:
(A) ifconfig eth0 A.1
(A) route add default gw A.254
(A) ifconfig tunl0 192.168.0.1
(A) route add -host 192.168.1.1 gw B.1 tunl0
(B) ifconfig eth0 B.1
(B) route add default gw B.254
(B) ifconfig tunl0 192.168.1.1
(B) route add -host 192.168.0.1 gw A.1 tunl0
doesn't work. the route always refuses "network unreachable" ...
what's wrong ?
thanks for your help.
regards, andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
