00:05:47 <xmrmatterbridge> <agentpatience> guys, how do i solo  mine monero on my server without the GUI, the GUI is very slow?
00:06:18 <xmrmatterbridge> <agentpatience> i want to use xmrig, it offers much faster speed?
00:07:01 <xmrmatterbridge> <agentpatience> perhaps i need to leave my node open vi CLI and mine with xmrig, but I am uncertain of the instructions?
00:07:09 <iDunk> Wrong channel, try #monero-pools.
00:07:46 <xmrmatterbridge> <agentpatience> IDunk, sorry.
00:37:28 <xmrmatterbridge> <agentpatience> It might be a developer question as I can only attain half the rate of xmrig?
00:38:27 <moneromooo> Well, if you're offering to speed up the monerod miner, sure, it is.
00:38:37 <moneromooo> Double check the licence allows.
00:39:13 <moneromooo> Also, keep an eye for bang for the buck. 1% speed increase for massive amounts of changes if not worth it.
00:42:36 <xmrmatterbridge> <agentpatience> Moneromoo -- why do I experience half the hashrate within the Monero wallet GUI is there anything I can do to improve it I really want to use Moneros official software to mine on the node?
00:43:04 <moneromooo> I suggested a couple things in #monero.
00:51:27 <xmrmatterbridge> <agentpatience> I think it is a developer question still.
01:12:50 <xmrmatterbridge> <agentpatience> moneromooo I thought was the expert in Monero.
03:51:51 <viperperidot[m]> Will the ban list for bad nodes be updated regularly and if so how will those updates be known so people can add the new list?
04:33:49 <gingeropolous> viperperidot[m], the strategies seem to be changing. im not aware of a way to identify new IPs .
05:06:01 <viperperidot[m]> Ok thanks I will stay tuned for any updates
11:00:29 <tobtoht> target height > daemon height issue on fully synced nodes is back on v0.17.1.5
11:02:02 <sech1> Height: 2242573/2242573 (100.0%) on mainnet, not mining, net hash 1.62 GH/s, v14, 64(out)+70(in) connections, uptime 4d 16h 35m 7s
11:02:08 <sech1> looks fine on my node (0.17.1.5)
11:02:14 <tobtoht> http://monero26mmldsallmxok2kwamne4ve3mybvvn2yijsvss7ey63hc4yyd.onion:18081/get_info
11:02:15 <sech1> I use ban list though
11:02:17 <tobtoht> http://mxcd4577fldb3ppzy7obmmhnu3tf57gbcbd4qhwr2kxyjj2qi3dnbfqd.onion:18081/get_info
11:02:21 <tobtoht> http://3t7v5zpcfxq2tocdofdcwxgrldco3elotz3iis4jtbbnscy5alezw7yd.onion:18081/get_info
11:03:53 <tobtoht> http://f42qg4hfn2jaohlmy7n2maywugnmwnnm5bffrnjcbj5nlwpe4v2qtjid.onion:18081/get_info
11:08:24 <selsta> yes, nodes have to apply the ban list when someone wants to transact with GUI
11:08:37 <selsta> CLI and Feather are fine afaik
12:23:07 <Lyza> why would it affect only the GUI?
12:24:23 <tobtoht> Lyza: programming oversight in libwallet
14:22:07 <dEBRUYNE> tobtoht: Any idea why this 'attack' is suddenly disruptive? I thought the recent releases included mitigations to curb it
17:29:26 <viperperidot[m]> Was the GUI supposed to 'reset' on the latest update?
17:29:44 <viperperidot[m]> Because I did the update and when I launched it opened the Welcome screen as if I had not run the app before
17:29:45 <dEBRUYNE> Are you using a hardware wallet?
17:29:50 <viperperidot[m]> and all my settings were reset
17:29:56 <viperperidot[m]> Now it will not connect to my remote node
17:30:00 <viperperidot[m]> <dEBRUYNE "Are you using a hardware wallet?"> Yes
17:30:01 <dEBRUYNE> cc selsta, xiphon
17:32:28 <viperperidot[m]> The weird thing is that I can connect to my node on other wallets but the Monero GUI is not connecting for some reason..
17:35:16 <dEBRUYNE> Do you use the --ban-list flag on your node?
17:36:00 <viperperidot[m]> Yes
17:38:56 <dEBRUYNE> Odd, can you check if it still works with .4?
17:40:06 <viperperidot[m]> It was working with .4 before I updated
17:41:00 <xiphon> viperperidot[m]: have a look at the proxy setting (Settings -> Interface tab)
17:41:05 <viperperidot[m]> Also nothing is showing up in the log for some reason
17:41:38 <viperperidot[m]> <xiphon "viperperidot: have a look at the"> Oh do I need to enable Socks5 proxy?
17:41:51 <viperperidot[m]> If so that must have got unchecked in the 'reset' and I forgot
17:43:20 <xiphon> "Oh do I need to enable Socks5 proxy?" -> yep, if you want to connect to remote node through socks
17:43:35 <xiphon> what OS do you use?
17:44:25 <viperperidot[m]> Ubuntu
17:44:48 <viperperidot[m]> Im not sure if I used this setting before or not
17:44:54 <viperperidot[m]> But I had my remote node connection working
17:45:09 <viperperidot[m]> Which IP and port am I entering into this field?
17:46:08 <xiphon> Sounds like you don't need a proxy
17:46:10 <xiphon> Is your remote note accessbile on the clearnet?
17:46:26 <viperperidot[m]> Its on the same network as me - LAN
17:47:06 <xiphon> No need for proxy then, disable the setting
17:47:07 <viperperidot[m]> So not accessible to the public but it is on clearnet not Tor
17:47:52 <viperperidot[m]> Ok
17:48:17 <xiphon> check whether the GUI is able to connect to some public remote node, for example, to node.xmr.to:18081
17:49:33 <viperperidot[m]> What the heck it is able to connect to that node
17:49:48 <viperperidot[m]> But I have a different wallet connected to my node using the same credentials....
17:53:01 <xiphon> Raise log level (Settings -> Log tab)
17:53:11 <xiphon> might shed some light on the issue
17:53:46 <viperperidot[m]> I checked log level 4 and nothing showed up
17:53:48 <viperperidot[m]> But I will check again
17:55:52 <xiphon> weird, but anyway, have a look at the log file
17:56:09 <viperperidot[m]> What he heck!!
17:56:15 <viperperidot[m]> Now it is connecting to my node
17:56:21 <viperperidot[m]> Still nothing in log level4 though.....
17:56:26 <xiphon> hm, did you download the gui from getmonero.org?
17:56:47 <viperperidot[m]> Yes
17:56:52 <viperperidot[m]> And verified signature
17:57:16 <xiphon> do you use portable mode?
17:57:55 <viperperidot[m]> I did not select portable mode
17:58:03 <viperperidot[m]> When I type status in the log it says
17:58:07 <viperperidot[m]> [2020-12-01 10:57 A.M.] 2020-12-01 17:57:25.295 I Monero 'Oxygen Orion' (v0.17.1.5-release)
17:58:07 <viperperidot[m]> Error: Couldn't connect to daemon: 127.0.0.1:18081
17:58:22 <viperperidot[m]> Even though the remote daemon is connected and syncing
17:58:24 <xiphon> yep, it tries to connect to local node
17:58:43 <xiphon> it doesn't work with remote nodes (yet?)
17:59:07 <xiphon> mean the particual error is expected
17:59:16 <viperperidot[m]> Wait it appears that the Wallet blocks remaining is not progressing
17:59:34 <viperperidot[m]> So maybe the GUI just hasn't updated from when I was connected to xmr.to
17:59:40 <viperperidot[m]> And I actually am not connected to my node..
18:00:37 <viperperidot[m]> Yes it doesn't look like anything is actually happening so I dont know that I am actually connected
18:01:00 <xiphon> do you use ipv4 address?
18:01:09 <xiphon> did you set the port correctly?
18:01:49 <viperperidot[m]> Yes port is correct, I am not sure about ipv4 but I had my node connected to the Monero GUI previously.
18:02:08 <viperperidot[m]> Same exact credentials that I have working in another wallet
18:03:11 <viperperidot[m]> I restarted the GUI and it looks like it was just stuck from previous node
18:03:15 <viperperidot[m]> Not connecting again
18:03:28 <viperperidot[m]> Log level 4 is empty
18:03:41 <xiphon> "I am not sure about ipv4"
18:03:45 <xiphon> do you use a hostname?
18:04:17 <viperperidot[m]> No I enter the IP address given to the node device on my network
18:04:26 <xiphon> "I restarted the GUI and it looks like it was just stuck from previous node" -> so after restart you have node.xmr.to in the remote node address field?
18:04:47 <viperperidot[m]> No I have my local node entered
18:05:30 <xiphon> "Log level 4 is empty" -> even the gui log file?
18:05:31 <viperperidot[m]> But the connection to xmr.to worked and when I switched back to my local node it appeared like it was still connected but it wasn't
18:07:34 <selsta> If you select local node on one machine you can’t also select local mode on the other machine to connect to the same node.
18:08:21 <viperperidot[m]> OK one sec I opened up the actual monero GUI log file instead of looking in the App
18:09:03 <xiphon> Lyza: "why would it affect only the GUI?" -> it should affect all the wallet implementations, cause they use the same libwallet library internally
18:14:00 <xiphon> dEBRUYNE: "tobtoht: Any idea why this 'attack' is suddenly disruptive? I thought the recent releases included mitigations to curb it"
18:15:13 <xiphon> ^ just Monero GUI Simple mode mitigations and Dandelion-related change
18:15:46 <selsta> v0.17.1.3 had peer list fixes that fixed it previously
18:16:08 <selsta> "fixed it" as in it didn’t show up previously
18:16:13 <tobtoht> with the exception of the CLI (uses wallet2 directly), wallets that use woodser's c++ library (idem dito) and Feather (uses libwallet, but patches in a fix)
18:16:17 <tobtoht> xiphon: I'm looking into it. It had appeared the target height issue was fixed in v0.17.1.3, but none of the commits suggest that it was.
18:16:33 <xiphon> it was never fixed
18:16:39 <viperperidot[m]> Ok sorry everyone but here is what happened - I check the Monero GUI log file and it was saying that there was an incorrect username and password for the RPC...So I went back and I copied and pasted the RPC info directly from the other wallet that was connected to my node. It is now connected but just to be sure I compared the RPC info from the other wallet to the RPC info in my password manager (where I was
18:16:39 <viperperidot[m]> originally copying and pasteing from) and they are identical!! So I do not know why this was happening. But sorry about this, next time I will just open up the log directly to do some more digging myself.
18:16:55 <xiphon> "^ just Monero GUI Simple mode mitigations and Dandelion-related chang"
18:17:31 <xiphon> ^ ... the core still don't drop the peers claiming higher height and not returning the blocks upon request
18:17:48 <xiphon> something like https://github.com/monero-project/monero/pull/6944
18:18:30 <tobtoht> this issue threw me off https://github.com/monero-project/monero/issues/7029
18:52:54 <dEBRUYNE> <xiphon> it was never fixed <= Guess we need another release then
18:53:52 <dEBRUYNE> xiphon: Would 6944 have fixed the issue?
18:54:47 <xiphon> yep, we would need another release
18:54:52 <xiphon> maybe we will come with better solution
18:55:09 <selsta> IMO adding a timeout is "good enough" for now
18:55:24 <selsta> with some better solution in a further release
18:55:53 <xiphon> yeah
19:38:41 <tobtoht> nodes that applied the ban list are starting to run into the target height issue again
19:40:17 <tobtoht> using the most recent list from https://gui.xmr.pm/files/block.txt
19:44:15 <selsta> do you have one of these nodes?
19:44:41 <selsta> it is possible that he spun up new IPs
19:45:15 <selsta> all of my nodes are fine with block list
19:45:50 <selsta> if you know someone who has this issue please ask them to run `sync_info` and send you the output
19:49:51 <tobtoht> yes it's a new IP, one moment
19:51:06 <selsta> I have more IPs that are not included in block.txt because I want to avoid false positives
19:51:39 <tobtoht> 178.62.116.193
19:53:05 <selsta> do you have a sync_info output?
20:00:38 <tobtoht> https://paste.debian.net/plainh/2c940fd6
20:02:32 <selsta> thanks, updated the list
20:15:11 <lh1008> Hello everyone. This is not easy for me but here I am. When I first started studying programming I was told that most of it is because we never give up and some good luck helped us reach the goal. I'm not here to sermon or change anyone's way of thinking. I've seen how people are shut and I personally don't like it, that hurts and hurt people do
20:15:11 <lh1008> bad things. No drama, I'll pay the price, I myself got into this situation. We'll keep coming here as always.
20:15:49 <lh1008> Thank you for your reading and time.
20:22:20 <xmrmatterbridge> <agentpatience> We all suffer our own demise.
20:23:16 <xmrmatterbridge> <agentpatience> Since I have been a systems engineer I have become fat and ugly but I am paid well.
20:26:07 <azy> talk a walk each day and stop eating so much
20:41:58 <lh1008> good to know you're watching :)
21:32:00 <Lyza> I'm having a ton of hosts get blocked from 185.220.101.* and 185.220.100.*
21:32:27 <Lyza> does the block list or the ban command work on entire subdomains, cidr notation or smth?
21:32:28 <moneromooo> Some asshole is sending bad data through tor, you're banning the exit nodes.
21:32:36 <moneromooo> AFAIK no.
21:32:37 <Lyza> ah crap
21:32:39 <Lyza> I see
21:33:48 <moneromooo> Sorry, ban does work with CIDR. Block list AFAIK does not.
21:34:09 <Lyza> got it ty. if they're tor exit nodes though I don't really want to do that anyway I guess
21:37:13 <Lyza> on another note somebody mentioned another point release. if we're lining one up, can I draw attention to #7010 and especially #7017? I thought they were gonna end up in the last point release
21:37:31 <Lyza> #7017 is a big deal for tor / i2p anonymity imo
21:40:50 <hyc> #7010 still has not been reviewed by anyone
21:41:08 <hyc> obviously I think it's fine to go in, I've been running it for over a month
21:42:29 <selsta> done
21:42:52 <selsta> .merge+ 6948 7010
21:42:52 <xmr-pr> Added
21:44:21 <selsta> 7017 needs a review from someone else
21:51:14 <moneromooo> Looks good, approved.
21:53:21 <selsta> vtnerd: please also PR 7017 against release branch
22:17:11 <Snipa> .merges
22:17:11 -xmr-pr- 6890 6910 6923 6939 6948 6954 7010 7024 7025
22:44:15 <selsta> moneromooo: please rebase 6874
22:44:34 <selsta> not rebase but update to put the seed in the correct location
22:45:42 <selsta> oh wait, forget what I wrote, we have to merge  6984 first. sorry
22:52:42 <selsta> .merge+ 6984
22:52:43 <xmr-pr> Added