Hi, last message didn't get posted it would appear, just got blank screen, sorry if this is posted twice, but I'm desperate.
I have a tunnel to my ISPs cosine router which is connect to 3 of my other offices as well via tunnels and it is supposed to route traffice between all our offices.
two offices were working ok, but when they added the next two, I can't ping them. I have two access-lists, one that matches packets for the tunnel, one that deny's packets getting NATd that are bound for tunnel. I just added the new private networks to these and figure that should work, but it doesn't looked at them like 1000 times now, retyped them etc, there are not typos. I turned on ip packet debugging and get this when I ping the office that I can get to:
May 17 04:58:45 10.50.254.254 62539: 065137: May 17 04:58:45.707 BST: IP: tableid=0, s=10.50.100.50 (FastEthernet0/1), d=172.26.12.2 (Serial0/0:0), routed via RIB May 17 04:58:45 10.50.254.254 62540: 065138: May 17 04:58:45.707 BST: IP: s=10.50.100.50 (FastEthernet0/1), d=172.26.12.2 (Serial0/0:0), g=172.26.12.2, len 60, forward
when I ping the office I can't get to I get:
May 17 05:03:12 10.50.254.254 63419: 066008: May 17 05:03:12.406 BST: IP: tableid=0, s=10.50.100.50 (FastEthernet0/1), d=172.27.12.1 (Serial0/0:0), routed via RIB
no forward line...
I thought perhaps that is because they haven't setup their end, of my tunnel, to accept for the new private block... could that be? Is there someway I can prove if the packets are going out through my tunnel? actually leaving my router? This has become really urgent now, I'm on vacation and have been working 2am to 6am to fix this and pullying what little of my hair is left out as I can't figure this out and I've tried all manner of debug, if anyone can tell me what the debug above means it would help or any additional debugging I can do,
thanks bill