[skyland]

Hi

I don't not why the ACK does not work property on any wireless link over 61 KM

I have 2 wireless link with the same problem:

- one is about 79 Km FULL LOS using 1 Avila gateworks 2348-2 and one DCMA-82 on each side the signal is -66 ,

- The other is about 94 Km FULL LOS using 1 Avila gateworks 2348-2 and one links DCMA-82 on each side the signal is -68 ,

I have 2 identical 94 km on the same direction using 2 UBIQUITI XR5 and 2 Avila gateworks 2348-2 on each side but have the same ACK problem ( ACK Timing409µs (60900m)

I have severals wireless link using Avila gateworks 2348-2 and DCMA-82 on distances between 50 Km and 60 KM and the ACK work perfectly using 20 MHZ channels but in distances up to 61 KM They work correctly only using 10 MHZ channel because the ACK have a bug and show on the 78 KM link ACK Timing409µs (60900m) on the 94 km link ACK Timing show the same 409µs (60900m)

I use the latest firmware available

[Sash]

this is a physical problem no bug!
u can get to 10mhz bandwith this will double the ack distance

[skyland]

Sash please read before post

The problem is the ACK Timing show the same 409µs (60900m) on the 94 km link and show the same 409µs (60900m) on the 74 km link.

if you Put the ACK like ( 94100) for a 94 KM link the status show the same 409µs (60900m) this is a bug

I have test today 2 mikrotik 532A running on the same direction ( 94 KM ) and they work on 20 MHZ channel the ping are very good about 1 ms and 2 ms

[Sash]

again: this is no bug!!
ack is not possible for links bigger than 60km!!

[skyland]

I try to set the ACK manually via terminal but does not work at all

root@FIREWALL DCMA-82:/etc# athctrl -i ath1 -d 94100
Setting distance on interface ath1 to 94100 meters
Could not open /proc/sys/dev/ath1/slottime for writing!
Could not open /proc/sys/dev/ath1/acktimeout for writing!
Could not open /proc/sys/dev/ath1/ctstimeout for writing!
root@FIREWALL DCMA-82:/etc#

[skyland]

I hear that is possible modify via terminal to have an unlimited ACK otherwise what is the way to correct the ACK limit using dd-wrt.

Any idea?


I make a stable 94 km wireless link using 2 mikrotik and the ping are around 1 - 2 ms , the throughput is about 14 mbps

[Sash]

its not working with ddwrt right now.

mtik uses soft ack which is proprietary n-stream stuff

[Sash]

what i hve see is that ddwrt with ath9k allows to set ack to distances over 60km. in fact ack-time gets proberly calculated even on ack settings of 100km. but this is what is see from the cli and gui.
this needs to be tested for proofing!