[Commotion-dev] Issues with Picostation with both 1.1 and 1.2rc

[Josh King]

As Dan alluded to, the reboots are most likely due to the out-of-memory
condition that was mentioned in the 1.2rc1 email. A device like a
picostation is going to be somewhat more susceptible to that, but we're
working on fixing that particular bug before the 1.2 final release.

On 04/13/2015 09:56 AM, Dan Staples wrote:
> The configuration of the Pico images should be identical to the Rocket images (they are produced in the same compilation). I'm guessing you're running into an issue that a lot of folks have, which is due to an often confusing feature.
> 
> When the node boots up, it attempts to get a DHCP lease for its primary ethernet interface. If it does, the ethernet interface is put into the WAN zone and configures itself as a gateway. If it doesn't, it puts itself in the same bridge as the access point, and the bridge assigns itself a 10.x.x.x IP address. To change from one mode to the other, however, requires rebooting the node. So try rebooting the Rocket and see if that changes things.
> 
> As for rebooting every few minutes, this is simply a limitation of the Picostation hardware. It has very little RAM and is likely rebooting due to low memory conditions. We actually recommend against using Picostations when you need a device to both mesh and provide an access point. Rockets are a better alternative, as are Nanostations if you want a directional antenna.
> 
> I hope this helps, and let us know if the issues persist.
> 
> Dan
> 
> On 04/13/2015 09:44 AM, Adam Longwill wrote:
>> Quick question.
>>
>> I have been battling with a Picostation all weekend to act like how we configure our Rockets and I am having NO success. I think it's a bug but I wanted to pick everyone else's mind.
>>
>> The Rocket's can have a static IP address set on the WAN without a problem, allowing them to be statically assigned on our office's LAN with a dependable IP address.
>>
>> The Pico... by default it has no WAN IP address and it shares 2 IPs on its LAN interface, the 10. address generated from it's MAC and the 169 address. Whenever I try to give the WAN a static, it stops responding to all traffic to it: HTTP, ping, nothing. Although, using TCPdump I can see that it has indeed taken the new LAN-range IP address.
>>
>> What in the world is going on with these things? Does anyone else have this issue?
>>
>> Are these meant to be used in a different way than Rockets? This issue is on both 1.1 and 1.2.
>>
>> Also, it reboots every few minutes.
>>
>> Thoughts?
>>
>> Adam L.
>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>
> 

-- 
Josh King
Lead Technologist
The Open Technology Institute
http://opentechinstitute.org
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20150413/6ba53941/attachment.sig>