> Lorenzo, I've pulled out all patches related to extended ham radio > channels and ath9k is same out of openwrt 18.06.2. I replaced wpad-mini > with the full version and "option encryption psk2". In testing between a > mickrotik QRT5 and LHG5 about 10m apart (roof to office), ack_to will > float up to ~200, then settle down to ~55 -- seems about right. However, > I do not see any late ack messages in the debug logging. Shouldn't I be > seeing late acks? I can send full debug data on both sides of the fence. > Is there anything that doesn't sound right in my setup? I wanted to do > one more clean test to capture logs.
Hi Joe, this is the expected behavior since 'late acks' are triggered just when the real ack-timeout is higher than the initial default value (64us IIRC). In other words 'late acks' are necessary just on pretty long links Regards, Lorenzo > > It shouldn't matter on wpad-mini or wpad, correct? The size went from > ~500k to 727k, ouch. > > Joe > > On Thu, Feb 28, 2019 at 8:48 AM Lorenzo Bianconi < > lorenzo.bianc...@redhat.com> wrote: > > > > On Thu, Feb 28, 2019 at 1:59 AM Koen Vandeputte > > > <koen.vandepu...@ncentric.com> wrote: > > > > > > > > > > > > On 27.02.19 08:13, Lorenzo Bianconi wrote: > > > > >> <snip> > > > > > What I mean is just a p2p link running in AP-STA mode, I guess there > > is no > > > > > difference for users. Am I missing something? > > > > > > > > > > > The design of the out-of-box firmware for AREDN, there are many end > > > users that do not have IT skill set to change these settings at > > > /etc/config level. Although, we could create high level UI setting > > > options. The firmware is packaged so a "node" can boot live and will > > > simply work extending the network with no previous coordination of > > > config settings -- it can be in any logical network position: P2P, > > > P2MP, MP2P, MP2MP. Adding such a setting of this network position > > > could be a fallback option to consider, but not desirable. > > > > > > > >> Is dynack going to receive the late acks if I manage to run > > > > >> wpa_supplicant (wpad-mini?) in plaintext or key_mgmt=NONE mode? > > > > > What we really needs are authentication packets to trigger 'late > > acks' > > > > > in ibss mode. I think wpa_supplicant in plaintext is enough but I am > > not > > > > > 100% sure. > > > > > @Koen: could you please confirm it? > > > > > > > > Will try to test it asap. > > > > > > > > Regards, > > > > > > > > Koen > > > > > > > > > > I'm also working to test, but may not be for several days. > > > wpa_supplicant would be required on both ends? dynack is dependent on > > > ack's generated by wpa_supplicant? This is an upgrade issue of > > > people using old and and new versions of the firmware at the same time > > > across a larger network. > > > > Yes, you need it on both ends since late acks are detected on > > authentication > > messages in ibss mode and ack timeout estimation is done independently on > > each side. > > Could you please just try it on a single 50km link in order to double > > check if it > > works properly? > > > > Regards, > > Lorenzo > > > > > > > > Joe AE6XE > >
signature.asc
Description: PGP signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
