wlan1?
Waht?
I suggest to reflash with the "bullet" image (if your device is XM)
without keeping old configuration (-n option of sysupgrade or the check
in the web interface) and retry with Pau's instructions which basically is:
add
config net wan_network
option linux_name 'eth0'
list protocols 'wan'
to /etc/config/lime
issue lime-config
reboot
Then it should automagically work.
For connecting to the device now will be easier via wireless or via
ethernet with IPv6 link-local (via ethernet now there's a DHCP client,
not server).
Let us know :)
Ilario
On 03/29/2017 02:13 PM, James Lewis wrote:
Pau,
Thanks for the info.
It appears that you can do this through the UI. I tried adding the
lines as per the doc to /etc/config/lime, then ran lime-config but it
didn't seem to make any difference - eth1 was still shown as being in
wan.
I then made the change through the UI - added eth0 to wan instead of
eth1, and it then got DHCP ok.
But, no devices connecting to the mesh networking could route out
through that connection (their gateways were set correctly to
10.13.0.1, all mesh devices were talking to each other, and the mesh
device with the gateway could connect to internet devices fine)
So, I tried adding manual NAT settings [1], and this made everything work!
Is that the correct way to set up the gateway device, or is there a
setting somewhere in the libremesh firmware that should have taken
care of this for me?
Thanks again
James
[1] (obviously with interface names changed)
iptables -A FORWARD -i wlan1 -o wlan0 -j ACCEPT
iptables -A FORWARD -i wlan0 -o wlan1 -m state --state ESTABLISHED,RELATED \
-j ACCEPT
iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
On Tue, Mar 28, 2017 at 8:08 PM, Pau <pau(a)dabax.net> wrote:
> On 28/03/17 18:54, Ilario Gelmetti wrote:
>> On 03/28/2017 06:41 PM, James Lewis wrote:
>>>>> On 28/03/17 16:13, James Lewis wrote:
>>>>>> Now the quesiton is: how do we set one of the mesh devices to
_take_
>>>>>> DHCP through the LAN port rather than give it, and to be the
'gateway'
>>>>>> device on the mesh network, and then what will happen with
devices
>>>>>> that subsequently connect to the mesh? How will they get their
gateway
>>>>>> set?
>>>>
>>>> There are two ways in your case:
>>>> * configuring LibreMesh for using that ethernet port as WAN (as Pau is
>>>> going to write in the web);
>>>
>>> Great, this is what we thought and tried, but perhaps got something wrong
>>> somewhere as it didn't work. Look forward to Pau's docs.
>
> Let's see if it helps you understand how it works.
>
>
http://libremesh.org/docs/changing_network_behavior.html
>
> Feel free to make comments and/or send modifications via pull-request.
>
> We are working on the LiMe Web interface and soon this kind of
> configuration will be available via Web, but for the moment it is only
> possible via shell.
>
>> Did you modify just the /etc/config/lime* files or also the others?
>> I have no idea if this can be done also via the web-ui (I don't think so).
>>
>>>> * otherwise just plugging the cable from the gateway device into the
>>>> secondary port of Nanostation M2 (your model has 2 ethernet ports,
>>>> right?)
>>>
>>> No, I have the little M2 which only has one ethernet port.
>>
>> Ah ok! So it's a Ubiquiti NanoStation M2 LoCo
>>
>>> I do have eth0 and eth1 interfaces though
>>
>> For the LoCo XM model (as well for other models with just 1 ethernet
>> port) the "bullet" image should be used [1]. For XW hardware with one
>> ethernet port (also stuff like newest AirGrid models) there's a
>> "loco-m-xw" image.
>> If you see two ethernet could be because you used the "nano" image.
>> I suppose that there's no problem of having an unused eth1...?
>> Ciao!
>> Ilario
>>
>> [1]
https://wiki.openwrt.org/toh/ubiquiti/airmaxm
>
> I think the eth1 controller exist but the physical port is just not
> attached.