[GH-ISSUE #276] ios: ip of the router defaults to 192.168.2.1 #115

New issue

Closed

opened 2026-03-04 01:34:55 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:34:55 +03:00

Owner

Originally created by @0vercl0k on GitHub (Jan 24, 2024).
Original GitHub issue: https://github.com/spr-networks/super/issues/276

It'd be nice if the iOS could cache the IP of where SPR is at or just defaults with the gateway defined on the network interface. My set-up doesn't use the 192.168.2.x network and so every time the application is killed / phone rebooted, I need to update the IP when logging in via the app.

Originally created by @0vercl0k on GitHub (Jan 24, 2024). Original GitHub issue: https://github.com/spr-networks/super/issues/276 It'd be nice if the iOS could cache the IP of where SPR is at or just defaults with the gateway defined on the network interface. My set-up doesn't use the `192.168.2.x` network and so every time the application is killed / phone rebooted, I need to update the IP when logging in via the app.

kerem closed this issue

2026-03-04 01:34:55 +03:00

kerem commented

2026-03-04 01:34:56 +03:00

Author

Owner

@lts-rad commented on GitHub (Jan 24, 2024):

can do. one other thing here is to look into how the react deals with a self signed certificate, havent checked on this yet but i think its going to be a pain point

@lts-rad commented on GitHub (Jan 24, 2024): can do. one other thing here is to look into how the react deals with a self signed certificate, havent checked on this yet but i think its going to be a pain point

kerem commented

2026-03-04 01:34:56 +03:00

Author

Owner

@lts-po commented on GitHub (Jan 24, 2024):

Thanks! This is fixed now in dev, stores hostname if login successful. Will be in the next release.

@lts-po commented on GitHub (Jan 24, 2024): Thanks! This is fixed now in dev, stores hostname if login successful. Will be in the next release.

kerem commented

2026-03-04 01:34:56 +03:00

Author

Owner

@0vercl0k commented on GitHub (Feb 7, 2024):

This is also fixed as far as I can tell!

@0vercl0k commented on GitHub (Feb 7, 2024): This is also fixed as far as I can tell!

kerem referenced this issue

2026-03-04 01:36:16 +03:00

[PR #115] [MERGED] docker build update #322