[lime-users] Trouble connecting the dots

Hello all, I'm having some trouble getting traffic routed. I have a couple Bullet M2 XW devices.  One is a gateway connected via Ethernet to the internet, and the other I connect to over wifi to try and access the internet. I'm using chef images; I selected LibreMesh, Testing, Ubiquiti Rocket M XW, Libremesh with BMX7 and libremesh-adhoc as the options. The configuration I'm running is mostly stock; I read that since these particular devices only have one ethernet port you have to manually set it to be a WAN port.  I did this by removing eth0 from the lan bridge and adding the following to /etc/config/network: ``` config interface 'wan'         option proto 'dhcp'         option ifname 'eth0'         list protocols 'wan' ``` Now this wan unit gets a DHCP address from eth0, can access the internet properly, etc. When I set up the other unit, it seems to connect the BMX7 adhoc network properly: both web interfaces populate a bunch of information on the BMX7 pages.  From the consoles on both units they can ping each other's IPv6 addresses.  From the non-wan unit, when I check the BMX7 Gateways tab, I can see that the wan unit is announcing an Internet IPv4 network, so it looks like things are close to working. From here I'm not sure what to do.  I would expect at this point if I try to access the web from the non-wan unit I should be able to, since BMX7 looks OK and it can see that a node is announcing a route to the internet.  But I'm not sure how this actually works; the non-wan unit gets a route like this: ``` Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 0.0.0.0         0.0.0.0         0.0.0.0         U     1024   0        0 X7Out_5C7DE568 10.13.0.0       0.0.0.0         255.255.0.0     U     0      0        0 br-lan 10.13.0.0       0.0.0.0         255.255.0.0     U     1024   0        0 X7Out_5C7DE568 ``` While the units can ping each other's IPv6 addresses, they cannot ping each other's IPv4 addresses; I'm not sure if this is to be expected.  The non-wan unit cannot seem to ping any IPv4 addresses other than my laptop.  What I was expecting was the non-wan unit getting a default route to the wan unit once it sees the announcement of an Internet IPv4 network but this does not seem to be the case.  I must be missing something, but I cannot seem to find it in the documentation.  Any insights or suggestions of what to check? Thanks, Charles