If using Windows, open the Command Prompt. The Ping command operates virtually identically on all systems. Every operating system has a command line interface that will allow you to run the Ping command. To solve this: announce your l0 from R2 into BGP. The good thing is that when you run Loopback Ping, your PC tests itself to ascertain that it is working correctly. ![]() You can see this by starting a debug on AS100: debug ip icmp and send the ping from R2. When AS 100 tries to send you the ICMP reply, the router is not finding any route and will drop the icmp reply. 2461 -> 208.91.112.68.443: syn 1102060009įor any other service using the loopback as source it is working perfect. To test network connectivity with ping: Open the Command Prompt or Terminal. If you ping in this way: R-2ping 100.100.100.100, your source IP address will be 12.12.12.2. When you ping 10.0.3. ![]() ![]() The outgoing interface (in my configuration a ipsec vpn) is the same for both (ping and https).įGT60C (root) # diagnose sniffer packet any 'port 443' 4Ģ5.294676 out. There is nothing that can change this behaviour of the loopback interface, thats what it is coded to do. ping statistics - 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 169.6/169.8/170.3 msīut a sniffer for HTTPS traffic results in a source-ip different to the loopback. Yes - the loopback is within management vdom and fortiguard services are reachable via PING.įGT60C (root) # execute ping-options source įGT60C (root) # execute ping PING (208.91.112.198): 56 data bytes 64 bytes from 208.91.112.198: icmp_seq=0 ttl=45 time=169.7 ms 64 bytes from 208.91.112.198: icmp_seq=4 ttl=45 time=169.6 ms
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |