I then tried the IPv4 Firewall tab on the Desktop of each system within the group, and while that was very good at stopping access in one direction, it also completely stopped pinging in the other direction too, even if I allowed ping access from the sender IP address group on the receiving system.ĭoes anyone know what my issue might be? And what should I do in order to rectify it (should I use access lists or IPv4 Firewall?)? Any help would be much appreciated I've integrated my Cisco Packet Tracer file within a zip folder to give you some idea of what I'm working with here. This means that R2 will use the IP address of the Fa0/1 interface (10.0.0.1) as the source IP address for the ping packets sent to 10.0.0.2 (R1). I initially tried doing this using access lists on the Master Router, but that did not work at all packets were still able to ping in both directions even when I added the access list to a particular interface. By default, routers choose the IP address of the outgoing interface as the source IP address for ping echo packets. (So for instance, in my network, I need for the group of systems with IP address 192.168.102.0 to be blocked from accessing the group of systems with IP address 192.168.101.0, but not vice versa 192.168.101.0 must still be able to ping 192.168.102.0, but 192.168.102.0 must not be able to ping 192.168.101.0). (So for instance, in my network, I need for the group of systems with IP address 192.168.102.0 to be blocked from accessing the group of systems with IP address 192.168.101.0, but not vice versa 192.168.101.0 must still be able to ping 192.168.102.0. I agree that the primary purpose for a loopback is to create an interface that is not tied to a physical link. In my network, I need to be able to deny ping access from one direction, but not the other. its like duplicate address we need to ping particular network. In my network, I need to be able to deny ping access from one direction, but not the other. loopback is use for testing purpose its a cisco catalyst the loopback address is 127.0.0.0. Sorry to bother you all, but I'm having some issues with a network I'm building in Cisco Packet Tracer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |