IvanVolosyuk / wifikeyboard

Automatically exported from code.google.com/p/wifikeyboard
GNU General Public License v2.0
170 stars 54 forks source link

Port forwarding forces new port number #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open wifi keyboard, it listens on 7777
2. Open connect bot; create a remote port forward - source port 7777 to 
localhost:7777 and connect to server (this way, connecting to 7777 on dest host 
will connect back to phone on 7777)
3. Go to another app and enabled WiFi keyboard; port number changes

What is the expected output? What do you see instead?
For the port number to remain the same between each run

What version of the product are you using? On what operating system?

Please provide any additional information below.
You can (sort of) fudge it by doing things in the reverse order- 
Open wifi keyboard and enable it to get the source port, 
Then open connect bot and create the port forward and connect... 

Ideally, it would be nice to define a single port which is used every time!

Thanks for an awesome piece of software!

Original issue reported on code.google.com by sebmayn...@gmail.com on 17 Sep 2010 at 9:38

GoogleCodeExporter commented 9 years ago
The problem is: sometimes port is used by another program and it is impossible 
to used it. It is reproducible on some phones. Another part is a bug in the app 
- it allocates the port and fails to release it, thus new instance allocates 
another port. I will try to fix the bug.

Original comment by Ivan.Volosyuk on 28 Nov 2010 at 5:44

GoogleCodeExporter commented 9 years ago
I made some change for port allocation in WiFiKeyboard 2.0. I hope it fixes the 
issue.

Original comment by v...@google.com on 1 Dec 2010 at 1:43