When we deploy filr it is pretty common, that the same filr is reachable from external (internet) name / address via "filr.external-domain.com" and at the same time from internal network (filr.internal-domain.com).
This brings two problems:
1. we need two different SSL certificates on the same filr or at least one that includes both names (us subject alternative names).
2. When a user is using the filr client (desktop/mobile) - one needs to reconfigure the filr client for different names based on the network location of the device (one time internet and one time internal network).
In iFolder - to address this problem - it is possible to specify an internal name and an external name of the iFolder server and the client will automatically switch depending on which address is reachable.
Could we get this functionality added to the Filr clients, too?
(Get a list of URLs filr is reachable during each login / refresh, contact filr via the URL that is responding the fastest / lowest latency...)
by: Martin W. | over a year ago | Desktop Client
Comments
emm... Have I misunderstood something?
isn't filr.mydomain.com is available both internally and externally !
Yes filr.mydomain.com is reachable from internal and from external - but we not want to have all internal clients communicating to the external interface of filr because that is only reachable through the proxy/firewall.
As example filr has this config:
External address: filr.mydomain.com -> IP 86.12.54.12
Internal address: filr.internal.mydomain.com -> IP 192.168.1.3
Internal client address: 192.168.1.4
--> When the internal client wants to talk to filr it is much better to communicate to filr.internal.mydomain.com instead of filr.mydomain.com to reduce the traffic routing required. (not a big problem for a single client - but think about having hundreds or thousands of filr desktop clients deployed on internal machines...)
And - when this is a roaming machine (notebook) - the filr client should talk to the internal address in case the internal address is reachable because the notebook has an internal network connection.
In case the notebook is on the road i.e. in a public network and can not connect to the private network - the client should use the public address of the filr server.
All this leads to the requirement that the filr server needs two names / addresses (one internal and one external) and the filr client needs to know both addresses and needs to connect to the internal address when reachable - otherwise connect to the public address.