| 1 |
On Nov 7, 2011 8:38 PM, "Massimiliano Ziccardi" < |
| 2 |
massimiliano.ziccardi@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> seems to be a really tricky one... |
| 5 |
>> What does |
| 6 |
>> tracepath 195.75.145.33 |
| 7 |
>> give? |
| 8 |
> |
| 9 |
> |
| 10 |
> Here is the output: |
| 11 |
> |
| 12 |
> 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu |
| 13 |
16436 |
| 14 |
> 1: 195.75.145.33 (195.75.145.33) 0.039ms |
| 15 |
reached |
| 16 |
> 1: 195.75.145.33 (195.75.145.33) 0.028ms |
| 17 |
reached |
| 18 |
> |
| 19 |
> I tried shutting down localhost with: |
| 20 |
> |
| 21 |
> ifconfig lo down. |
| 22 |
> |
| 23 |
> Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx |
| 24 |
addresses). |
| 25 |
> |
| 26 |
> And now tracepath gives: |
| 27 |
> |
| 28 |
> 1: send failed |
| 29 |
> Resume: pmtu 65535 |
| 30 |
> |
| 31 |
> So, for some reason, seems it always uses the 'lo' device... |
| 32 |
> |
| 33 |
> Any idea? |
| 34 |
> |
| 35 |
|
| 36 |
I've been deploying multi-interface Linux gateways since 2008, so I'll try. |
| 37 |
|
| 38 |
Please post: |
| 39 |
|
| 40 |
- output of ip rule sh |
| 41 |
- output of ip route sh table $t, where $t is *all* table names/numbers you |
| 42 |
get from the first output ( "... lookup $t" ) |
| 43 |
|
| 44 |
Rgds, |
Archives