Please check out the new Instant Help (beta) first before posting.
Understood that, if ‘eBlocker Mobile’ is installed on an iPad, you can use that VPN-connection to safely access devices in the the home LAN trough that same connection when away from home. If correct, would somebody be kind enough to tell me how?
Rob
Hi Rob,
yes that is right, I use this every day!
You have to enable for your device "Remote device my access resources in local network"
regards
PIO78
See also here for a screenshot of the switch: https://eblocker.org/docs/the-eblocker-mobile-function/
THX!
OK, your files are on the NAS, at home you can access the file.
How do you do that? With the browser over HTTP/HTTPS? Or a Client-App on your iPad?
🤔
On my iPad with the app ‘FE File Explorer’ with the enclosed settings.
On my iMac i use Forklift with similar settings.
okay,
for yout hostname /ip of your NAS give the IP Address of the NAS in this field.
(like 192.168.yyy.zzz)
The second sollution, go to eBlocker "DNS Firewall - local Network" and set the Hostname an IP
here an example:
try
😀
Thanks for the hints, but i think i have a DNS-problem.
Switched OFF WiFi in my Fritz!Box 7590 (IPv6 switched off already
iPhone set up for ‘eBlocker Mobile’ and connected to 4G-network (eBlocker-icon and controlbar are shown when visiting websites)
iPhone finds eBlocker-dashboard and -settings immediately, but can’ find any other local device
Included ‘wdmycloud.local’ in ‘DNS Firewall / LOCAL NETWORK’ (as instructed), but that didn’t help iPhone to find the NAS
Changed ‘DNS Firewall / STATUS’ from ‘Default’ (router-address 192.168.178.1) to ‘Custom List’ (1.1.1.1), but without any result
Enough info to bring me a step further?
Rob
Hi Rob,
have you tried the first solution, to give the APP the host ip of your NAS?
Enclosed the corresponding screenshot for my eBlocker.
Tomorrow i’ll switch on the ‘Remote device may connect etc’, generate a new ovpn-file and try again
Yes, i replaced ‘wdmycloud.local’ with the (fixed) local IP-address my NAS got from my Fritz!Box, but that didn’t help. Sorry for not mentioning this change in my previous message.
Hope the newly discovered setting ‘Remote device may connect etc’ will help, but can’t try now by switching off WiFi in the router without causing a revolution in the family. Will do tomorrow.
Switched OFF WiFi in Fritz!Box
Switched ON ‘Remote device may connect etc.’ (necessity!) in Settings/Devices/iPhone/MOBILE
In ‘FE File Explorer Pro’ on my iPhone, replaced ‘wdmycloud.local’ by its fixed IP (necessity!) (for unknown reason, the addition in Settings/DNS Firewall/LOCAL NETWORK of ‘wdmycloud.local’ = fixed IP is not good enough)
Under these conditions i can get to the files on my NAS using ‘FE File Explorer Pro’ without WiFi and using the 4G-network. Done!! Works!
Thanks to the both of you, Rob
PS For your info
Under the conditions described above, i also can connect to ‘fritz.box’, mentioned in Settings/DNS Firewall/LOCAL NETWORK as well
Switched ON ‘Remote device may connect etc.’ (necessity!) in Settings/Devices/iPhone/MOBILE
Great you finally found the spot @pio78 pointed you to in his very first post. BTW: The screenshot I‘ve linked above is from the docs document you said you know about already... 🤔 Probably we need to rework the docs to point this out more prominently for „quick readers“ 🧐
In ‘FE File Explorer Pro’ on my iPhone, replaced ‘wdmycloud.local’ by its fixed IP (necessity!)
This is not a necessity. If configured correctly you can always use a domain name instead of the device IP.
You might want to share a screenshot of your local eBlocker DNS config (DNS FW>Local Network) to get help with this as well. While connected to eBlocker Mobile please also share a Traceroute to eblocker.org (see here)...
THX!
Screenshot of local DNS-settings in eBlocker
Screenshot of Traceroute on iPhone WITH WiFi
Screenshot of Traceroute on iPhone WITHOUT WiFi
Screenshot of FE Explorer Pro with IP-address of NAS
Screenshot of FE File Explorer Pro with domain name ‘wdmycloud.local’
and the diagnosis supplied by FE File Explorer Pro
Grz, Rob
Are you sure eBlocker is set to be the DNS for your clients (ie. eBlocker's DNS FW is enabled)?
To verify, just add a random domain name (under DNS FW>Local Network) like "this-is-my-local-raid-domain.box" pointing to the local IP 172.168.178.3. Then try to access this domain from within your LAN and (afterwards) from within eBlocker Mobile. (Yes, it's OK to leave the other entry "...local" pointing to ...178.3 in the config too).
Alternatively you could do a nslookup (for any domain / ie. eBlocker.org) to see which DNS server is taking the request. Under macOS there seems to be "dig" (instead of nslookup), as discussed here: https://www.a2hosting.com/kb/getting-started-guide/internet-and-networking/troubleshooting-dns-with-dig-and-nslookup (sorry, I'm on win and have no clue about macOS).
THX!
To verify, just add a random domain name (under DNS FW>Local Network) like "this-is-my-local-raid-domain.box" pointing to the local IP 172.168.178.3. Then try to access this domain from within your LAN and (afterwards) from within eBlocker Mobile. (Yes, it's OK to leave the other entry "...local" pointing to ...178.3 in the config too).
Alternatively
To start with, the requested verification via LAN (via G4 will take a bit longer)
This is what you are looking for?
================================================================================
NSLookup Results of eblocker.org
--------------------------------------------------------------------------------
Device Name : iPad Rob
Device Version : 14.4.2
Date/Time : Tuesday, 30 March 2021 at 12:47:01 Central European Summer Time
Query : eblocker.org
Server Address : Auto
Force Authorative : No
Query Type : ANY
Query Class : IN
Timeout : 5s
================================================================================
---[ ANSWER SECTION ]---------------------------------------------------------
eblocker.org 21599 IN SOA ns.udag.de
Email: hostmaster@united-domains.de
Serial: 2020102101
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum TTL: 3600
eblocker.org 21599 IN NS ns.udag.net
eblocker.org 21599 IN NS ns.udag.org
eblocker.org 21599 IN NS ns.udag.de
eblocker.org 3599 IN MX mxlb.ispgateway.de
Preference: 10
eblocker.org 599 IN A 174.138.100.168
eblocker.org 599 IN TXT v=spf1
a
mx
?all
eblocker.org 599 IN TXT google-site-verification=3UFP-cxEFaLyyZhD_1Ms7hY0Q-9suXzpPEiPOL7BhS8
---[ AUTHORITY_SECTION ]------------------------------------------------------
---[ ADDITIONAL_SECTION ]-----------------------------------------------------
================================================================================
Results provided by NSLookup 1.5.5 for iPhone/iPod/iPad
NSLookup can be found at http://itunes.bejbej.info/nslookup
================================================================================
please find enclosed the Safari-screenshot from iPhone connected to 4G
Hm. So to me this looks like everything is working well with the newly added domain. Just redo the same with a new domain you desire. Issue solved?
Das ‘Tüpfelchen auf das i’, Ping with WiFi and Ping with 4G ...
Not sure what the „Tüpfelchen“ is as you tried the same .local address again (with same result as above - which is expected).
THX!
Well.. , i thought i had an issue in that Ping with WiFi gave the result shown, but Ping without WiFi gave an error as shown as well.
In honor of an eBlocker-team-member i created a domain ‘random.box’ and - believe it or not - it can be accessed with or without WiFi. Must be a ‘special’ domain 😉
So, i suggest we forget about it; my NAS can be accessed while away from home using IP-addresses (both from my iPhone, my iPad and my MacBook) and accessing my NAS was what it was all about.
Thank you for the support and enjoy the good weather!
Rob
Looking back...
iPhone on 4G-network and the entries ‘random.box’, ‘random.local’ and ‘wdmycloud.local’ in Settings/DNS Firewall/LOCAL NETWORK
random.box connects fine, as reported before,
random.local does NOT connect and
wdmycloud.local does NOT connect either
Looks like the issue i thought having is related to the ‘extension’ .local
I can’t say this is true for everybody, but it is true in my situation.
Rob
Looks like the issue i thought having is related to the ‘extension’ .local
Good call! Yes, that was my feeling too - and the reason why I suggested using a different domain. I'll check back whether this is a bug or a feature 😉
THX!
Neither a bug, nor a feature. ‘.local’ simply doesn’t exist in the list of Root Zones.
http://www.iana.org/domains/root/db
Have a nice day, Rob
@robfranssen-fr I wouldn't be too sure that's the reason. You could try i.like.rob as domain for a counterprove. .rob is not a Root Zone either - but I would guess it works too.
Generally .local addresses are usually used for "local" servers that can not be reached from the Internet but in the LAN only. Interesting .local seem to be resolved differently by DNS depending on the clients IP address 🤔 Every day you learn - and sometimes it's just a bug 😉
THX!
For the sake of the exercise, let’s try ‘i.like.rob’ (are you sure you want to try this particular domain? 😀).
I switched WiFi OFF again and found:
to make sure, i also tried ‘fritz.box’ and again i include the result
It seems that eBlocker doesn’t swallow what’s not in list of Root Zones.
Rob