Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • State Verified Answer
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 677 subscribers
  • Views 2275 views
  • Users 0 members are here
Related

Raspberry Pi B+ wi-fi slowdown

screamingtiger

SO I boot my pi, and ping the wireless router (gateway).  I get nice times of 10s and no drops.

 

After a while, using SSH it starts dropping packets and the ping to the gateway gets up to 1000ms.  A reboot fixes it for awhile.

 

Its not open to the outside world.  Processor shows low usage.

 

Using an EDIMAX wifi dongle.

 

Ideas?

Parents
  • 0

    Instead than an idea I suggest a possibility: it may depend on the gateway that - I suppose - It is the main gateway and the ADSL connection too. I experienced almost the same problem with the master PI on the Meditech project but I also discovered that this was only when the data packets was going to the router to be addressed to other machines. Then it was not occurring inside of the Meditech networks, where the gateway is a Raspberry PI instead of the main LAN router.

    Beside this verifications I also noted that after a certain period of inactivity - keeping the connection up - between a Mac and the main Raspberry PI, both machines connected to the same LAN with the ADSL router as the gateway some slowdown occurred as I was trying again when starting something from the Mac on the Raspberry via SSH over terminal.

     

    My actual conclusion is that this may depend on the fact that the PI after a certain period of inactivity maybe goes in a sort of power-saving mode (should be investigated, I am not 100% sure where I read something about this). When the network connection is awaken, linux machines like the OSX of the Mac simply adapt the packages transmission and the PI in a couple of seconds re-enable all the sleeping services and the connection restarts at the expected speed.

    On the router side instead, as it is probably not equipped with a very good software, as the speed goes low then it simply keep this IP packets transmission speed low.

     

    I suggest two test that maybe useful for alls:

     

    • After the connection goes slow for one of the reasons you mentioned, ignore this fact, continue working for a reasonable time (i.e. half one hour or more if possible) and see if the router aligns again it s speed.
    • Instead of rebooting try simply to stop and restart the networking on the PI and see if the speed remain slow or not (sudo /etc/init.d/networking stop then sudo /etc/init.d/networking start) and see if the same problem occur again and if the slow state persists.

    Then with these information maybe we can investigate more in-detph enabling some specific logs on the network behaviour.

     

    Enrico

Reply
  • 0

    Instead than an idea I suggest a possibility: it may depend on the gateway that - I suppose - It is the main gateway and the ADSL connection too. I experienced almost the same problem with the master PI on the Meditech project but I also discovered that this was only when the data packets was going to the router to be addressed to other machines. Then it was not occurring inside of the Meditech networks, where the gateway is a Raspberry PI instead of the main LAN router.

    Beside this verifications I also noted that after a certain period of inactivity - keeping the connection up - between a Mac and the main Raspberry PI, both machines connected to the same LAN with the ADSL router as the gateway some slowdown occurred as I was trying again when starting something from the Mac on the Raspberry via SSH over terminal.

     

    My actual conclusion is that this may depend on the fact that the PI after a certain period of inactivity maybe goes in a sort of power-saving mode (should be investigated, I am not 100% sure where I read something about this). When the network connection is awaken, linux machines like the OSX of the Mac simply adapt the packages transmission and the PI in a couple of seconds re-enable all the sleeping services and the connection restarts at the expected speed.

    On the router side instead, as it is probably not equipped with a very good software, as the speed goes low then it simply keep this IP packets transmission speed low.

     

    I suggest two test that maybe useful for alls:

     

    • After the connection goes slow for one of the reasons you mentioned, ignore this fact, continue working for a reasonable time (i.e. half one hour or more if possible) and see if the router aligns again it s speed.
    • Instead of rebooting try simply to stop and restart the networking on the PI and see if the speed remain slow or not (sudo /etc/init.d/networking stop then sudo /etc/init.d/networking start) and see if the same problem occur again and if the slow state persists.

    Then with these information maybe we can investigate more in-detph enabling some specific logs on the network behaviour.

     

    Enrico

Children