![]() PS: I know you can do some tricks to capture traffic and packet sniff through Wireshark, but I'm not after log files of packets. I want to find out if there are any creative workarounds to bridge or route this loopback adapter traffic through some kind of interface that Perfmon CAN monitor.įor example somehow use a TAP Adapter, or some other special type of virtual network driver, or even somehow use an unused physical adapter. RIP: received v2 update from 192.168.1.12 on Serial1ġ92.168.1.128/25 -> 0.0.0.I am getting my internet connection through a Microsoft Loopback Adapter (coming from a Virtualbox), and because of loopback implementation, you can't monitor its traffic via Perfmon or Task Manager. ![]() RIP: received v2 update from 192.168.1.11 on Serial0 RIP: received v2 update from 192.168.1.129 on Ethernet0 RIP: ignored v2 packet from 10.1.1.1 (sourced from one of our addresses) Since I don't have PPP setup, I'm guessing the RIP advertisements are being dropped and routers 2 and 3 simply have nothing to advertise to or receiv from. I have not configured encapsulation or any of that. I am getting the sneaking suspicion that this has everything to do with my serial hub and spoke setup. Routers 2 and 3 which are spokes from R1 are not sending or receiving any RIP updates. It is sending and receiving in version 2. I am however ignoring the advertisement for the loopback on R1. Both are directly connected, but I am not receiving any advertisements from the othe loopbacks. ![]() I ran a debug ip rip on R1 and found that the advertisements are being sent across my serial connections. I have added those statements and still cannot ping. Success rate is 100 percent (5/5), round-trip min/avg/max = 60/66/80 ms Sending 5, 100-byte ICMP Echos to 192.168.1.12, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 36/56/84 ms Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 36/50/64 ms Sending 5, 100-byte ICMP Echos to 192.168.1.9, timeout is 2 seconds: Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds: Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds: Here are the running configs and ip routes for all three routers:Ĭ 192.168.1.8/29 is directly connected, Serial1 It looks like version 2 is enabled on all the routers, and I can ping on the 192 adresses, just not the 10s. Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:Įnable secret 5 $1$0UdW$yy6AD7sKOwdA1EYZPGp0A0 Hints, suggestions and full-on answers are all welcome!Ĭ 10.1.1.0 is directly connected, Loopback0ġ92.168.1.0/24 is variably subnetted, 3 subnets, 3 masksĬ 192.168.1.8/29 is directly connected, Serial1/3Ĭ 192.168.1.0/30 is directly connected, FastEthernet0/0 I know this is something simple that I am just overlooking in my notes, but I need help. I thought at first this was because I wasn't using the no auto-summarization statement, but i have added that and it is still changing the network back to 10.0.0.0. The problem I can't understand at the moment is in my router rip statement: it is changing 10.1.1.0 to 10.0.0.0. All of my ethernet and serial interafces using the 192.168.1.0 spaces are able to ping fine to and from each router. I have added the networks to my router rip satements, networks 192.168.1.0 and 10.1.1.0. I have 3 routers, each connected through ethernet and serial, and each with a loopback interface using a /29 mask and the ips 10.1.1.1-3. Hi, I am having some difficulty understanding a setback I'm experiencing with RIP version 2 advertising and a loopback design.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |