20 Nov
2007
20 Nov
'07
1:45 p.m.
Hi,
Marek Lindner wrote:
- More important: The routing table operates on IP
addresses and not on
interface names. Even if olsrd can distinguish your interfaces by name the
kernel can't.
sure? (I'm in no way an expert, its an honest question.)
root@OpenWrt:~# ip route
192.168.1.48 via 192.168.1.188 dev ath1 metric 7
192.168.2.40 via 192.168.1.188 dev ath1 metric 6
192.168.1.49 via 192.168.1.188 dev ath1 metric 4
192.168.2.42 via 192.168.1.188 dev ath1 metric 7
192.168.1.51 via 192.168.2.172 dev eth0 metric 2
192.168.1.53 via 192.168.1.188 dev ath1 metric 6
192.168.1.56 via 192.168.1.188 dev ath1 metric 6
192.168.2.32 via 192.168.1.188 dev ath1 metric 7
192.168.1.57 via 192.168.1.188 dev ath1 metric 6
192.168.2.33 via 192.168.1.188 dev ath1 metric 8
192.168.1.58 via 192.168.1.188 dev ath1 metric 3
192.168.1.60 via 192.168.1.188 dev ath1 metric 7
....
so there are interfaces shown in the routes, the kernel should recognize
them, what else they are for?
Imagine: You have a node A with 2 Interfaces and node
B can hear both
interfaces but one better than the other. The routing table entry would look
like that "<destination> via IP_of_node_A" whereas the kernel can't
send the
packet to a distinct interface of A.
see above...
regards,
Rene
PS: Invited Sebastian Hagen who programmed the patch to join the
discussion, hope he will help me/us with more details