[Commotion-dev] meshing over ethernet

[Chris Ritzo]

This sounds like the same issue we encountered in a recent mesh
deployment at AMC. It may be a firewall zone bug specific to meshing
over ethernet. This may help diagnose/fix:

https://github.com/opentechinstitute/commotion-router/issues/128



On Mon 30 Jun 2014 04:23:56 AM EDT, miles wrote:
>
>
> I'm having problems with the following mesh
> Subnet -> wifi -> Device F ->ethernet link -> Device C -> wifi link -> Device A or Device E
>
> C gets updates from F, A and E.   Route table looks good & it can connect to Subnet and the other routers. 
>
> F  only gets routes for C. 
> A gets routes only for  E. 
> E gets routes only for A
>
> all hosts are using the same serval keyring & signing key.  All are rc1.1r2. 
> Each node has a wired ether interface and a mesh interface.  The wired interface is unplugged except for nodes F & C. 
>
> I suspect that part of my problem may be with HNA. 
> https://commotionwireless.net/docs/cck/installing-configuring/common-configuration/ suggests disabling HNA for both devices in "Two wireless devices meshed over an ethernet connection".  This seems counter intuitive. Don't I still want to announce both AP subnets? 
>
> Any suggestions where I should look for problems? 
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev


-- 
---
Chris Ritzo
Senior Technologist, Open Technology Institute
New America Foundation
1899 L St. NW Suite 400
Washington, D.C 20036
202-596-3406
---