| 1 |
Sorry, I sent you the wrong output of ip route sh table 0. |
| 2 |
|
| 3 |
Follows the right one (sorry!) |
| 4 |
|
| 5 |
# ip route sh table 0 |
| 6 |
192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 |
| 7 |
195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 |
| 8 |
default via 195.75.145.1 dev eth0 |
| 9 |
broadcast 127.255.255.255 dev lo table local proto kernel scope link |
| 10 |
src 127.0.0.1 |
| 11 |
local 195.75.145.122 dev eth0 table local proto kernel scope host src |
| 12 |
195.75.145.122 |
| 13 |
broadcast 192.168.19.0 dev eth2 table local proto kernel scope link src |
| 14 |
192.168.19.95 |
| 15 |
broadcast 195.75.145.255 dev eth0 table local proto kernel scope link |
| 16 |
src 195.75.145.122 |
| 17 |
broadcast 195.75.145.255 dev lo table local proto kernel scope link src |
| 18 |
195.75.145.120 |
| 19 |
local 195.75.145.120 dev lo table local proto kernel scope host src |
| 20 |
195.75.145.120 |
| 21 |
local 192.168.19.95 dev eth2 table local proto kernel scope host src |
| 22 |
192.168.19.95 |
| 23 |
broadcast 192.168.19.255 dev eth2 table local proto kernel scope link |
| 24 |
src 192.168.19.95 |
| 25 |
broadcast 195.75.145.0 dev eth0 table local proto kernel scope link src |
| 26 |
195.75.145.122 |
| 27 |
broadcast 195.75.145.0 dev lo table local proto kernel scope link src |
| 28 |
195.75.145.120 |
| 29 |
broadcast 127.0.0.0 dev lo table local proto kernel scope link src |
| 30 |
127.0.0.1 |
| 31 |
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 |
| 32 |
local 195.75.145.0/24 dev lo table local proto kernel scope host src |
| 33 |
195.75.145.120 |
| 34 |
local 127.0.0.0/8 dev lo table local proto kernel scope host src |
| 35 |
127.0.0.1 |
| 36 |
|
| 37 |
Regards, |
| 38 |
Massimiliano |
| 39 |
|
| 40 |
On Mon, Nov 7, 2011 at 14:59, Pandu Poluan <pandu@××××××.info> wrote: |
| 41 |
|
| 42 |
> |
| 43 |
> On Nov 7, 2011 8:38 PM, "Massimiliano Ziccardi" < |
| 44 |
> massimiliano.ziccardi@×××××.com> wrote: |
| 45 |
> >> |
| 46 |
> >> seems to be a really tricky one... |
| 47 |
> >> What does |
| 48 |
> >> tracepath 195.75.145.33 |
| 49 |
> >> give? |
| 50 |
> > |
| 51 |
> > |
| 52 |
> > Here is the output: |
| 53 |
> > |
| 54 |
> > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu |
| 55 |
> 16436 |
| 56 |
> > 1: 195.75.145.33 (195.75.145.33) 0.039ms |
| 57 |
> reached |
| 58 |
> > 1: 195.75.145.33 (195.75.145.33) 0.028ms |
| 59 |
> reached |
| 60 |
> > |
| 61 |
> > I tried shutting down localhost with: |
| 62 |
> > |
| 63 |
> > ifconfig lo down. |
| 64 |
> > |
| 65 |
> > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx |
| 66 |
> addresses). |
| 67 |
> > |
| 68 |
> > And now tracepath gives: |
| 69 |
> > |
| 70 |
> > 1: send failed |
| 71 |
> > Resume: pmtu 65535 |
| 72 |
> > |
| 73 |
> > So, for some reason, seems it always uses the 'lo' device... |
| 74 |
> > |
| 75 |
> > Any idea? |
| 76 |
> > |
| 77 |
> |
| 78 |
> I've been deploying multi-interface Linux gateways since 2008, so I'll try. |
| 79 |
> |
| 80 |
> Please post: |
| 81 |
> |
| 82 |
> - output of ip rule sh |
| 83 |
> - output of ip route sh table $t, where $t is *all* table names/numbers |
| 84 |
> you get from the first output ( "... lookup $t" ) |
| 85 |
> |
| 86 |
> Rgds, |
| 87 |
> |
Archives