Jump to content

Pineapple NANO client mode poor performance


CTflex
 Share

Recommended Posts

I purchased a Pineapple NANO with the included RaLink RT5370 tertiary radio. I've connected the radio and confirmed it's recognized as wlan2 and I'm able to connect to my home wireless access point with it. However, when I enable PineAP and connect to an SSID on the Pineapple using a test client, the test client is only able to access the internet briefly before it stops working completely.

If I SSH into the Pineapple and ping an external address (eg. 8.8.8.8), the ping times will begin around 40-50 ms but will quickly start increasing until they hit 30000 ms or higher and I start dropping pings. However, if I ping the Pineapple's default gateway (my home wireless access point), ping response times are reasonable and do not increase.

I have tested this by powering the NANO with both the included Y-cable and the Anker PowerCore Slim 5000 battery and I get the same results with both power sources.

It seems like a routing or iptables issue but I haven't made any customizations to the default Pineapple config. Does anyone have any experience getting client mode to work on a NANO using a tertiary radio (wlan2) in addition to PineAP? Thanks in advance!

Link to comment
Share on other sites

Interestingly, wlan2 is working much better today but now wlan0 is acting like wlan2 was yesterday. I removed wlan2 from the NANO, connected a laptop via the provided Y cable, factory reset the NANO, and then connected a single wireless client via the management network. When I ping the wireless client from either the laptop or the NANO itself, I get similar ping results. The NANO and the test wireless client approximately 5' apart.

Pinging 172.16.42.154 with 32 bytes of data:
Reply from 172.16.42.154: bytes=32 time=608ms TTL=64
Reply from 172.16.42.154: bytes=32 time=2405ms TTL=64
Reply from 172.16.42.154: bytes=32 time=4ms TTL=64
Reply from 172.16.42.154: bytes=32 time=2225ms TTL=64
Reply from 172.16.42.154: bytes=32 time=4ms TTL=64
Reply from 172.16.42.154: bytes=32 time=2065ms TTL=64
Reply from 172.16.42.154: bytes=32 time=5ms TTL=64
Reply from 172.16.42.154: bytes=32 time=1683ms TTL=64
Reply from 172.16.42.154: bytes=32 time=3ms TTL=64
Reply from 172.16.42.154: bytes=32 time=409ms TTL=64
Reply from 172.16.42.154: bytes=32 time=2162ms TTL=64
Reply from 172.16.42.154: bytes=32 time=3ms TTL=64
Reply from 172.16.42.154: bytes=32 time=1246ms TTL=64
Reply from 172.16.42.154: bytes=32 time=3ms TTL=64
Reply from 172.16.42.154: bytes=32 time=1749ms TTL=64
Reply from 172.16.42.154: bytes=32 time=6ms TTL=64
Reply from 172.16.42.154: bytes=32 time=1234ms TTL=64
Reply from 172.16.42.154: bytes=32 time=4ms TTL=64
Reply from 172.16.42.154: bytes=32 time=754ms TTL=64
Reply from 172.16.42.154: bytes=32 time=75ms TTL=64

Ping statistics for 172.16.42.154:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 2405ms, Average = 832ms

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...