[Olsr-users] Help to find best configuration

[Chris W.]

Hello Kevin,

the easiest way would be not to have all clients in the same IP subnet
but in the routers' individual ones.

So on olsr 192.168.2.101 the LAN (& HNA) will have 192.168.101.1 with a
netmask 255.255.255.0 , 192.168.102.1 on the next one etc. This way the
setup remains simple.

You might install olsrd-mod-bmf too.

Hope this info will be helpful.

Best,
Chris W



On 11/13/21 10:58 AM, kevin Legendre wrote:
> Hello Lars
> Thank you for your answer.
> I think I'm trying to do something really complicated for nothing 😕.
>
> My configuration is the one I described on the previous mail.i have
> several routers. Each router have both ethernet and wifi.
>
> And I have several clients. Each client is connected to a router through
> ethernet.
>
> What I want to achieve is having olsr on all the router and I want all
> the clients to be able to communicate together.
>
> The best would be to have all the clients and router using the same subnets.
>
> I tried to setup one bridge interface between lan and Wan on each router
> with olsr on it.
>
> And then have a static ip on each client with the same subnet.
>
> But a client can only ping a neighbour client it can't talk to a client
> that is several nodes after.
>
> Do you have any advice for this kind of setup?
>
> Thanks in advance
>
>
>
>
>
> Le 12 nov. 2021 16:00, Lars Kruse <(spam-protected)> a écrit :
>
>     Hallo Kevin,
>
>
>     Am Fri, 12 Nov 2021 10:38:17 +0000
>     schrieb kevin Legendre <(spam-protected)>:
>
>      > With this configuration :
>      > 1) All the router can ping each others
>      > 2) All the router can ping all the clients
>      > 3) All the clients can ping all the routers
>      >
>      > But I can't ping a client from another client.
>
>     I guess, executing "ip route get 192.168.1.2" on your client1 will
>     reveal, that
>     the client expects the target on its *local* interface.
>     Thus it will issue ARP requests (you could check this via "tcpdump
>     arp"?) and
>     give up, without event talking to router1.
>
>     I see the following options:
>     A) reduce the IPv4 address on client1 from "192.168.1.1/24" to
>     "192.168.1.1/32"
>         and add at least the following static routes:
>             192.168.1.101/32 dev eth0
>             192.168.1.0/24 via 192.168.1.101
>     B) use different subnets for the client networks
>
>      From my point of view, (A) is *very* hacky.
>     (I am not sure, whether your requirements could justify such a crude
>     setup)
>     I think, (B) should be preferable.
>
>     Please note, that your setup allows only routed traffic (i.e. no
>     broadcasts of any kind) between the different networks behind the
>     clients. Thus
>     there is probably really no point in using the same subnet for these
>     separate
>     physical networks.
>
>     Regards,
>     Lars
>
>
>     PS: "tcpdump" is a *very* useful tool for verifying your
>     expectations of the
>     network traffic
>
>
>