Hi, all The routed mesh node connected to Internet need to have WAN doing NAT Masquerade. Then, your wireless interface on the routed mesh node has the DHCP server setup (allocating 192.168.100.0/24) on the mesh wireless interface. Other mesh nodes are configured with DHCP client attached to the wireless interface. Then, they will get the IP addresses in the range of 192.168.100.0/24. If your DHCP server assigned the default route. Then, every single mesh node can send the traffic out to Internet.
As David pointed out, 11s is on layer-2 routing or MAC routing, not layer-3 routing, such as OLSR, so your mesh node won't have any IP routing table update even if you play around with the o11s mesh parameters. RANN or root node assignment is a proactive routing that assists to minimize the setup latency for other mesh nodes to find the mesh node with connectivity to outside world. But bear in mind, it is on layer-2, you can inspect the "iw wlan0 mpath dump" and see that the MAC routing table is updated with the mesh node setting as root node and gate announcement. Hi, maxe Perhaps, you can try the steps that Thomas mentioned and raise the issues again. So that it will be more easy to follow up what's the problem. Regards, Chun-Yeow On Sat, May 5, 2012 at 4:35 AM, Thomas Pedersen <[email protected]> wrote: > Hi Maxe, > > Did you try the steps I oulined in the other thread? > > Thomas > > On Fri, May 4, 2012 at 3:03 AM, maxe wifi <[email protected]> wrote: >> Dear All, >> >> >> Can anyone help me in 802.11s mesh internet connectivity. >> >> >> Thanks >> Maxe >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel >> > _______________________________________________ > Devel mailing list > [email protected] > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
