Hi Rene,
I have been trying to test the RIP load balancing with an ACL and seems like the source router is choosing one path although there is two same metric paths.
in this lab, R3 is choosing always the path trough R1 (90.0.0.2) instead of share the traffic with R2 (80.0.0.2). Do you know why?
For your information this is a GNS3 lab.
R3#sh ip route 4.4.4.4
Routing entry for 4.4.4.4/32
Known via “rip”, distance 120, metric 2
Redistributing via rip
Last update from 90.0.0.2 on GigabitEthernet1/0, 00:00:07 ago
Routing Descriptor Blocks:
90.0.0.2, from 90.0.0.2, 00:00:07 ago, via GigabitEthernet1/0
Route metric is 2, traffic share count is 1
(*) 80.0.0.2, from 80.0.0.2, 00:00:12 ago, via FastEthernet0/0
Route metric is 2, traffic share count is 1
This is the ACL result:
3.3.3.3 → R3
4.4.4.4 → Remote destination
R1#sh ip access-lists
Extended IP access list 100
10 permit icmp host 3.3.3.3 host 4.4.4.4 (1015 matches)
20 permit ip any any (174 matches)
R2#sh access-lists
Extended IP access list 100
10 permit icmp host 3.3.3.3 host 4.4.4.4
20 permit ip any any (31 matches)