octopus
Part of the Furniture
I think https://bostad.stockholm.se/Minasidor/login/ have nothing to do with it. Rediction to Bankid is your problem. They may have som security kicks in.
I think https://bostad.stockholm.se/Minasidor/login/ have nothing to do with it. Rediction to Bankid is your problem. They may have som security kicks in.
I think this time it is you ho did not read what @octopus said...I have to say no on that - at the point when you select what kind of "BankID" you like to select for starting the login process has not started at all. And, again, it works after switching DoT Off and then ON again - if "BankID" would be that problem you suggests, then it would not work. And yet again, if I do this on my mobile, disconnected from the AX88, it always works.
Okay, if you have that kind of problem i suggest you set up a packet sniffer Wireshark and se if packet are blocket/redicted in some way.I have to say no on that - at the point when you select what kind of "BankID" you like to select for starting the login process has not started at all. And, again, it works after switching DoT Off and then ON again - if "BankID" would be that problem you suggests, then it would not work. And yet again, if I do this on my mobile, disconnected from the AX88, it always works.
When I clicked the blue button I got:
login003.stockholm.se’s server IP address could not be found.
I was following blocked domains in Diversion and nothing came up. I'm using cloudflare for DoT and 384.15.
Still on 384.13 here, been stable so haven't felt the need to update constantly, now we are on 384.15 I think I will update though. Will do a full reset as well seen as I'm jumping a version.
Again you fail to understand. I do NOT use DoT in my mobile, where did you get that assumption from - do you even read what I wrote?
I assume this is WPA3 triggered warnings? Seems like it can not detect the encryption
Still on 384.13 here, been stable so haven't felt the need to update constantly, now we are on 384.15 I think I will update though. Will do a full reset as well seen as I'm jumping a version.
I am still on .12 release... Wanne start clean on .15... Do I just do update, then afterwards a factory default? Or first factory and then upgrade?...
perfect, thnx for feedback , gonna do it laterReset must always be done after, so that the default settings your router inherits will be those of that new firmware.
You have an answer not being a DoT issue but more a DNSSEC (combined) one by @MarkRH in post #207, so it is the domain/site "fault" for not supporting it.Okay, DoT is now turned off permanently. This way DNS name lookups always works, and the site I mention above somewhere works 100% of the time. Problem solved - and anyone that like to guess why DoT does not work can do so - but it will be without my help.
PS! Anyone trying to convince me the site has problem, can think - again - about the fact that it does work after cycling DoT OFF/ON - for a limited time at least, then start to fail again.
Im on 384.12. Let me know Wifi performance of 2.4 and 5ghz if you experience any drops etc.
Shouldn't be necessary.
On my AC86U I can only select "Auto" (channel) in the GUI, so I will try the nvram trick. Thanks for that!
This morning several devices (Homey, Pi) were again disconnected...
I see 100/80 & 112/80 in acsd.log; I believe both are indeed DFS in Europe?
Which channel should be safe? (Where is a good overview?)
PS! Anyone trying to convince me the site has problem, can think - again - about the fact that it does work after cycling DoT OFF/ON - for a limited time at least, then start to fail again.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!