IPv6 address in proxy field? #814

1. 
   gavinandresen commented at 2:48 PM on February 9, 2012: contributor

   From https://bitcointalk.org/index.php?topic=63165.msg739328#msg739328

   I'm not using the proxy option, but the new GUI is showing some strange IPv6 looking address in the proxy field.

   e.g. a9b1:0:f2:v532:200:0:0:0

   Once I change it, its all good.

2. ghost assigned laanwj on Feb 9, 2012
3. 
   laanwj commented at 2:57 PM on February 9, 2012: member

   Probably caused by the network stack refactor, it shows everything (even IPv4 addresses) as IPv6 now?

4. 
   slothbag commented at 1:03 AM on February 10, 2012: none

   I just tried running v0.6rc1 on a PC that WAS using a proxy and it replaced my valid proxy address details with the IPv6 looking address.

5. 
   laanwj commented at 10:06 AM on February 11, 2012: member

   The UI gets the string representation of the proxy address in this way:

   return QVariant(QString::fromStdString(addrProxy.ToStringIP()));
   

   ... which returns either a IPv4 address or IPv6 address string, based on the return value of isIPv4(). An address is identified as IPv4 if it starts with 0000:0000:0000:0000:0000:FFFF (IPv4 Mapped address). I see nothing wrong in the logic here.

   This does not explain how the garbage value ended up in the proxy option in the wallet, though. And I'm unable to reproduce this. Could there be a backward compatibility issue in the serialized representation of addresses? @sipa?

   Some experimentation did uncover another problem: the input field takes only IPv4 addresses

   Edit: He is not using the proxy. Theoretically, the setting should still be at the default (127.0.0.1:9050), or at least what he left it at last time.

6. 
   sipa commented at 5:32 PM on February 19, 2012: member

   Not sure how this is possible. Does the problem still exist?

7. 
   slothbag commented at 10:56 AM on February 20, 2012: none

   I just tried deleting my wallet.dat and let v0.6rc1 create a new wallet and the proxy address was ok (127.0.0.1:9050). However when I copied back my original v0.5.2 wallet and reran v0.6rc1 the proxy address was garbage again.

   My wallet file is the same wallet file that was generated by the v0.3.2 client a year ago.

8. 
   gavinandresen commented at 8:48 PM on February 23, 2012: contributor

   This is definitely an issue, I just tested by:

   • Ran bitcoin 0.4 on a testnet-in-a-box datadir, set the Use Proxy and Proxy address to 127.0.0.2
   • Re-ran with git HEAD bitcoin 0.6, I get: "409c:0:e1:f505:100:0:0:0" as the proxy address.
9. gavinandresen closed this on Feb 27, 2012

   ---

10. destenson referenced this in commit 37b4666c09 on Jun 26, 2016
11. ptschip referenced this in commit 27182973ed on Nov 11, 2017
12. sipa referenced this in commit 52380bf304 on Oct 14, 2020
13. KolbyML referenced this in commit 98ab596778 on Dec 5, 2020
14. MarcoFalke locked this on Sep 8, 2021

Milestone
V0.6