From: Geatti (geatti@xxxxxxxx)
Date: Sun Sep 03 2000 - 21:58:03 GMT-3
With AURP there is no address on the interface, if you put them on it
shouldn't. You cannot ping across the aurp tunnel on the router that your
tunnel resides as the outgoing app address will be the exiting interface,
and in the case of AURP it doesn't have one. So everything is working ok for
you David this is normal. Just ping from a router that has a outgoing
AppleTalk address on it and it will work.
You should be able to ping across the tunnel but not to or from the tunnel.
Marco
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
David Hiers
Sent: Sunday, September 03, 2000 6:49 PM
To: ccielab@groupstudy.com
Subject: AURP Tunnel Endpoint Pings
I'm working through the FatKid labs, and I've got some weird behavior on
AURP tunnels.
I've got the tunnel, and it works great. Packets go through it like crazy.
The only problem seems to be that the two routers that form the endpoints
can't ping anything on the other side of the tunnel. I get:
00:08:57: %AT-3-NOSRCADDR: Tunnel0: AppleTalk packet error; no source
address available
To REALLY confuse the issue, things on the other side of the tunnel CAN ping
the router interfaces that can not, in turn, ping back. The ping failures
are asymmetrical. If initiated from anything other than a tunnel endpoint,
they work great.
I've hung all sorts of address on the tunnel interface, and nothing seems to
work.
Is this the expected behavior of AURP, or should I keep beating my head
against the monitor? I can't find any documented limitations that would
cover this problem.
David
#############################################
David Hiers
Gobosh
Formerly Central Design Systems, Inc.
808 NW 3rd Ave, 7th Floor.
Portland, OR 97204
v: 503.205.1401 f: 503.243.6705
dhiers@gobosh.cc
Opinions herein are not necessarily those of
Gobosh.
#############################################
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:52 GMT-3