I'm seeing this striking detail:<br><br>- 2 separate Commotion nodes hanging off the near end of the 5GHz P2P link from BKFiber<br>- I unplugged the Nano and then Internet access worked great on the Pico.<br><br>How close together physically are the Nano and Pico running DR1.1? Also, I assume they're on the same channel too?<br>
<br>Since both Commotion nodes are still operating as wired gateway nodes, regardless of DHCP settings, I think it's very likely they are interfering with each other. I had similar problems (i.e. super long latency) try to operate more than one node on the same mast on the same channel.<br>
<br>You want to have 2 wired Commotion nodes within very close proximity, they will either need to operate on different channels, or one will have just be a repeater node (and with its TX power turned way down).<br><br><div class="gmail_quote">
On Wed, Jun 5, 2013 at 10:19 AM, Preston Rhea <span dir="ltr"><<a href="mailto:prestonrhea@opentechinstitute.org" target="_blank">prestonrhea@opentechinstitute.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Moving this to commotion-dev (original recipients on BCC).<br>
<br>
My setup was:<br>
<br>
(BKFiber point-to-point Nano LoCo 5GHz gateway ) >>> [[ETHERNET<br>
SWITCH]] > 2 separate Commotion nodes: // (1 PicoStation w/ DR1.1,<br>
powered-on when plugged into switch then set to DCHP Client only) //<br>
(1 NanoStation M2 w/ DR1.1, powered-on when plugged into switch then<br>
set to DHCP Client only). The two Commotion nodes were meshed at about<br>
ETX 7.5.<br>
<br>
When both nodes were powered on in this way, I got erratic times of<br>
very high latency (as seen in the traceroutes below) mixed with times<br>
of normal operation, while associated with the Pico. After I saw<br>
Andy's report of the same problems, I unplugged the Nano and then<br>
Internet access worked great on the Pico.<br>
<br>
<br>
On Wed, Jun 5, 2013 at 11:09 AM, Dan Staples<br>
<<a href="mailto:danstaples@opentechinstitute.org">danstaples@opentechinstitute.org</a>> wrote:<br>
> Thanks for reporting these issues, all. I am fully available today to<br>
> investigate these issues.<br>
><br>
> I just tried putting up a DR1 node, and hitting it with about 15<br>
> different website loads simultaneously, from two different computers.<br>
> All the tabs were redirected to the captive portal within a second, and<br>
> the CPU usage went to about 85%-95% for just about a second or two, then<br>
> went back down to idle levels. Absolutely no lock-up at all. Could you<br>
> provide more information on the architecture of the network, and any<br>
> other relevant info? How many gateways were there? About how many people<br>
> were connecting to each of the nodes? Were they all trying to access the<br>
> admin interface, or go to outside websites? If the latter, were they all<br>
> captive portaled?<br>
><br>
> I have two picos with me now, and will look into the latency issue as well.<br>
><br>
> On 06/04/2013 02:07 PM, Preston Rhea wrote:<br>
>> I unplugged the rooftop router from power, so now there's only the<br>
>> indoor AP (RHI HQ). Seems to be working fine now.<br>
>><br>
>> FWIW, the two nodes were connected by a switch, which was also<br>
>> connected to the BKFiber gateway on the roof.<br>
>><br>
>> On Tue, Jun 4, 2013 at 2:03 PM, Preston Rhea<br>
>> <<a href="mailto:prestonrhea@opentechinstitute.org">prestonrhea@opentechinstitute.org</a>> wrote:<br>
>>> Just finished updating RHI WiFi 3 (roof of RHI) and the internal AP<br>
>>> with DR1.1. Worked fine at first, but for the last 10 minutes, I've<br>
>>> definitely been noticing (2). Traceroutes:<br>
>>><br>
>>> 41 packets transmitted, 34 received, 17% packet loss, time 42111ms<br>
>>> rtt min/avg/max/mdev = 411.582/4302.645/11538.744/3289.556 ms, pipe 10<br>
>>> preston@preston-ThinkPad-X220:~$ traceroute 8.8.8.8<br>
>>> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets<br>
>>> 1 RHI-HQ583780718.local (101.203.201.1) 1930.986 ms 1931.265 ms 1931.370 ms<br>
>>> 2 192.168.2.1 (192.168.2.1) 1932.298 ms 1932.847 ms 1937.548 ms<br>
>>> 3 192.168.12.1 (192.168.12.1) 2051.621 ms 2051.727 ms 2051.857 ms<br>
>>> 4 66.109.17.35 (66.109.17.35) 2051.963 ms 2117.879 ms 2117.949 ms<br>
>>> 5 4.28.73.69 (4.28.73.69) 2785.550 ms 2785.619 ms 2785.623 ms<br>
>>> 6 4.69.155.142 (4.69.155.142) 2785.591 ms 166.634 ms 611.093 ms<br>
>>> 7 <a href="http://GOOGLE-INC.edge1.NewYork1.Level3.net" target="_blank">GOOGLE-INC.edge1.NewYork1.Level3.net</a> (4.71.172.86) 609.147 ms<br>
>>> 656.012 ms <a href="http://GOOGLE-INC.edge1.NewYork1.Level3.net" target="_blank">GOOGLE-INC.edge1.NewYork1.Level3.net</a> (4.71.172.82) 659.011<br>
>>> ms<br>
>>> 8 72.14.238.232 (72.14.238.232) 661.644 ms <a href="tel:209.85.255.68" value="+12098525568">209.85.255.68</a><br>
>>> <a href="tel:%28209.85.255.68" value="+12098525568">(209.85.255.68</a>) 663.585 ms 72.14.238.232 (72.14.238.232) 661.615 ms<br>
>>> 9 72.14.236.206 (72.14.236.206) 663.549 ms 72.14.236.208<br>
>>> (72.14.236.208) 661.766 ms 663.459 ms<br>
>>> 10 72.14.239.93 (72.14.239.93) 663.480 ms 209.85.249.11<br>
>>> (209.85.249.11) 772.857 ms 72.14.239.93 (72.14.239.93) 772.861 ms<br>
>>> 11 72.14.238.18 (72.14.238.18) 772.849 ms 772.829 ms 72.14.238.16<br>
>>> (72.14.238.16) 772.742 ms<br>
>>> 12 216.239.49.145 (216.239.49.145) 163.840 ms 72.14.232.21<br>
>>> (72.14.232.21) 20.100 ms *<br>
>>> 13 * * *<br>
>>> 14 * * *<br>
>>> 15 * * *<br>
>>> 16 * * *<br>
>>> 17 * * *<br>
>>> 18 <a href="http://google-public-dns-a.google.com" target="_blank">google-public-dns-a.google.com</a> <a href="tel:%288.8.8.8%29%20732.816" value="+18888732816">(8.8.8.8) 732.816</a> ms 732.773 ms 732.762 ms<br>
>>> preston@preston-ThinkPad-X220:~$ traceroute 8.8.8.8<br>
>>> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets<br>
>>> 1 RHI-HQ583780718.local (101.203.201.1) 4103.799 ms 4861.648 ms 5457.216 ms<br>
>>> 2 192.168.2.1 (192.168.2.1) 5457.872 ms 5458.274 ms 5458.838 ms<br>
>>> 3 192.168.12.1 (192.168.12.1) 5469.609 ms 5470.288 ms 5471.173 ms<br>
>>> 4 66.109.17.35 (66.109.17.35) 5471.846 ms 5472.272 ms 5473.052 ms<br>
>>> 5 <a href="http://vlan1065.car4.NewYork1.Level3.net" target="_blank">vlan1065.car4.NewYork1.Level3.net</a> (4.28.73.69) 6685.639 ms<br>
>>> 6685.630 ms 6685.617 ms<br>
>>> 6 <a href="http://ae-3-80.edge1.NewYork1.Level3.net" target="_blank">ae-3-80.edge1.NewYork1.Level3.net</a> (4.69.155.142) 6685.603 ms<br>
>>> 68.883 ms 30.913 ms<br>
>>> 7 <a href="http://GOOGLE-INC.edge1.NewYork1.Level3.net" target="_blank">GOOGLE-INC.edge1.NewYork1.Level3.net</a> (4.71.172.82) 31.692 ms<br>
>>> 32.169 ms <a href="http://GOOGLE-INC.edge1.NewYork1.Level3.net" target="_blank">GOOGLE-INC.edge1.NewYork1.Level3.net</a> (4.71.172.86) 34.990<br>
>>> ms<br>
>>> 8 209.85.255.68 (209.85.255.68) 109.264 ms 72.14.238.232<br>
>>> (72.14.238.232) 74.341 ms 74.656 ms<br>
>>> 9 72.14.236.206 (72.14.236.206) 78.480 ms 72.14.236.208<br>
>>> (72.14.236.208) 78.672 ms 72.14.236.206 (72.14.236.206) 78.890 ms<br>
>>> 10 209.85.249.11 (209.85.249.11) 79.985 ms 80.466 ms 72.14.239.93<br>
>>> (72.14.239.93) 81.046 ms<br>
>>> 11 72.14.238.16 (72.14.238.16) 81.554 ms 81.743 ms 81.907 ms<br>
>>> 12 216.239.49.145 (216.239.49.145) 63.974 ms 72.14.232.21<br>
>>> (72.14.232.21) 44.343 ms 46.145 ms<br>
>>> 13 <a href="http://google-public-dns-a.google.com" target="_blank">google-public-dns-a.google.com</a> (8.8.8.8) 36.717 ms 36.732 ms 37.026 ms<br>
>>> preston@preston-ThinkPad-X220:~$ traceroute 8.8.8.8<br>
>>> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets<br>
>>> 1 RHI-HQ583780718.local (101.203.201.1) 138.704 ms 138.680 ms 138.672 ms<br>
>>> 2 192.168.2.1 (192.168.2.1) 138.757 ms 138.849 ms 138.950 ms<br>
>>> 3 192.168.12.1 (192.168.12.1) 139.050 ms 139.138 ms 139.231 ms<br>
>>> 4 66.109.17.35 (66.109.17.35) 139.303 ms 139.408 ms 139.497 ms<br>
>>> 5 * * *<br>
>>> 6 4.69.155.142 (4.69.155.142) 141.727 ms 20.589 ms 43.078 ms<br>
>>> 7 <a href="http://GOOGLE-INC.edge1.NewYork1.Level3.net" target="_blank">GOOGLE-INC.edge1.NewYork1.Level3.net</a> (4.71.172.82) 20.595 ms 1391.805 ms *<br>
>>> 8 * <a href="tel:209.85.255.68" value="+12098525568">209.85.255.68</a> <a href="tel:%28209.85.255.68" value="+12098525568">(209.85.255.68</a>) 1459.420 ms 72.14.238.232<br>
>>> (72.14.238.232) 1459.389 ms<br>
>>> 9 72.14.236.208 (72.14.236.208) 1459.017 ms * *<br>
>>> 10 * * *<br>
>>> 11 * * 72.14.238.16 (72.14.238.16) 534.701 ms<br>
>>> 12 72.14.232.21 (72.14.232.21) 615.623 ms 216.239.49.145<br>
>>> (216.239.49.145) 535.296 ms 72.14.232.21 (72.14.232.21) 7653.385 ms<br>
>>> 13 <a href="http://google-public-dns-a.google.com" target="_blank">google-public-dns-a.google.com</a> (8.8.8.8) 7559.047 ms 7558.923 ms<br>
>>> 7759.846 ms<br>
>>><br>
>>> On Tue, Jun 4, 2013 at 1:55 PM, Andy Gunn<br>
>>> <<a href="mailto:andygunn@opentechinstitute.org">andygunn@opentechinstitute.org</a>> wrote:<br>
>>>> We definitely ran in to some issues in the past few days while<br>
>>>> installing, and doing test deployments on battery packs. Will, please<br>
>>>> fill in my gaps:<br>
>>>><br>
>>>> 1. The nodes cannot handle more than a _single_ http request at one<br>
>>>> time. If more than one person tries to log on to the admin interface, or<br>
>>>> even browse the local application portal at once, the entire node locks<br>
>>>> up, and will usually drop all connections. Caused huge headaches while<br>
>>>> we were trying to diagnose. Recommending completely disabling local<br>
>>>> splash pages, and perhaps even the local application portal.<br>
>>>><br>
>>>> 2. There may be some conditions (lots of connections, too many nodes in<br>
>>>> close proximity, not sure), that cause extremely large latencies (2 to<br>
>>>> 10 seconds) at irregular intervals. Needs to be repeated and verified.<br>
>>>><br>
>>>> Other that that, I think there were a few small things, but this is just<br>
>>>> an initial brain dump. Will can report back as well with better detail.<br>
>>>><br>
>>>> Dan - I will assume that you will pass this information on to the rest<br>
>>>> of the Commotion team.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On 06/03/2013 10:54 AM, Preston Rhea wrote:<br>
>>>>> Hey Dharamsala crew,<br>
>>>>><br>
>>>>> How is it working out in the field? Plan is to start loading it in Red<br>
>>>>> Hook tomorrow, so would be great to know!<br>
>>>>><br>
>>>>> Hope all is well in the air up there,<br>
>>>>><br>
>>>>> Preston<br>
>>>>><br>
>>>>> --<br>
>>>>> Preston Rhea<br>
>>>>> Program Associate, Open Technology Institute<br>
>>>>> New America Foundation<br>
>>>>> <a href="tel:%2B1-202-570-9770" value="+12025709770">+1-202-570-9770</a><br>
>>>>> Twitter: @prestonrhea<br>
>>>>><br>
>>>> --<br>
>>>><br>
>>>> Andy Gunn, Field Engineer<br>
>>>> Open Technology Institute, New America Foundation<br>
>>>> <a href="mailto:andygunn@opentechinstitute.org">andygunn@opentechinstitute.org</a> | <a href="tel:202-596-3484" value="+12025963484">202-596-3484</a><br>
>>><br>
>>><br>
>>> --<br>
>>> Preston Rhea<br>
>>> Program Associate, Open Technology Institute<br>
>>> New America Foundation<br>
>>> <a href="tel:%2B1-202-570-9770" value="+12025709770">+1-202-570-9770</a><br>
>>> Twitter: @prestonrhea<br>
>><br>
>><br>
<span class="HOEnZb"><font color="#888888">><br>
> --<br>
> Dan Staples<br>
><br>
> Open Technology Institute<br>
> <a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
><br>
<br>
<br>
<br>
--<br>
Preston Rhea<br>
Program Associate, Open Technology Institute<br>
New America Foundation<br>
<a href="tel:%2B1-202-570-9770" value="+12025709770">+1-202-570-9770</a><br>
Twitter: @prestonrhea<br>
_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
314-246-9434<br></div>