Feature request: add ability to configure relay hosts [Android]

[benhubert]

At the moment it is not possible to configure relay hosts on Android (Version 0.3.1), such as:

relay:
  relays:
    - 192.168.100.1

But especially LTE devices are very often connected behind NAT, therefore I think this is a very important feature.

Feature request: Please add the ability to enter the relays on Android.

Related issues:

• Similar: Andriod relay support #107
• iOS: [ios][feature request] need relay config ui or allow config all stuff as a whole for every thing #69
• Feature request: Allow loading of a fully-formed config.yml file #135 would also kind of solve it

[johnmaguire]

Hi @benhubert -

If your mobile devices only connect to non-mobile devices, adding the relay to your non-mobile device config should allow your mobile devices to take advantage of relays. (Per the iOS ticket you linked: #69 (comment))

Do you have a specific need for mobile-to-mobile connectivity? If so, it'd be great if you could share your use case.

[Spydron3]

One of my clients is connected via lte router. I can't access it from my android tablet. Either add the options to the android gui or even better allow import/export of the config .

[johnmaguire]

Hi @Spydron3 - are you able to specify the relay on your client connected to the LTE router? Only one side needs to the list the relay IP in their config as long as use_relays is enabled on both nodes - and mobile always has relaying enabled:

mobile_nebula/nebula/config.go

Line 42 in 2353eaf

UseRelays: true,

[Spydron3]

Hi,

first better description of my setup:

Site A: Lighthouse, PC A, Tablet A public IP
Site B: PC B, public IP
Site C: PC C, CGNAT (LTE router)

all are linux with use_relays: true and the IP of the relay is in the config

so

PC A -> PC B works
PC A -> PC C works
PC C -> PC B works
PC B -> PC C works

Tablet A -> PC B works
but
Tablet A -> PC C doesn't work

only difference the Tablet A is Android and has no relay IP.