shortlink:
http://bit.ly/vm2VDx
and it is also quantity prices...
Quantity 3+ units 5+ units 10+ units
Rate $22.40 shipped $22.30 shipped $22.20 shipped
I just ordered three of them....
I will add them to my MeshPotato network and see how it works.
How would it be to use 802.11n standard on this? Use a 20MHz channel
for good range....
cheers
sjur
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
Hi Paul
We have started looking at this briefly.
When flashed with OpenWRT and webif as above it comes up in AP mode which works fine with WPA.
We can't get it to work in adhoc mode as yet. Also can't get it working in client mode with WPA. It wants to load up a module which is actually already loaded.
On the other hand, batman modules etc are all ready to load with opkg.
Just needs a few good eyes looking at it I think.
Regards
Terry
SKU = 99273
Genuine TP-LINK TL-WR703N 150M
11N Mini 3G/WiFi Wireless Router for Instant WiFi Connection
Qty 3 @ $18.51 = $55.53
Air Mail With Shipment Tracking $ 10.81
Total: USD $66.34
Dave Duchesneau
Paul.
--
If you buy three from dealextreme, remember to click on the "bulk rate" on checkout.
Vennlig hilsen
Sjur Eivind Usken
+47 96999902
do you have a firewall running?
Cheers,
Elektra
>
> It would be good to hear from others as to their experiences in setting up
> the device.
Hi Terry
I dont have one of these units, they arent availlable here yet.
But I'll give this a stab.
Are u using madwifi or ath?
What normally causes the batman-adv issue is, when batman starts
before the interface is up,
What I do is get adhoc operating first, then script the virtual
interface, to run via hostap.
check ps-aux, to make sure batman is running, check also batctl -i ,
I would take out the second bssid, I'm not to sure how luci deals with comments.
In network, ifname does not look right,, try changing wlan0 and wifi0.
what does ifconfig give?
Sorry, best I can do without a unit,
> I don't have one of these units, they aren't available here yet.
I was going to send three TP-Link units to Terry, but I just got the
necessary customs form, so I haven't sent them yet. If you and Terry agree,
I could send one to you, and two to Terry. I will need a shipping address.
If either of you needs more, I can order additional units. Although you are
welcome to keep the unit(s), please note that these are intended to help the
VT dev team, and are not for production purposes. Of course, limited
deployment for testing is fine, if that's your highest and best use of them.
...Just trying to remove a few roadblocks...
Dave Duchesneau
d...@crisis-force.org
what does ifconfig give?
--
This would be great, if Terry agree's.
Wayne
Hi Dave
I have been able to arrange for some more units to be sent and they are on the way so it may be more useful to send yours to the other people who are working on this ie Wayne, Keith and Elektra.
Thanks
Terry
Hi Elektra
Firewall - a good thought.
A quick look shows that the firewall is set up by default in the firmware.
It is set to allow lan to lan traffic explicitly.
I started to look at this but realised that something else has gone awry and I am only getting rx traffic on the wlan0 interface.
I will reflash and start again with a clean slate.
Thanks for the tip.
Xxcccc
Regards
Terry
Hi Wayne
Thanks for the tips. I am really only just getting started with this and squeezing it in to bits of time between other jobs so it is a bit fragmented.
This firmware / device is a bit different to to MP and uses wlan0 instead of wifi0.
I will send you some iw and ifconfig outputs so you can see what is happening.
Batman-adv is running and the wlan interface is handling traffic from the mesh, but the two haven't made the connection as yet.
The units are not available here either. I ordered mine on line and it was shipped from Hong Kong. I will send you the details if you wish. It will be good to get a few more experienced people looking at this.
RegardsJn
Terry
Hi Terry
Try removing option 'network' 'wifi0'
Thus removing the interface from the firewall.
Another thing, do the logs mention anything about mtu? Amazingly on
one unit I had to raise the mtu to a higher rate for some weird
reason.
Wayne
Here u go:
As per log
batman_adv: bat0: The MTU of interface wlan0 is too small (1527) to
handle the transport of batman-adv packets. Packets going over this
interface will be fragmented on layer2 which could impact the
performance. Setting the MTU to 1528 would solve the problem.
I found 1528 still didnt do it, but just raise it in config/network
until the warning goes away.
YMMV ( I didn't really investigate, but I could send it to the BAT-DEV
list to get a answer.)
Wayne
Can't remember offhand, I since changed the build, but it was about
153* , The warning did cause batman to seem like it's working but it
did not work until I changed the value.
All I can remember is , I changed until the warning disappeared, then
it was fine.
Wayne
Hi Wayne
I set the MTU to 1550 on both TP and MP devices which removes the error message from dmesg but still no connectivity.
Regards
Terry
Terry
I did not change it on the working mesh side at all, and it def wasn't
that high, Did you move up slowly? I recall it was some where in the
30's.
However, I see wr703 is now integrated into trunk, maybe try compiling
your own with a older version of batman-adv. Could be a version
incompatibility issue. I've posted to Bat-dev.
Hope I can get a unit soon,
Cheers
Wayne
If you think the 703 was great, check this out, the possibilities are
becoming endless.
Who votes for a small gateway to service a small # of MP's ?
Wayne
Wayne
Seems you've solved all the mesh and Vap challenges, care to
divulge,,, Or some Friday humour for us?
Enjoy!
--
Terry
Have you tried to compile from a fresh openwrt build checkout?
Marek from the bat-adv dev list opines thus:
> We had some bugs in the 2011.3.0 release which led to connection issues,
> therefore we released 2011.3.1. However, the originator list was unaffected.
> You might want to give it a try.
Good luck
Wayne
Hi Wayne
I think you are right. A clean build environment for the TP devices will help sort out the issues and we are working on that now. Also I should have some extra TP devices soon so we can test with same firmware and package versions even before we start building new firmware.
Do you plan to use the TP devices at all?
Regards
Terry
Yep, I'm still waiting on dave, if not I'll try to get somewhere. I did try to build a old version with trunk for u to try, but ran into a few challenges, Batctl errors, I'll try again, and send the package.
Hi Wayne,
I just need physical addresses to ship to. I believe the last suggested recipients were Wayne, Keith, and Elektra, but I could be wrong. Shipping addresses can be emailed privately to d...@crisis-force.org. I’ll be shipping from the USA, but the TP-Link units came from Hong Kong.
Dave Duchesneau
From:
village-...@googlegroups.com [mailto:village-...@googlegroups.com] On Behalf Of Wayne Abroue
Sent: Sunday, November 06, 2011
11:02 PM
To:
village-...@googlegroups.com
Subject: Re: [vt-dev] Re: Small
Linux Appliance - TP-Link TL-WR703N
Yep, I'm still waiting on dave, if not I'll try to get somewhere. I did try to build a old version with trunk for u to try, but ran into a few challenges, Batctl errors, I'll try again, and send the package.
PM sent
Thank you
ditto.
Elektra
TP only,
Strange, did u enable and set the config? but read this thread,
recovery explained
https://forum.openwrt.org/viewtopic.php?id=31729
Hopefully I'll be getting mine soon,
Wayne
I am replying to the list, since the information can be interesting for others.
> If I recall correctly you mentioned in one of your emails that you had
> recovered your TP Link boards via the serial port.
>
> Would you be able to point me to a HowTo document that shows how to go
> about this, and any particular hints for TP Link units.
There are a few options for de-bricking a OpenWRT device.
If it is a configuration failure, you might get access to the device via the OpenWRT failsafe method. The procedure is explained here:
http://wiki.openwrt.org/doc/howto/generic.failsafe
However, for advanced firmware work you will always need a serial port to talk to the serial console of the device. It is a integral part of the toolkit of a firmware developer. Even more so, if the OpenWRT firmware does not check a hardware key during the bootup process. So you never might get into failsave without the help of a serial console.
Unlike the MP the TP-L 703 comes with the U-Boot bootloader. All TP-Link devices that I came accross do not support connecting to the bootloader via telnet or http. You need a serial port in order to talk to the bootloader and trigger a firmware update via tftp.
Usually the pins to access the serial port are not populated by the manufacturer on the pcb. You need some pin header pins and sockets (usually 2.54mm grid) from an electronics store, solder wire and a solder iron, as well as a mini drilling machine (Proxxon, Dremel...) and a 1 mm drill. Or better: You know a electronics technician that will do the required steps for you.
You should now have three additional pins on the pcb: Ground, TX and RX.
Now we have one more small hurdle to overcome: The RS232 port on a uC (microcontroller) board usually only has 3.3 Volt levels. The RS232 port of a PC however uses -5 Volt / + 5 Volt at least for the binary 0 and 1 signals on the serial interface. This is where a level shifter comes in. A level shifter will adapt the uC serial port levels to the RS232 levels of a PC.
You can get a data cable for a old mobile phone, since these also had to use RS232 and include a level shifter. Chances are that you already have that lying around somewhere. A electronics store may also sell a generic circuitry that includes a USB-to-serial-converter which operates on uC levels. Another option is to solder a level shifter on a bread board.
There are a number of IC chips that do it. The IC MAX232 takes a single 5 Volt supply (I use this solution and connect it to a USB port) and a few external components to do the magic. There is another MAX232 version which only needs 3.3 Volt.
http://www.societyofrobots.com/microcontroller_uart.shtml
Next you need a terminal program. The Linux recommendation is minicom. Now you can talk to the serial console of the darn WiFi device :)
Last but not least you need to set up a tftp server on your PC, if you want to reflash devices from the bootloader.
Cheers,
Elektra
Hi According to the guys already busy with the TP.
To enter failsafe mode:
1. Reboot (Power Down and then UP) the router
2. When the blue LED starts flashing, press the RESET (inside the tiny
hole next to the mini-usb)
3. Stop pressing the RESET when the blue LED starts flashing quickly
At this time the router is in failsafe mode.
4. telnet 192.168.1.1. It will take you to the root prompt.
5. Enter "firstboot" at the prompt to reset the router to default
6. Reboot.
Serial connection:
As already pointed out, TP_In is Rx and TP_Out is Tx.
GND is any GND point.
Takes a bit of soldering skills though.
Wayne
good to know that failsafe mode works already!
> 4. telnet 192.168.1.1. It will take you to the root prompt.
> 5. Enter "firstboot" at the prompt to reset the router to default
Another option is to mount the root filesystem read/write and fix the configuration mistake(s) by performing:
mount_root
Cheers,
Elektra
So after a small diversion via OpenWrt Recovery, back to the problem of why the TP unit won't work on the mesh.
Since we can see tx and rx traffic in the output of ifconfig on both MP and TP units, it would seem to indicate that the issue is at the batman layer.
The MP version of batman-adv is earlier than that on the MP and Wayne has suggested that this is a possible cause of the issue.
As I only have one TP unit at present (the others are still swimming across the ocean from HK) , I can't test whether two TP units will mesh together.
It would be good to get packages for both devices built to the same version, presumably the latest known stable version.
Elektra
Would it be possible to compile the package for the MP at the same or better version as is used in the TP build?
Or would it be better to build the package for the TP unit at the same version as the MP since we know that one works?
Wayne
When I installed the package you built, I made sure the config files were set up correctly (ie same as for previous) before I rebooted, so I don't think that was the issue. The unit responded to pings ok for a second or so at the end of the flashing led boot up period. So my conclusion is that something upset the networking operation late in the boot sequence, presumably the new package.
Is it worth having a look at the build config to see if there is some problem there?
As I am not set up to build these packages I greatly appreciate your collective help with this.
Regards
Terry
Great, Seems these WRT-devs don't have any social life, How they
figure out all these undocumented tricks is beyond me.
Wayne
Hi Terry
I'll give it another go, this time, getting the MP up to latest stable.
What wrt version are you running on each, and what are the current Bat
versions on both units?
Wayne
Wayne
I have compiled a more recent version of the batman-adv kernel module for the MP - attached. It is not the latest, but I did not see any issues with this version. I can also compile this version for the TP-Link, so if the issues are in fact related to the differences in the batman-adv version - and not problems with the ath9k WiFi driver - we can downgrade to 2011-2.0. Unfortunately support for Linux kernels earlier than 2.6.29 has been dropped after this batman-adv version, since there have been changes in the Linux networking infrastructure. Currently the MP firmware is running 2.6.26.3
So I could either manually patch each upcoming release of batman-adv or we switch to a more recent kernel with the MP. This actually calls for a kernel update for the MP firmware, I think.
Cheers,
Elektra
Hi Tom,
Do you have a way to log the to/from IP addresses observed in the IP traffic? Are the devices trying to probe the LAN? The upstream WAN? Trying to call home?
Dave Duchesneau
From: village-...@googlegroups.com [mailto:village-...@googlegroups.com] On Behalf Of T Gillett
Sent: Thursday, November 10, 2011
2:30 PM
To: village-...@googlegroups.com
Subject: Re: [vt-dev] Re: Small
Linux Appliance - TP-Link TL-WR703N
Hello All
--
read the batman-adv developer list or the changelog. these two
versions are known to be not compatible. yout need 2011.2.0 on MP
_and_ tplink or 2011.3.1 on both...
> One important point: the BSSID used for the mesh cell identification has to
> be changed from the default MP one starting with 01: ... to 02: ...
one more word on this: I have been told that the least significant bit in the first byte of the cell-id is not allowed to be 1, since the cell-id might be seen as a broadcast cell-id. I have not noticed any problems related to this so far, but OpenWRT is now enforcing this policy. So there is a problem now. Well, it might lead to a real-life hard to debug problem one day.
If the least significant bit of the first byte is 1, OpenWRT will not enable the ad-hoc interface.
So, 02:... in binary is:
00000010
- this is fine, since the least significant bit is 0.
01:... in binary is:
00000001
- this is now ignored by OpenWRT, since the least significant bit is 1.
So we can use 00: 02: 04: 06: 08: and so on, any even number. Or we use 02: and vary the CA:FF:EE:BA:BE part. CA:FF:EE:BA:BE is popular, because it is human readable and memorable. We can make a brainstorm about easy to remember cell-ids :) Obviously we can use ABCDEF, 0=O,1=I and with a bit of phantasy other numbers...
One word of caution:
If you don't want cells to merge that you don't want to merge the cell-id *must* be different.
A last word:
If you don't care about this or don't want to reconfigure all the existing nodes in your mesh you can still create an ad-hoc interface with the least significant bit being one with OpenWRT trunk, by first creating a cell-id which is accepted and then setting it to 01: with iwconfig:
iwconfig ath0 ap 01:CA:FF:EE:BA:BE
iwconfig does not care about this.
Cheers,
Elektra
Hello -
00000010
00000001
One word of caution:
A last word:
Cheers,
Elektra
--
You received this message because you are subscribed to the Google Groups
"village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to
village-telco-...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/village-telco-dev?hl=en.
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6627 (20111114) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 6627 (20111114) __________
The message was checked by ESET NOD32 Antivirus.
Kudos to Keith, Elektra, and Terry, and any others who were in on this! You rock!
Let me be the first to congratulate you! Besides getting theses devices to play nice, the fringe benefit from finding and highlighting the broadcast bit problem is that future ports may be easier. This is actually a giant step forward toward device interoperability.
Dave Duchesneau
Tenacity! Completely inspiring tenacity in breaking down every
obstacle that came up and there were more than a few. Kudos to all
three of you.
That confirms the AR9331 chip as a viable platform.
Cheers... Steve
--
Steve Song
http://manypossibilities.net
http://villagetelco.org
Hi Terry and all,
Thanks for the nice summary of the situation.
Ø At one extreme, …SECN 2.0 … BSSID of 02: ...
Ø and a current version of batman-adv,
Ø which would mean… updating the MP01 firmware,
Ø but would be easier for porting to other devices.
Ø …
Ø At the other extreme, …stay with MP01… easy for the moment,
Ø but …more difficult to port to other devices.
If I had a vote, I’d vote for the longer view (i.e., get things in sync so that VT can take advantage of the work of other development communities, and vice-versa).
That’s my two cents’ worth.
Dave Duchesneau
From: village-...@googlegroups.com [mailto:village-...@googlegroups.com] On Behalf Of T Gillett
Sent: Monday, November 14, 2011
7:28 PM
To: village-...@googlegroups.com
--
Cheers... Steve
--
Paul
Good call, I will be doing some testing to have bat-adv on the mesh,
with batmand (L3) on the VAP AP,
In theory this should work fine, It just hasn't been tested enough for
feasibility yet.
Watch this space!
Wayne A
Simpler, better, faster! I'll be sure to test that!
Wayne
If that works it means that a SECN network can support both softphones and serval based phones which would be a nicely complete offering.
running batmand and batman-adv together would be no problem.
With regards to the kernel version issue: I have already started on getting the MP to work with the latest kernel
of OpenWRT trunk. But that might take a while to complete.
I'm also working on improving the scalability and performance of batmand, thanks to the support of Paul and a grant
from the Dutch NGO nlnet.nl.
My server is running again, will upload the backup as soon as I have sufficient bandwidth. (I am currently depending
on 3G with traffic limit). So batman-adv images for ath9k based WiFi devices will be available soon.
Cheers,
Elektra
--
Viral meme of radical freedom
The fact that you talk in your head doesn't mean that you think.
The best way to lose control over yourself is trying to control yourself.
Most people experience themselves as a voice in their head, telling them
who they are, what they think and what they have to do.
O.T
If you think the 703 was great, check this out, the possibilities are
becoming endless.
http://www.volumerates.com/product/tp-link-wr710n-mini-pocketable-11n-150-mbps-wireless-broadband-router-with-dual-lan-connectors-101283
Who votes for a small gateway to service a small # of MP's ?
does anyone know the difference between the TL-WR703N and the TL-MR3020
(http://www.tp-link.com/en/products/details/?categoryid=218&model=TL-MR3020)
I don't find anything concrete on openwrt.org
Thanks,
-Graham-
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-telco-dev@googlegroups.com.
To unsubscribe from this group, send email to village-telco-dev+unsubscribe@googlegroups.com.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
Hello All
For anyone interested in getting started with one of these TP-Link TL-WR703N devices, following is a brief HowTo on getting it going with OpenWRT.
Regards
Terry
A. Flashing the TL-WR703N
-----------------------------------------
The device can be reflashed using the web interface of the device.
As shipped from the factory, the web user interface is in Chinese language, but it is fairly easy to find the
firmware up load page.
The OpenWRT firmware image can be downloaded from here:
http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin
1. Power the device up and connect a PC configured so it can see the device on its default IP address on 192.168.1.1
2. Point your web browser to this address to get the login page. Credentials are 'admin' and 'admin'
3. When you are logged in, select the last item from the menu on the left.
4. Select from the sub-menu items till you find the page for firmware upload.
The URL is http://192.168.1.1/userRpm/SoftwareUpgradeRpm.htm
It will show a text box to specify the file to be uploaded. A screen shot is attached.
Be careful as there is a similar page that is for uploading a saved configuration page.
5. Click on the button to the right of the text box to start the upgrade process.
6. The process takes a few minutes, then the device will restart (blue LED flashes).
7. After the device has restarted (the blue LED stops flashing and is steady on) you should be able to telnet to 192.168.1.1
B. Using OpenWRT and Webif
--------------------------------------------
1. Telnet to default address of 192.168.1.1
2. Set the root password and exit
3. SSH to 192.168.1.1
4. Edit /etc/config/network to set IP, gateway and dns so it can get to the internet through your LAN. Example file below.
5. Restart the box and ssh back in.
6. Run the following commands:
# opkg update
# opkg install webif
# openssh-sftp-server
7. Rename /etc/httpd.conf to httpd.conf.bak
(This removes login from web i/f which doesn't work)
8. Copy /etc/init.d/webif to webif.bak
9. Edit /etc/init.d/webif to just the basic entries to start and stop uhttpd as shown below.
10. Stop the web server with:
# killall uhtpd
Start the web server:
# /etc/init.d/webif start
11. Point your browser to the device address to get the XWRT page.
12. Select Network/Wireless from the menu to set up the wireless configuration.
The AP mode works for me but I can't get the Client or Ad Hoc modes working as yet.
13. Reboot to check that the web server and AP come up correctly.
14. Browse to the file system from Nautilus (in Ubuntu)
Select Places/Connect to Server/
Select SSH
Enter IP of the TPLink device
Enter Username 'root'
Click Connect and enter root password when prompted
-----------------------------
# /etc/config/network
config 'interface' 'loopback'
option 'ifname' 'lo'
option 'proto' 'static'
option 'ipaddr' '127.0.0.1'
option 'netmask' '255.0.0.0'
config 'interface' 'lan'
option 'ifname' 'eth0'
option 'type' 'bridge'
option 'proto' 'static'
option 'ipaddr' '192.168.1.201'
option 'netmask' '255.255.255.0'
option 'dns' '8.8.8.8'
option 'gateway' '192.168.1.254'
--------------------------------
#!/bin/sh /etc/rc.common
#
# /etc/init.d/webif
START=90
start() {
uhttpd -p 80 -h /www &
}
stop() {
killall uhttpd
> Hello how are you doing, i am having problem with tplink cant get webif on
> it when i type 192.168.1.1 it show me blank page.
use https:// instead of http://
Cheers,
Elektra
----- Original Message -----
From: "elektra" <onel...@gmx.net>
To: <village-...@googlegroups.com>
> --
> You received this message because you are subscribed to the Google Groups
> "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to
> village-telco-...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/village-telco-dev?hl=en.
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 6815 (20120121) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 6815 (20120121) __________
Sent from my iPhone
Try setting your laptop to 172.31.255.xxx and browsing to the fallback
IP address at 172.31.255.254 on the MP.
Cheers... Steve
--
Hi Soumaila
Which firmware version did you flash on to the device?
What is the name of the .bin file that you used?
Also what firmware was on the device before you flashed it?
If you used sysupgrade to flash the device, did you use the -n flag?
Regards
Terry
--
Hi Soumalia
What version of firmware do you have running on the device?
When you say the device is full I assume you mean the flash memory is full because you have loaded additional packages with opkg.
The best way forward is probably to reflash the device with the SECN-1.1 firmware version SN1-7
To do this, copy the .bin file to /tmp with scp, then execute the command
sysupgrade -v -n <filename>
This version of the firmware supports additional usb devices and is set up to allow additional packages to be installed in usb memory.
Regards
Terry
Exactly which .bin file did you use to flash the device?
The default OpenWrt image configures the device as an AP but with the wireless disabled.
Have a look at the config file /etc/config/wireless to see what the settings actually are. Also look at the network config file in the same directory to see how the network is set up.
The same info is present in the Luci web interface but is spread over several pages.
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/village-telco-dev/-/tppd7M3xf7MJ.
i'm trying to follow these instructions, but I don't know what a lot of the steps mean. I've floundered my way to part B. Using OpenWRT and Webif step 4. how do i do this? i don't know how to edit it. i'm assuming i do this with the ssh connection right? also, do i just use the example file exactly? if not, where can i find an explanation of what each thing is / what to change it to?
--
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/village-telco-dev/-/t1K7lGmcZRIJ.
Hi David
Could you post the contents of the network config file please?
Your other question sounds like you are considering something like a wifi repeater. There are ways to do this but they are somewhat problematic in practice.
One of the ideas behind the SECN firmware we have developed is to be able to build arbitrarily large wifi cells using mesh networking to link the various nodes together to route data around the mesh in a predictable manner.
Regards
Terry
I was just thinking that it would be cool if the device could not only connect to a network, but rebroadcast it as well, to give it a larger useful range. It seems like this shouldn't be very hard to do. What would this type of configuration be called?
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/village-telco-dev/-/MC6Kx819vo0J.