Kevin, thanks for the reply. Correct me if I'm wrong, but option 3 would require I be rooted, correct? Would I only need to root temporarily in order to create the file, and then NeoRouter would use it even if I un-rooted? (I ask because there are "temporary" root programs that give you root access but then revert back to normal when the phone is rebooted)
I had an additional thought, and am wondering if it would be possible (or useful!) to work this into a future release of the Android NeoRouter client. I'm not up to speed enough to know for sure what the correct terminology for all this would be, though.
Consider a typical point-to-site sample configuration: You have computer 1, which is the "point" computer, with an NR address of 10.0.0.1. You have computer 2, which serves as the NR client on the "site" network, with an NR address of 10.0.0.2 and a physical address of 192.168.0.1. Then there's Computer 3, with no NR client and a physical address of 192.168.0.2. We won't bother detailing the various feature.ini or route settings that go on each machine.
Let's call this scenario 1: When computer 1 wants to communicate with computer 3, it sends the data to computer 2, which routes it on to computer 3. Computer 3's response goes back to 2, which routes it back to 1.
So now we add computer 4, which is an Android device with an NR IP of 10.0.0.3. Currently, we can communicate with computer 2 by setting up port forwarding. For example, our android RDP application accesses localhost:32973 and the NR client intercepts that and sends it to 10.0.0.2:5900. The NR client then receives the response from 10.0.0.2 and routes it back to the application at localhost:32973.
So what I'm thinking is that we have an additional port forwarding option that could be configured to send
routed data to the other NR computer.
In other words, the Android NR client would be told to watch for localhost:32973 and send it to 10.0.0.2
with a final destination of 192.168.0.2:5900.
In this scenario, computer 2 would be doing the same thing it did in scenario 1 - acting as a router between another NR client and computer 3.
The only difference in the Android client is that instead of sending data to computer 2 saying "this data is for you," the Android client would send data to computer 2 saying "this data is for 192.168.0.2 - please forward it."
Would something like that work?