problem with the configuration of the 881g

[witek99]

Hello.

I have a problem with the configuration of the 881g. The problem is when i connect by fastetethernet and try ping my tunel i loos 50% of pings but from router the ping is 100% successful. Could someone look at my configuration?

[witek99]

10.250.0.x is one of my corp network. I try connec by lte connection on router new network 10.250.99.x.
I think the tunnel is ok because ping from router looks fine:
LTE_RTR1#ping 10.250.0.1 r 100
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 10.250.0.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 64/76/96 ms

but when i connect computer to FE and try ping (from computer) some address in my corp network, i'm lose at least 50% of ping.
Sytuation look similar when i ping from my corp network when i ping router 10.250.99.1 it looks ok. but when i ping computer 10.250.99.50 (DHCP) i lose ping.

[Georg Pauwen]

Hello,

remove this line from your configuration:

--> no ip nat inside source route-map LOKALNE_WYJ interface Dialer1 overload

and change the order of access list 100:

access-list 100 deny ip 10.250.99.0 0.0.0.255 10.0.0.0 0.255.255.255

access-list 100 permit ip 10.250.99.0 0.0.0.255 any

[witek99]

I made the suggested changes, but everything looks the same.

[witek99]

I just add that, when i ping router 10.250.99.1 from computer (10.250.99.50) connected by FE ping is ok

[Georg Pauwen]

Hello,

can you post the output of 'show ip route' ?

[paul driver]

Hello

Can you amend the eigrp process a little so to advertise classless subnets instead of classful boundaries. Also add a delay metric to tunnel 20 as as present I guess you also have equal paths due to two tunnel eigrp peers and possible asymmetric return traffic.

router eigrp 1

no network 10.0.0.0

no auto-summary

network 10.251.99.2 0.0.0.0

network 10.252.99.2 0.0.0.0

Int  tun20

delay 5000

[witek99]

sh ip route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0

S* 0.0.0.0/0 is directly connected, Tunnel10
44.0.0.0/32 is subnetted, 1 subnets
C 44.44.44.44 is directly connected, Dialer1
10.0.0.0/8 is variably subnetted, 80 subnets, 3 masks
D 10.64.0.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.64.255.0/30 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.0.0/24 [90/26880256] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.4.0/24 [90/26880512] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.7.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.8.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.9.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.10.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.12.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.13.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.14.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.15.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.16.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.17.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.18.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.20.0/24 [90/26880512] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.21.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.22.0/24 [90/26880512] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.26.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.27.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.28.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.33.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.36.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.37.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.38.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.39.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.250.41.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.43.0/24 [90/28162560] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.49.0/24 [90/28160000] via 10.251.99.1, 04:06:10, Tunnel10
D 10.250.50.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.250.90.0/24 [90/26880512] via 10.251.99.1, 04:06:10, Tunnel10
C 10.250.99.0/24 is directly connected, Vlan1
L 10.250.99.1/32 is directly connected, Vlan1
D 10.251.7.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.9.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.10.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.14.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.16.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.17.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.18.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.19.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.21.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.26.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.27.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.28.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.33.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.35.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.37.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.41.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.43.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.49.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
D 10.251.50.0/24 [90/28160000] via 10.251.99.1, 04:06:11, Tunnel10
C 10.251.99.0/24 is directly connected, Tunnel10
L 10.251.99.2/32 is directly connected, Tunnel10
D 10.252.7.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.8.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.9.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.10.0/24 [90/298524672] via 10.251.99.1, 01:02:24, Tunnel10
D 10.252.12.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.13.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.14.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.15.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.16.0/24 [90/298524672] via 10.251.99.1, 01:02:24, Tunnel10
D 10.252.17.0/24 [90/299804416] via 10.251.99.1, 04:06:10, Tunnel10
D 10.252.18.0/24 [90/298524672] via 10.251.99.1, 01:02:24, Tunnel10
D 10.252.19.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.25.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.26.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.33.0/24 [90/299804416] via 10.251.99.1, 04:06:10, Tunnel10
D 10.252.36.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.37.0/24 [90/298524672] via 10.251.99.1, 01:02:24, Tunnel10
D 10.252.38.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.39.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
D 10.252.41.0/24 [90/299804416] via 10.251.99.1, 04:06:10, Tunnel10
D 10.252.43.0/24 [90/299804416] via 10.251.99.1, 04:06:10, Tunnel10
D 10.252.49.0/24 [90/299804416] via 10.251.99.1, 04:06:10, Tunnel10
D 10.252.50.0/24 [90/299804416] via 10.251.99.1, 02:37:28, Tunnel10
D 10.252.90.0/24 [90/298524672] via 10.251.99.1, 01:02:21, Tunnel10
C 10.252.99.0/24 is directly connected, Tunnel20
L 10.252.99.2/32 is directly connected, Tunnel20
11.0.0.0/32 is subnetted, 1 subnets
S 11.11.11.11 is directly connected, Dialer1
22.0.0.0/32 is subnetted, 1 subnets
S 22.22.22.22 is directly connected, Dialer1
33.0.0.0/24 is subnetted, 1 subnets
S 33.33.33.33 is directly connected, Dialer1


After last suggestion also no change.

[paul driver]

Hello

sh ip eigrp topology x.x.x.x
sh ip cef (source address) (destination address)

Note: You have a default static route pointing to the tunnel10, meaning you will need more specific routes in your rib rib table if you want to reach certain destinations over the other tunnel or physical interfaces.