| 1 |
Am Montag, 7. November 2011, 14:35:46 schrieb Massimiliano Ziccardi: |
| 2 |
> > seems to be a really tricky one... |
| 3 |
> > What does |
| 4 |
> > tracepath 195.75.145.33 |
| 5 |
> > give? |
| 6 |
> |
| 7 |
> Here is the output: |
| 8 |
> |
| 9 |
> 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu |
| 10 |
> 16436 |
| 11 |
> 1: 195.75.145.33 (195.75.145.33) 0.039ms reached |
| 12 |
> 1: 195.75.145.33 (195.75.145.33) 0.028ms reached |
| 13 |
> |
| 14 |
> I tried shutting down localhost with: |
| 15 |
> |
| 16 |
> ifconfig lo down. |
| 17 |
> |
| 18 |
> Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx |
| 19 |
> addresses). |
| 20 |
> |
| 21 |
> And now tracepath gives: |
| 22 |
> |
| 23 |
> 1: send failed |
| 24 |
> Resume: pmtu 65535 |
| 25 |
> |
| 26 |
> So, for some reason, seems it always uses the 'lo' device... |
| 27 |
> |
| 28 |
> Any idea? |
| 29 |
|
| 30 |
I noticed lo:0 is on the same net and has the same netmask as eth0. |
| 31 |
Where does lo:0 come from? Is it needed? |
| 32 |
I have no idea, if this is the problem or even related, just wondering. |
| 33 |
|
| 34 |
> Regards, |
| 35 |
> Massimiliano |
| 36 |
|
| 37 |
Best, |
| 38 |
Michael |
Archives