[Cerowrt-devel] Meshing broken?

[Cerowrt-devel] Meshing broken?

[Juergen Botz]

In the whole 3.10.x series (2-6 so far) meshing appears to be
broken... my routers come up without an address on either of
the babel interfaces.  Reverting to 3.7.5 makes it work again.

All the relevant processes (babeld, zebra, watchquagga) seem
to be running, and there are no obvious error messages I can
find...

:j

Re: [Cerowrt-devel] Meshing broken?

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

ahcpd is enabled in client mode by default in this test series. So either
you need to have an ahcpd server or two on the mesh running, or to assign
ips manually in /etc/config/network for gw11 and gw01.

See the differences between /etc/config/ahcpd prior to 3.10 for how to
setup a server version of ahcpd

It's nice to know someone is playing with and actually dependent on the
meshy stuff.

I can revert back to server mode if you like but I had a reason for
switching to ahcpd client mode by default. 33 machines in the lab are
clients, and accidentally ending up with a rogue ahcp server on that caused
me serious headaches. Several times. I could, I guess, leave the static ips
up....



On Thu, Aug 15, 2013 at 2:27 PM, Juergen Botz <jurgen@botz.org> wrote:

> In the whole 3.10.x series (2-6 so far) meshing appears to be
> broken... my routers come up without an address on either of
> the babel interfaces.  Reverting to 3.7.5 makes it work again.
>
> All the relevant processes (babeld, zebra, watchquagga) seem
> to be running, and there are no obvious error messages I can
> find...
>
> :j
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 2041 bytes --]

Re: [Cerowrt-devel] Meshing broken?

[Juergen Botz]

On 08/15/2013 07:48 PM, Dave Taht wrote:
> ahcpd is enabled in client mode by default in this test series. So
> either you need to have an ahcpd server or two on the mesh running, or
> to assign ips manually in /etc/config/network for gw11 and gw01.
> 
> See the differences between /etc/config/ahcpd prior to 3.10 for how to
> setup a server version of ahcpd

Well I had been doing sysupgrades, so my config didn't change,
and I had one router as server and one as client in my config
regardless of what you made the default.  But first in 3.10.x
ahcpd wasn't even coming up... this part I figured out, it was
because I had the two 'list interface gwXX' lines in
/etc/config/ahcpd commented out; up through 3.7.x ahcpd came up
and did its thing regardless, but as of 3.10.x those lines are
needed for ahcpd to start.

Now ahcpd starts up, but the gw{01,11} interfaces still
don't seem to get an address even though /etc/config/network
does list them with 'proto ahcp'.

So something is still different... any ideas?

:j

Re: [Cerowrt-devel] Meshing broken?

[Juergen Botz]

One more detail... now that ahcpd starts up on one of
the routers (the 'server') the other does get addresses
on gw01 and gw11.  But the server itself doesn't.

:j

Re: [Cerowrt-devel] Meshing broken?

[Juergen Botz]

On 08/16/2013 03:06 PM, Dave Taht wrote:
> You need to statically assign addresses on the server box. 

Ok, fair enough... but then why did it work without statically
assigned addresses in 3.7.x?

:j