Új hozzászólás Aktív témák

  • jpeter82

    csendes tag

    válasz vargalex #1619 üzenetére

    a 0 érték itt mit jelent? kikapcsolja vagy automatán választ?

    még egy írás erről (ddwrt fórumban):

    ACK timing is also a throughput controller, too high and your devices will literally be "waiting" too long and time will be passing with them at idle. Too low and active transmissions could be cut off causing retransmissions which create overhead, that lowers throughput. The AP sends a packet and all clients must wait for XXX time, where XXX is the ACK timing, the client then receives that packet and responds to the AP with an ACK(nowledgement), AP sees the AP then finally everyone is free to transmit.
    Most users want this between 0 - 2000 (2.4/5 GHz), the distance used is meters and needs to be doubled the distance of the furthest client from the AP (plus some headroom). Doubled because the signal travels to the client and back, double the distance. In earlier builds with the older madwifi driver reducing ACK from default 2000 to 1500 caused a throughput increase of 0.6 Mbps - 1 Mbps, though with modern builds (r18000+) using the new ath9k driver, along with the internal changes to ACK timing, reducing to 1500 does about nothing for throughput, one would have to drop below 900m at least, as well with the current ath9k builds an ACK timing of 0 DOES disable it completely like on Broadcom, this is generally the new best setting. But if you do not disable ACK timing remember an ACK timing too low can cause issues described above.
    Long distance links, such as 2 KM+ will need to increase this setting accordingly. 4000m for 2km, 6000m for 3km, and so on.

    forrás: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=171400&postdays=0&postorder=asc&start=15&sid=2da0c69548e01b675e622a0d422e92fb

Új hozzászólás Aktív témák