Recent content by followmsi

Nexus 7 was similar .. connecting/disconnecting all the time. At some point the device did "see" 5GHz networks only. After full reboot of the Android tablet and forgetting/re-adding network configuration it finally worked. Now it's connected to hidden 2.4GHz - like before - all good ! Thanks !

Just did edit my text above :) It's an (older) Android tablet .. Nexus 7 2013 running lineage-18.1. After several tests 2.4GHz was finally connecting too.

Updated primary router (RT-AC68U) to 49D6 today. In case of 5GHz and media bridge connections all is (still) good. Like mentioned by @john9527 .. when using version 49D6 in router mode there are some 2.4GHz connection issues. In my case it's just one 2.4GHz device which is not connecting...

Tested Development version 49D6 on RT-AC68P in media bridge mode. No problems this time .. now the device connects to primary RT-AC68U in router mode. (still running 49E4) Will update primary router to 49D6 in the next days and check again. Thanks for all your work !

Yep - it's working now ! Just flashed 48E1 on RT-AC68P Media Brigde and all is working like on 46E9 .. no IP connectivity issues anymore ! The main RT-AC68U in Router mode is still running 46E9. Thanks a lot !

Thanks for looking into this issue ! Pls take your time .. pls let me know if I can help testing. Cheers

@john9527 Hi John Like always .. Thanks a lot for all your work ! I have RT-AC68U (v1) in Router Mode and RT-AC68P as Media Bridge .. using this setup since years. I do upgrade all your firmware releases on both devices .. starting always on media bridge first. The media bridge is configured...

Thanks for testing and proving the current situation ! Would love to have openssl11 binary in Johns fork as well .. maybe at some point - when he is back :) With TLS min version 1.2 the connection to 1.1.1.1 is rock stable .. like it used to be before. Realized the DNS drops since a few...

Stubby uses chiperlist for tls 12 and ciphersuite for tls 13. I added tls min version to make connection stable with 1.1.1.1. No idea why John stock config (tls min ver 13) is not working (anymore). That's why I am asking here :) EDIT: DNS resolution works with tls min ver 13 .. but quite...

For stubby John has built and linked openssl 1.1 static lib. As I understood in Merlin build there is also openssl11 binary to test openssl standalone. In John's fork there is no openssl11 binary just the staitc lib for stubby.

Here you are .. (removed " resolvconf: "/tmp/resolv.conf" " already ) The SNB forum seems not to like the code .. had to use pastebin. https://pastebin.com/1TF7EHF6 Thanks

Qickly tested this stuff .. The stubby.postconf script is adding .. resolvconf: "/tmp/resolv.conf" in to stubby.yml .. same if you add the line to stubby.yml.add .. 2 ways to reach the same result. Nevertheless it's not working .. still get tons of timeouts .. tail -f...

Like mentioned above .. have a try to add "tmp/resolv.conf". Will test it later today .. Hope to keep stable tls 13 connection with cloudflare.

Same here .. cloudflare issues started a few weeks ago. Was running 39e3 since April .. Switched to 40e9 for testing .. Same problem. Now I allowed tls 12 to make it stable again .. (tls_min_version: GETDNS_TLS1_2 into stubby.yml.add ) If you keep tls 13 you get tons of disconnects and DNS...

I want to use cloudflare too .. primary and secondary - ordered. Switched to "server only" and it seems to work fine with cloudflare. Thanks for all your work!