AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Why would you to ping your loopback3/15/2024 I reset the time on 5-2-2015, 7:10pm */Įncrypted-password "$1$.Kw圓nB8$IHVTgcWgqqjRo97tjOorj1" # SECRET-DATAĮncrypted-password "$1$cFcLmPXI$nZC3NQZtv0WztFUTwreaa1" # SECRET-DATAĮncrypted-password "$1$l0Uh4pQW$3VadaIK6OMZ6.eWSN4p6/." # SECRET-DATAĮncrypted-password "$1$zES4Qia2$cw0t/MQzx.7nJu2zcnQcF0" # SECRET-DATA * I am watching the system uptime to see how accuarate the internal clock is. Switch config: (after this is the router run show configuration | no-more This Juniper router is my 7th router so I want the loopback address to be 7.7.7.7)?Īny light shed on this subject is much appreciated! THIS still resulted in not being able to ping this loopback address from the Juniper switch.ĭoes anyone know what is required to set up a Juniper Router with a simple loopback address that matches the physical router in my lab (i.e. I did try to configure the Group Global loopback and it still did not show groups Why is this so mysterious on Juniper? I did searches on the internet and found articles on Group Global loopback configurations, and found people instructing to use a Proxy Arp. When I ping the Cisco lo0 address of 1.1.1.1 I have success. Just like between my switch and my juniper router these two are connected directly from the switch to the router on a direct link. If you notice in my static config above, I have a route to 1.1.1.1 via 10.40.1.1. I have had no problem setting up multiple Cisco routers with a lo0 address and pinging from my Juniper switch. I set up a static route on my switch to point to next-hop of 10.20.1.3 so the switch would know to go to that address to get to 7.7.7.7. I am able to ping from router to switch using the driectly connected address I am able to ping from switch to router using the directly connected address ![]() ON a EX2200-C switch that is connected to this router the following way: I am able to ping this address from the router itself #run ping 7.7.7.7 successful I am trying to set up a J2350 router with a lo0 interface address 7.7.7.7. AT THE VERY BOTTOM OF THIS POST I PUT THE OUTPUT OF THE LOOPBACK ON R8.ītw: came up with a nice command: show interfaces | match "0*|address" :: just shows ge and lo interface names and associated addresses. MAYBE it has something to do with what unit (logical subinterface) I am putting the loopback's address ON? I am using unit 0. MY CONCLUSION, something (aside from opening up complete TRUST zone of all services and all protocols on both routers) is keeping both routers from responding to PINGs to their LOOPBACK interface. but IĬAN'T ping from the switch to the loopback of either router, or from either router to the loopback of the other router. Does anyone out there have experience setting up loopback addresses on routers and being able to ping from other devices in the configured senario? These are all physical devices that I have.ĬAN ping from each router to the loopback of the switch (without even a static route in either router pointing to the loopback's next hop from the router to the switch). I need to get back to my studying and this is taking a very long time. ![]() I am at a point in my studying where I need to be able to ping loopback interfaces on different routers. Thanks in advance to anyone who will take the time to help me.Below I have several updates, things I have tried. Because it's a stateful FW, I normaly don't have to setup a out direction rule, so. I don't know what I'm doing wrong but it's dosen't work. I have setup a rule like that in the WAN Rules section :Įven if I do like that it's not working : I want to use this loopback interface to do many things, but at first I want to ping it from anywhere, and I don't know why, but I can't manahe to do it. From this interface I can ping my gateway and internet (no problem with # ping -S 51.xx.xx.203 1.1.1.1 I have setup correctly an public IP to my Lo1 interface. ![]() I don't know if someone can help me but, I'm facing a problem.
0 Comments
Read More
Leave a Reply. |