Project

General

Profile

Bug #1218

manual LAN mode vs Remote mode

Added by cpg over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Medium
Assignee:
-
Category:
-
Target version:
-
Start date:
12/18/2013
Due date:
% Done:

0%


Description

as a step into automatic LAN mode detection, let's start with manual LAN mode vs Remote mode selection.

for the time being, when the LAN mode is selected, the PFE API endpoint for the app is set to this url:

http://192.168.32.10:4653/

i.e. not use SSL.

when Remote is selected, the url should be set to the current PFE API endpoint for remote (note the https, using SSL):

https://pfe.amahi.org

Just for clarification, this the local LAN mode url above is my own local HDA's LAN URL.

In real operation, these two URLs are obtained from the return output of the PUT /client call to the PFE.

This call should be done each time

1) the user logs in, or
2) the app is started, or
3) the network changes

the json returned should have two fields (per the API document), local_addr and relay_addr.

History

#1 Updated by cpg over 8 years ago

here is a test linux binary to run a local server. it ought to work on most current linux systems:

http://alpha.amahi.org/tmp/local-server

here is how to run it:

./local-server -l IP -k SOMEKEY -r ~/some-dir

this should run a local server and listen on the local IP given by IP (on port 4653) and a register under a dunmy key SOMEKEY, and it serves files under ~/some-dir/ ...

the directories under ~/some-dir/ will appear as shares in this version and the rest of the shares inside as files/directories.

do not use a valid key please - use a dummy key.

#2 Updated by cpg about 8 years ago

  • Priority changed from Normal to Medium

#3 Updated by ming about 8 years ago

  • Status changed from New to Closed

Also available in: Atom