I''ve tried with iproute and it works now !
commands for A:
ip tunnel add mode ipip tunl1 local IP_A remote IP_B
ip addr add dev net1 local virtual-IP_A remote virtual-IP_B
ip link set net1 up
Same on B.
And then from A i''m able to ping virtual-IP_B.
It seems one can not use tunl0 as a tunnel name, is it true ?
I think it will be a good thing to add to the section 5.2 of the LARTC HowTo
the
way to do a tunnel with the ''ip'' commands and to specify that
new_tunnel.o is
only in old kernel. But that''s perhaps already in a TODO list...
Francois
> fechanti@ens-lyon.fr wrote:
>
> here is the config:
> (i cut the 192.168. part of IP addr)
>
> -----------------A-----------------B-----------------C
> 3.3 5.3 5.4 4.4 4.1
>
> on A:
> ifconfig tunl0 192.168.3.3 pointopoint 192.168.5.4
> route add -net 192.168.4.0 netmask 255.255.255.0 dev tunl0
> on B:
> ifconfig tunl0 192.168.4.4 pointopoint 192.168.5.3
> route add -net 192.168.3.0 netmask 255.255.255.0 dev tunl0
>
> From A i can''t ping C. Traceroute shows that packets
doesn''t even reach
> B.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: lartc.org