If the name is wan watchping should make the work.

You can check the system log with "logread | grep watchping". You can
see if the daemon is running "ps | grep watchping". And you can restart
it manually "/etc/init.d/watchping restart". If the node has Internet
and watchping detects it, a new "tunIn" rule named inet4 is added to
bmx6 in order to publish the Internet to other nodes (you can check it
with bmx6 -cp).

On 29/03/17 18:13, James Lewis wrote:

If the virtual network device is named "wan", there is a daemon named
"watchping" which will detect the Internet connection, will publish it
and set up the proper NAT rules.

My interface was definitely called wan, but this definitely didn't
happen until I manually added the iptables rules

Anything else to test? Does this daemon need restart or something if
interface setup changes?

Thanks

J

This is the recommended way, but if you do it manually configuring
network from OpenWRT (instead of using lime-config) then you must be
sure that you are using "wan" as interface name and not something like
"wwan" or "wan2".

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@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.

_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users

--
./p4u


_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users

--
./p4u


_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users