Ok thank you

Let’s figure out

1] Why dhcp leaks outside the lan-to-lan “hyperlan” between lime nodes up into the first lime node’s wan and into the upstream router [ISP in my case]
2] If lan-to-lan hyperlans are safe for wired equipment that hooks up to the network directly [i.e. to a switch] and **not** as a wired client to a lime router
3] What Ilario said – quote here: 

In my opinion LiMe routers should not forward DHCP requests or DHCP offerings. 
Clients should get DHCP offering from the very LiMe router they're 
connecting to. 
Why don't we filter forwarding of DHCP packets?

Last question: as I had noticed in the past, when lan-to-lan meshing over ethernet, the BATMAN status page still shows nodes being connected via wlan interfaces. BMX6 instead has br-lan as via-device. Is this normal? Can I verify the routing is being done correctly, via ethernet, and in the most efficient way, with a trace route for example, or in any other way?

I’m available to test any setup if someone can point me in the right direction

Thanks again!

Nk


On July 5, 2017 at 10:07:34 AM, Nicolas Pace (nico@libre.ws) wrote:

On Tue, 2017-07-04 at 11:22 +0200, Nikksno via lime-users wrote:
> Thank you Nicolas,
>
> What I mean is that if I do the setup ad you said, so ISP ROUTER Lan
> [eth] First LiMe router Wan and then First LiMe router Lan [eth]
> other LiMe router's LAN ports, if I connect a wired client [say a
> desktop pc] to that huge Lan, it will receive several DHCP
> broadcasts. This might not be an issue as you're saying since they
> all advertise the same stuff, but I don't understand how all LiMe
> nodes can apparently respond to 10.13.0.1 on that **wired** network.

I don't have much experience on this, but I guess all send DHCP
responses, all are similar, so the client picks one and announce the
DHCP server which he chose, and that's it.
No matter which router registers the data, as it is a wired network
I guess it will work.... maybe the more experienced guys can comment.
:)

>

> In any event, this setup has an issue whereby DHCP advertisements [if
> that's what they're called] of LiMe nodes connected lan-to-lan travel
> upwards through the wan port of the first lime node [the one
> connected to the ISP router via its wan port, as you suggested] and
> confuses the ISP router itself, to such point that my ISP router
> wasn't managing to connect upstream to the VDSL endpoint, and was not
> connecting to the public facing internet. As soon as I disconnected
> the cable going from the ISP router's LAN port to the first lime
> node's wan port, the ISP router started working again.

I guess this should not be happening.

>
> Also, as soon as we figure this stuff out, and I understand it
> [hardest part ;], I volunteer to write a fully detailed guide on how
> to design a lime topology so that our design works all across the
> world, and deployers like me know how to engineer their networks.

Great!!!
When you get here, let's coordinate :)