Hi Mark, FYI, 802.11 and 802.15.4 protocol is different. The 802.11 is for Wi-Fi connectivity, and 802.15.4 is for Low Power Wireless Area Network, especially for Sensor Network.
-- Rgds, Aston Blog <http://astonugroho.wordpress.com/> | Twitter <http://twitter.com/astonix> | LinkedIn <http://www.linkedin.com/in/aston/> "If you are working on something exciting that you really care about, you don't have to be pushed. The vision pulls you." (Steve Jobs) On Thu, Jul 14, 2016 at 7:49 AM, 'Mark Lazarewicz' via BeagleBoard < beagleboard@googlegroups.com> wrote: > mesh networks use a 802.11.15.4 link layer > > ------------------------------ > *From:* "pedrotecc...@gmail.com" <pedrotecc...@gmail.com> > *To:* BeagleBoard <beagleboard@googlegroups.com> > *Sent:* Wednesday, July 13, 2016 5:30 PM > *Subject:* [beagleboard] 802.11 Mesh Network with WiLink 8 > > Hi, > > I am trying to create a 802.11 Mesh Network using BBG-W. It seems to me > that it should be possible as TI has advertised that their WiLink 8 modules > are capable of this type of network. > > I first tried to use "sudo iw phy phy0 interface add mesh0 type mp mesh_id > mymesh", but it returns "Operation not supported (-95)". Then, I noticed > that "iw list" says only: > " Supported interface modes: > * managed > * AP > * AP/VLAN > * monitor > * P2P-client > * P2P-GO > * P2P-device" > So no mesh... > > I am using "BBGW-blank-debian-8.5-seeed-iot-armhf-2016-07-10-4gb.img.xz > <https://rcn-ee.net/rootfs/bb.org/testing/2016-07-10/seeed-iot/BBGW-blank-debian-8.5-seeed-iot-armhf-2016-07-10-4gb.img.xz>" > image. > > I hope this is a driver related problem, is that it? > > If so, how should I proceed? Follow > http://processors.wiki.ti.com/index.php/WiLink8_Linux_Getting_Started_Guide > to create a compatible image? > > Best, > Pedro > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/97cd0755-b505-4da4-bdd5-a193849324a6%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/97cd0755-b505-4da4-bdd5-a193849324a6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/1678669680.2913949.1468457345379.JavaMail.yahoo%40mail.yahoo.com > <https://groups.google.com/d/msgid/beagleboard/1678669680.2913949.1468457345379.JavaMail.yahoo%40mail.yahoo.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CA%2B9kmzw69ccKA6JyZFFHOrngS6tnF9L%3D0jsOAFcH-_%2BZvAPG4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
