@kekra said:
Yes, phase 2 requires a bit of ‘brute-forcing’. @voncount - as you mentioned the Windows error before, it’s in this case the equivalent of the error you see now on Linux.I finally managed to make the native client on Windows and the strong bird on Linux behave in the same way. Did the ‘brute-forcing’ on Windows and then confirmed on Linux. With hindsight, it might have been easier to automate on Linux, but I am more familiar with that stuff on Windows.
There is a one parameter with various ‘parts’ that require ‘brute-forcing’.
But while I get a stable and ‘quick’ ‘association’ both of my clients cannot make use of it yet when they fire up the ‘next stage’ of this type of V**. Might be a glitch in the ‘next stage’ config or something fundamental - common to two otherwise very different test systems.
Thanks! I got it on Linux with a bit of help (and discovered mm along the way - thanks schex), though I’m not sure how I’d go back and repeat on Windows. I at least don’t get an error when I fire up that bird on Linux, I guess I should go test that next stage.