Open xyzzklk opened 3 days ago
Router configurations are correct. I copied and pasted yours and it works as expected, but I'm on a local GNS3 server on Linux.
Router configurations are correct. I copied and pasted yours and it works as expected, but I'm on a local GNS3 server on Linux.
Interesting. Mine works as well right after configuration, but after about 5 minutes, their communication starts to corrupt.
The reason I discovered this was that I left my computer running for some time and then went back to check. By the way, it was running, not sleeping or locked.
No problems also after a few hours or resuming from suspension. Maybe you can try if something changes running the GNS3 VM on a different hypervisor or using a remote Linux server.
Describe the bug First I configured RIPv2 on three Cisco IOSv15.9(3)M6 routers that are connected to each other. After some time, they cannot receive each other's RIP update request. They also cannot ping each other, and I can't even start a packet capture to see what's going on.
Because I can't even start a packet capture, I suspect this is a problem of GNS3.
GNS3 version and operating system:
To Reproduce Steps to reproduce the behavior:
and use the
network
command to add the interfaces that should have RIP activated on.Routing Protocol is "application" Sending updates every 0 seconds Invalid after 0 seconds, hold down 0, flushed after 0 Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Maximum path: 32 Routing for Networks: Routing Information Sources: Gateway Distance Last Update Distance: (default is 4)
Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 17 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain GigabitEthernet0/0 2 2 No none Interface Send Recv Triggered RIP Key-chain Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 192.168.1.0 Routing Information Sources: Gateway Distance Last Update 192.168.1.2 120 02:37:39 Distance: (default is 120) R1#
R2#sh ip int br Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.168.2.1 YES manual up up GigabitEthernet0/1 192.168.1.2 YES manual up up GigabitEthernet0/2 unassigned YES unset administratively down down GigabitEthernet0/3 unassigned YES unset administratively down down R2#sh ip protocol IP Routing is NSF aware
Routing Protocol is "application" Sending updates every 0 seconds Invalid after 0 seconds, hold down 0, flushed after 0 Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Maximum path: 32 Routing for Networks: Routing Information Sources: Gateway Distance Last Update Distance: (default is 4)
Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 9 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain GigabitEthernet0/0 2 2 No none Interface Send Recv Triggered RIP Key-chain GigabitEthernet0/1 2 2 No none Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 192.168.1.0 192.168.2.0 Routing Information Sources: Gateway Distance Last Update Distance: (default is 120)
R2#
R3#show ip int br Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 unassigned YES unset administratively down down GigabitEthernet0/1 192.168.2.2 YES manual up up GigabitEthernet0/2 unassigned YES unset administratively down down GigabitEthernet0/3 unassigned YES unset administratively down down R3#show ip proto IP Routing is NSF aware
Routing Protocol is "application" Sending updates every 0 seconds Invalid after 0 seconds, hold down 0, flushed after 0 Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Maximum path: 32 Routing for Networks: Routing Information Sources: Gateway Distance Last Update Distance: (default is 4)
Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 2 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain GigabitEthernet0/1 2 2 No none Interface Send Recv Triggered RIP Key-chain Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: 192.168.2.0 Routing Information Sources: Gateway Distance Last Update 192.168.2.1 120 02:40:33 Distance: (default is 120)
R3# Oct 4 01:48:10.636: RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/1 (192.168.2.2) Oct 4 01:48:10.637: RIP: build update entries - suppressing null update
R3#ping 192.168.2.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) R3#
(Somehow I accidentally restarted R2 and forgot to save the running config, but I configured it again, so things might be a little bit different than what was originally)