[Commotion-discuss] mesh and gateway (internet) conflict

[falanster.by]

Hello,

There are our today result:

1. We tried to connect to node (U Nanostation M2), we implemented
several approaches:
1.1. Use direct cable connection.
1.2. Use connection through AP (TP-LINK WDR4300) - commotion software

It gave us access to a captive portal on an AP (not commotion node) but
when we started to load an administration page it hung and broke.
We
    1. reloaded of all hardware several times in certain consequence.
    2. plugged out all devices.

2. The situation was the same with commotion nodes (U Nanostation M2).

3. In other case when we switched off DHCP (mode: acquire DHCP lease...)
on AP (on Node we didn't have access this evening)
Then all devices AP, Node (we scan network with nmap) and clients had IP
addresses as 192.168.0.XXX In the case we had just Internet...

We don't know where is the issue because of unpredictable hardware and
software behaviour. 
It is strange and dismotivated us today. Tomorrow we will bring other
routers but the question remained.
And try to change to another.

Thanks,
Mikhail


On 09/05/2015 02:57 AM, Andy Gunn wrote:
> Hi Mikhail - my first instinct is to change "This device should always
> PROVIDE DHCP" to "This device should always RECEIVE DHCP".
>
> The reason for this is the router or modem connected to the Internet
> (not the Commotion device) should be giving out an IP address via DHCP
> to Commotion nodes on the Ethernet port. When the Commotion node
> receives that IP, it will set itself up as a gateway.
>
> I'm realizing the language is a bit unclear - it sounds like if you
> change that to always receive, people connecting to the APs won't
> receive IP addresses, but that menu only effects how the WAN Ethernet
> ports behave.
>
> I would also recommend plugging the TP-Link with the 3G card into the
> switch directly, so the Commotion nodes and APs are all getting DHCP
> directly from that, instead of chaining the connection through the
> Commotion TP-Link.
>
> Let me know if this resolves things!
> -Andy
>
>
> On 09/04/2015 03:27 PM, falanster.by wrote:
>> Hello,
>>
>> Today we deploy mesh network (on metafest.by) from two nodes
>> (Nanostation 2M) and two AP (Tp-link WDR4300 - they running on commotion
>> software)
>> The main issue: when we can use Internet the mesh network doesn't work.
>> If we use mesh network Internet doesn't work.
>>
>> There is our configuration on the files:
>> https://www.dropbox.com/s/zx8ef7ev888ua94/mesh-issue-1.jpg?dl=0
>> https://www.dropbox.com/s/ovk4chz1y9zhig7/mesh-issue-2.jpg?dl=0
>>
>> We setup the mode in each commotion node :
>> *This device should ALWAYS provide DHCP**leases **to clients.*
>> All cables are connected to yellow ports and switch.
>>
>> We drilled and followed the manual:
>> https://commotionwireless.net/docs/cck/installing-configuring/common-hardware-setups/
>> https://commotionwireless.net/es/docs/cck/installing-configuring/common-configuration/
> The "Common Configuration" page is old, and should have been removed.
> The "Common Hardware Setups" has replaced it. Not sure how that
> happened, it should have been removed a long time ago!
>
> I will fix that in the website.
>
>> We guess it is some conflict between Gateway router (which provides
>> access to Internet) and Node router (which register all connection
>> wireless and ethernet as well).
>>
>> I will be thankful your any advice.
>>
>> Thanks,
>> Mikhail
>>
>>
>> _______________________________________________
>> Commotion-discuss mailing list
>> Commotion-discuss at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>>