hi,
On Fri, Apr 26, 2002 at 01:08:59PM +0200, Gert Doering wrote:
> Soooo... any hints?
Additional info: CCO claims "it will just work" (since 12.0T).
I assumed that the problem has to do with "access-list 170" excluding
the packets generated by the router itself, and added:
access-list 170 permit ip any any
and now I get:
49w5d: %PIM-6-REG_ENCAP_INVALID: Bad register from a.b.c.d for (172.30.1.153, 224.2.188.149); additional info = 45000080 8BB24000 7E11266B 8B 2D043CC 2D043B0 0 0
huh?
The session itself is now shown (on the NAT router) as:
(172.30.1.153, 224.2.188.149), 00:02:45/00:02:56, flags: PCFT
Incoming interface: Ethernet0, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null
but never leaves that status, and isn't seen on the RP anymore.
My next try will be ("TAC answer") to upgrade to 12.1(14) and see whether
this will cure the problem. 12.2(x) isn't possible due to flash memory
constraints.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:42 EDT