Use pre-defined trusted peer when connected to an specific WLAN

[GoogleCodeExporter]

Since there is no zeroconf support for bitcoin servers, on option that defines 
an trusted peer when connected to an special WLAN would be great. I have an 
bitcoind instance running at home and this feature would would help to speed up 
the sync when my phone is connected with my WLAN at home.

Original issue reported on code.google.com by fschm...@gmail.com on 29 Jan 2012 at 2:16

[GoogleCodeExporter]

I see your point. I'm afraid this feels very special. Why would you not connect 
to your trusted peer from the road? (Yes, proper authentication and perhaps 
crypto should better be implemented for that trusted peer connection.)

Original comment by andreas....@gmail.com on 29 Feb 2012 at 3:17

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I could see this being useful only if that trusted peer exists on your home 
network and it's well firewalled from outside.  In that case, it'd be REALLY 
useful.

However, on the home end it'd be pretty easy to set up a DDNS account and 
configure the router to forward inbound requests on the bitcoin ports to point 
to your "server," which would then have a static IP on the local network.

You could take this one step further and implement a VPN connection into your 
router, and have your phone connect to that; then point the wallet to the local 
(private) IP address of your server and let Android and your home router sort 
out the details of whether to route it locally or via the VPN.  This has the 
added benefit of end-to-end IPSec security, which is pretty damn secure.

Original comment by danbowk...@gmail.com on 8 Apr 2012 at 3:41