Our network admin told me to create a lo:0 to that address to create a VIP to be balanced by the network load balancer.
That is why lo:0 is there... Thanks! Regards, Massimiliano Ziccardi On Mon, Nov 7, 2011 at 15:01, Michael Schreckenbauer <[email protected]> wrote: > Am Montag, 7. November 2011, 14:35:46 schrieb Massimiliano Ziccardi: > > > seems to be a really tricky one... > > > What does > > > tracepath 195.75.145.33 > > > give? > > > > Here is the output: > > > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu > > 16436 > > 1: 195.75.145.33 (195.75.145.33) 0.039ms > reached > > 1: 195.75.145.33 (195.75.145.33) 0.028ms > reached > > > > I tried shutting down localhost with: > > > > ifconfig lo down. > > > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx > > addresses). > > > > And now tracepath gives: > > > > 1: send failed > > Resume: pmtu 65535 > > > > So, for some reason, seems it always uses the 'lo' device... > > > > Any idea? > > I noticed lo:0 is on the same net and has the same netmask as eth0. > Where does lo:0 come from? Is it needed? > I have no idea, if this is the problem or even related, just wondering. > > > Regards, > > Massimiliano > > Best, > Michael > > >
