Hi,
Thank you for the reply but I am failing to understand how your test reflects my setup and this might be my fault not explaining well.
at the moment everything is working if I make sure the client dns is set to 192.168.0.1 (rutc50)
the original issue was caused by the fact that somehow on my phone leaving dns set as default I could not ping my static adresses; I had to manually enter 192.168.0.1 as dns so Im thinking maybe there is a bug or misconfiguration on the wifi side of the rutc since my laptop was working fine from the beginning and it is wired.
secondly I wanted to go a bit further and comment on the fact that my DNS pi (192.168.0.117) only sees requests from 192.168.0.1. That seems normal at first but it is a bit annoying since I cannot see requests from individual clients anymore.
It seems that the router is making the dns request on behalf of the client instead of forwarding the dns request from the client if you see what I mean ?
I am a bit shocked by this behavior because before owning the RUTC50 I used to own a GLinet router that supports adguard natively and I could see individual client request from their own ip so I know this is possible since it is also based on openwrt.
I also noticed from my post below that creating a new wireless interface will not set the dns to my custom dns by default; this could be IMO a security issue; I have to set my dns every time to 192.168.0.117 on the wan interface created after joining the hotspot
RUTOS should have a MASTER DNS setting that is applied by default everywhere and enforced as strict dns by default (this was possible on gl router)