Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Firewall patch in order to be able to connect to AsTeRICS-Ergo from remote Tablet/Smartphone #101

Closed
klues opened this issue Nov 2, 2017 · 6 comments
Assignees

Comments

@klues
Copy link
Contributor

klues commented Nov 2, 2017

Currently Windows 10 by default blocks traffic needed for AsTeRICS-Ergo to work on a remote Smartphone/Tablet. I wrote this patch:
fixfirewall.zip
which deletes blocking Java-Firewall-Rules and adds a a rule for the needed ports of AsTeRICS-Ergo.

This patch could be included similar to the FS20-patch to be started from the webapp with UAC-control dialog afterwards. A good place to start this patch would be in the FAQ-question where we describe how to use AsTeRICS-Ergo on a Smartphone/Tablet.

@klues klues self-assigned this Nov 2, 2017
@klues
Copy link
Contributor Author

klues commented Nov 2, 2017

for the exe-release this fix should be the right one:
fixfirewall2.zip
it disables the rules for "asterics ergo.exe" and not for java in general.

@klues
Copy link
Contributor Author

klues commented Nov 2, 2017

in order to also support Edge/IE for showing the correct local IP in the Smartphone-FAQ, we maybe could add a REST-method that returns the current local IP, with some snippet like this:

Enumeration< NetworkInterface > interfaces = NetworkInterface.getNetworkInterfaces( );
List<NetworkInterface> list = new ArrayList<>();
while(interfaces.hasMoreElements()) {
    NetworkInterface element = interfaces.nextElement();
    if(element.isUp() && element.getName().startsWith("wlan")) {
        list.add(element);
    }
}
list.get(0).getInetAddresses();

@klues klues mentioned this issue Nov 2, 2017
@deinhofer
Copy link
Contributor

Think about executing it in the installer run section: http://www.jrsoftware.org/ishelp/index.php?topic=runsection

Regarding fetching the IP address:
Yes this is a good idea. But the script should not only show IPs of WLANs as wired ones could be also used.

@klues
Copy link
Contributor Author

klues commented Nov 6, 2017

@ run in installer:
yes, good idea, better than a manual patch that has to be executed by the user.

@ ip address:
the problem is, that it is not really possible to detect which IP to use if there are more than one active network interfaces (element.isUp()). thats why I thought of this "hack" to only use wifi-interfaces, because it will be the right one in most of the cases...
Maybe we can implement something where wifi ip-addresses are prefered and if no wifi is found the next one is used.

@klues klues added this to the Version 4.0, 11/2017 milestone Nov 8, 2017
@klues
Copy link
Contributor Author

klues commented Nov 8, 2017

IP-address issue moved to own issue: #105

@klues
Copy link
Contributor Author

klues commented Nov 8, 2017

should be fixed with 3f38827

@klues klues closed this as completed Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants