iproute tunnel link problems

From: Chris Hellberg (odysseus@soa.co.nz)
Date: Sun Aug 25 2002 - 19:29:14 EST


Hi,

I've been using 'ip tunnel' from the iproute Debian package to create GRE
tunnels. The following is an example:

ip tunnel add tunnel1 mode gre remote xxx.xxx.xxx.xxx local xxx.xxx.xxx.xx
ip link set up tunnel1
ip link set tunnel1 multicast on
ip address add 192.168.102.6/30 dev tunnel1

ip addr gives me a tunnel of the following:

79: tunnel1@NONE: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1476 qdisc noqueue
    link/gre xxx.xxx.xxx.xxx peer xxx.xxx.xxx.xxx
    inet 192.168.102.6/30 scope global tunnel1

The problem is when running pimd and trying to establish neighbourships
across the tunnel fails as pimd thinks 192.168.102.5 isn't directly
connected:

20:39:10.359 Ignoring PIM_HELLO from non-neighbor router 192.168.102.5

However, if I issue the command:

ifconfig tunnel1 dstaddr 192.168.102.5

which specifies the other end of the tunnel, giving an output from ip
addr to be:

79: tunnel1@NONE: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1476 qdisc noqueue
    link/gre xxx.xxx.xxx.xxx peer xxx.xxx.xxx.xxx
    inet 192.168.102.6 peer 192.168.102.5/30 scope global tunnel1

I can't seem to find an equivalent dstaddr command in the iproute set of
tools. Is there such a command, or a similar way to do this?

Cheers,

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html



This archive was generated by hypermail 2b29 : Sat Aug 31 2002 - 22:00:01 EST