Running this particular script with ASH vs BASH results in totally different outcomes on my Router+Firmware (with shebang '#!/bin/sh'):
ASH -> 'No internet connection.' and in some cases 'line 105: syntax error: unexpected redirection'
BASH -> No Errors - the script execute as expected.
Kind regards.
Last edited by oh-wtf on Tue Feb 04, 2025 4:27; edited 1 time in total
I can verify this script does not work under ash. It's probably a very small change to make it compatible (besides the first line, it's most likely an expression within) but I don't really care to look for it.
While it's a handy script for many people, it's not one I'd use personally. There are better methods available that are web based. When the results report "You might have a dns leak", well that's just not enough to satisfy my requirements. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 18 Mar 2014 Posts: 13532 Location: Netherlands
Posted: Tue Feb 04, 2025 6:37 Post subject:
lexridge wrote:
I can verify this script does not work under ash. It's probably a very small change to make it compatible (besides the first line, it's most likely an expression within) but I don't really care to look for it.
While it's a handy script for many people, it's not one I'd use personally. There are better methods available that are web based. When the results report "You might have a dns leak", well that's just not enough to satisfy my requirements.
I can verify this script does not work under ash. It's probably a very small change to make it compatible (besides the first line, it's most likely an expression within) but I don't really care to look for it.
While it's a handy script for many people, it's not one I'd use personally. There are better methods available that are web based. When the results report "You might have a dns leak", well that's just not enough to satisfy my requirements.
I did make those small changes but it is not worth to bother with.
The script concludes that I have a DNS leak and I do not have one.
I found this to be the case for me as well...
Do you have a definitive and reliable method for evaluating DNS leaks from DD-WRT SSH CLI (eliminating false positives caused by browser DNS leaks) that you can share?
Yes, I followed your guide to the best of my knowledge. But for my own sanity, I would like to confirm that I've got it all correctly and therefore would like to do so from DD-WRT SSH for a browser-independent result/diagnostics.