01:50:29 <rottenwheel> https://peertube.thenewoil.xyz/videos/watch/c6f44348-3599-443d-8b92-f11dcdf10fc9
08:44:08 <lightloved[m]> Anyone know what this error `libundbound error: can't create socket: Operation not permitted` is about when trying to do a  `transfer` with the `monero-wallet-cli` inside Whonix?
08:45:12 <lightloved[m]> And after a few seconds I get another one `outgoing tcp: connect: Connection refused for [IP]` and wallet is stuck, need to CTRL+V to exit.
08:46:13 <lightloved[m]> I've tried starting the wallet with `torsocks` prefix and also with `--proxy 127.0.0.1:9050`, both with the same outcome.
08:47:19 <lightloved[m]> PS: other commands are working as expected, can connect to remote daemon (onion), can sync, `balance`, create new address, etc. All but `transfer`.
08:49:00 <lightloved[m]> Any ideas would be appreciated.
08:52:00 <anarkiocrypto[m4> Maybe wait 5 mins for the transfer to complete? Sometimes it takes a long time with remote onion nodes. I get the same errors sometimes with Monero GUI with an onion remote node, but the transfer eventually completes.
08:53:00 <lightloved[m]> anarkiocrypto[m4: I did wait ~5 mins but it keeps spamming the terminal with the same error and nothing happens.
08:53:29 <lightloved[m]> Also I have tested on non-Whonix and connected to an onion, transfer completed instantly. No wait.
08:53:38 <lightloved[m]> So I suspect it's somehow Whonix-related.
08:54:40 <anarkiocrypto[m4> That's what happens sometimes. Maybe let it run until it completes. Are you using the same remote node? Maybe some nodes have better bandwidth.
08:55:10 <lightloved[m]> Tried it with different remote nodes 3-4, same thing. Working on Debian, not working on Whonix.
08:55:56 <lightloved[m]> Maybe I should just try starting the wallet with the plain `monero-wallet-cli` command instead of prefixing it with `torsocks` or using the proxy flag. 
08:56:03 <lightloved[m]> That's pretty much the only thing I didnt try.
08:57:58 <lightloved[m]> I mean, Whonix already torrifies the connection, so I suppose since `torify` is just a bonus, it won't compromise my privacy a lot. Not sure if I'm right though.
08:58:17 <lightloved[m]>  * I mean, Whonix already torrifies the connection, so I suppose since `torify` is just a bonus, it won't compromise my privacy a lot if I don't add it. Not sure if I'm right though.
08:59:48 <anarkiocrypto[m4> Yes, those errors are on torsocks side, not Monero CLI. Whonix Workstation connects to the internet via Whonix Gateway only, which routes everything via Tor, so no IP leaks. I also connected Anbox and Android-x86 to Whonix, and they were likewise routed through Tor.
09:00:06 <lightloved[m]> Yes.
09:00:15 <anarkiocrypto[m4> You can try first with an empty test wallet if you are worried.
09:00:41 <anarkiocrypto[m4> If it connects to .onion, it's going through Tor.
09:01:03 <lightloved[m]> That's what I thought, but the maintainer of Whonix said using `torsocks` regardless, will be a bonus to privacy, not an unneeded redundancy.
09:02:00 <anarkiocrypto[m4> Whonix Workstation (and any other VMs that connect to the internet via Whonix Gateway) routes everything through Tor anyway.
09:02:11 <lightloved[m]> Yes, I know.
09:02:56 <lightloved[m]> Check the Whonix matrix channel. Here's my question and his answer:
09:03:09 <lightloved[m]> `Is it necessary to torify the connection when using monero cli wallet on Whonix? (ie. torsocks ./monero-wallet-cli --daemon-address xxx.onion:port)`
09:03:33 <lightloved[m]> A:
09:03:33 <lightloved[m]> `Necessary no.
09:03:33 <lightloved[m]> Bonus yes.
09:03:33 <lightloved[m]> Whonix monero wiki page mentions this. Stream isolation.`
09:03:36 <lightloved[m]>  * `Necessary no. Bonus yes. Whonix monero wiki page mentions this. Stream isolation.`
09:05:45 <lightloved[m]> Here's the recommended/advanced way of starting the cli (from Whonix's wiki on Stream isolation): https://whonix.org/wiki/Monero#Stream_Isolation
09:06:41 <lightloved[m]> `DNS_PUBLIC=tcp TORSOCKS_ALLOW_INBOUND=1 torsocks monero-wallet-cli --p2p-bind-ip 127.0.0.1 --no-igd --hide-my-port`
09:06:51 <lightloved[m]> `torsocks monero-wallet-cli`
09:07:02 <lightloved[m]> Thoughts?
09:09:30 <anarkiocrypto[m4> I believe stream isolation just uses a different Tor circuit (different entry node - relay node - exit node) than your other internet connections (e.g. Tor browser, Debian updates, XMPP, whatever you are using). It still runs through Tor and doesn't leak your IP.
09:09:36 <anarkiocrypto[m4> - Even though you would still be anonymous, i.e. the Tor exit relay would still not know your real IP/location, they can easily correlate those activities issued by different applications to the same pseudonym.
09:09:36 <anarkiocrypto[m4> - Stream Isolation for Monero has not yet been considered.
09:09:36 <anarkiocrypto[m4> - To enforce stream isolation, you could *experiment* with the following commands.
09:10:00 <anarkiocrypto[m4> Just close Tor Browser, XMPP, etc. and run Monero CLI by itself if you don't want to risk correlation.
09:11:01 <anarkiocrypto[m4> I use torsocks with Monero GUI on Ubuntu (sometimes on Whonix Workstation) and it works fine, just need to wait 5-10 mins sometimes for TX to be ready.
09:11:25 <lightloved[m]> So what you're saying is just close everything and just run `monero-wallet-cli` vanilla if I understood you correctly.
09:11:43 <anarkiocrypto[m4> You can try it. It wouldn't leak your IP.
09:12:49 <lightloved[m]> Yeah, it's either that or just wait like 10-15 minutes with torsocks.
09:12:59 <lightloved[m]> Thanks, will give it a try.
09:14:52 <anarkiocrypto[m4> No problem, let me know if it works.
19:53:17 <ajs_[m]> no javascript, no cookies, no trackers, no images version of xmr.radio accessible at https://static.xmr.radio