WAN and LAN multiple support

[GoogleCodeExporter]

RetroShare is an F2F client like Alliance. One of the nice things with 
RetroShare is that the client records all ip addresses of all network 
interfaces. Both LAN and WAN.

So if WAN users meet on a LAN they will automatically find eachother by trying 
the different IP addresses.

I had this scenario today where Alliance became a pain the butt due to this, 
and due to the reported bug where A does not tell B and C that D has new 
connection info and so on...

Original issue reported on code.google.com by info%tim...@gtempaccount.com on 29 Jun 2010 at 2:01

[GoogleCodeExporter]

I can add option that will trigger listening on all available NICs, but still i 
don't think it will solve your problem in 100%. The option you really want is 
selection of what IP add to invitation code. For now 'LAN mode' (old lan 
support) is same as adding localIP to invitation code , if it's not selected 
then all invitation code will be created with externalIP. We plan to move that 
option to 'just before' creating invitations (tbh it should be there in first 
place). Problem will be with user info refreshing because actual code can't 
tell if connection is from LAN or WAN.

Original comment by Bastv...@gmail.com on 29 Jun 2010 at 9:20

[GoogleCodeExporter]

Here is how to determine a private IP by looking at it
http://en.wikipedia.org/wiki/Private_network

Example of RetroShare:
  User: John Doe
  IP(s): 192.168.0.121, 84.11.23.152

Now settings.xml could store something like:

  <friend guid="0000000000" nickname="John Doe" lanhost="192.168.0.121" wanhost="84.11.23.152, 83.114.12.54" lastseenonlineat="1276547252054" port="27561" trusted="1" />

Note the last wan hosts are stored in wanhost (primary, secondary). Suitable 
for laptops on several locations. When joining one of my friends LAN I could 
easily detect him on the private network.

The invitation codes could stay the way they are. Once successfully connected, 
extended data could be exchanged with remote client.

Original comment by info%tim...@gtempaccount.com on 29 Jun 2010 at 10:33

[GoogleCodeExporter]

This will be done in some time. Maybe i wasn't clear with "can't tell if 
connection is from LAN or WAN". It's not about IP but it doesn't matter any 
more because I've found solution.

'The invitation codes could stay the way they are. Once successfully connected, 
extended data could be exchanged with remote client.'
That's how Alliance works.

WAN history is good idea.

Original comment by Bastv...@gmail.com on 29 Jun 2010 at 11:12

[GoogleCodeExporter]

I am delighted to hear that response.

Original comment by info%tim...@gtempaccount.com on 29 Jun 2010 at 11:23

[GoogleCodeExporter]

Original comment by Deathfi...@gmail.com on 22 Aug 2010 at 9:32

• Added labels: Milestone-Release1.2.0