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