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. But, because the network software demands a private network, the loopback device can be used as a pseudo device in the private network that doesn’t really exist.Below I have several updates, things I have tried. Where I have assigned the loopback adapter a network address is when I’ve deployed a multi-homed machine configuration in a colo where there isn’t really a network behind the machine. You can do so, but it still shouldn’t be accessible from a network. Note that what you describe in your original post (and wolfi’s follow up) might work, but is typically misleading and incorrect practice because the loopback device and interface in both Windows and Linux is completely different than the network-capable interface so should not be assigned a LAN address. ![]() When you do this, then webpages are accessible by any one or more addresses you want to assign it (typically 127.0.0.x) but not accessible from the network.Ĭonversely if you bind your actual ethernet adapter (might be eth0 but today more likely a name related to your NIC hardware), then it’s accessible from the network but accessible using localhost or a loopback address. A common example and use (and mistake) is for example to bind your webserver to this loopback address. This loopback adapter should not be assigned any LAN address, because as a loopback adapter, its interface is visible and usable only on the machine itself. To see the properties of all your network adapters, including your loopback (typically called “lo”) run the following command ip addr In Linux, a loopback adapter is created automatically for you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |