11:38:26 <llacqie[m]> The node worked for 12 hours, 128 outgoing and 0 incoming
11:44:46 <ofrnxmr[m]> It works on your not Nat device, correct ?
11:50:06 <llacqie[m]> 1. Both my servers can work without NAT, I myself force one of them to work through the ip address of the other so that the stagenet and mainnet nodes work on the same ip address.
11:50:06 <llacqie[m]> 2. But now I don't do it and the mainnet node works without NAT through its public ip address
11:51:33 <llacqie[m]> Stagenet node and mainnet node run on different machines with different public IP addresses
11:53:16 <llacqie[m]> Is there at least someone in this chat whose node is working fine??
12:07:54 <selsta> llacqie[m]: all my nodes work fine
12:08:56 <selsta> can you clarify if the stagenet node also has the same issue with 0 incoming?
12:09:00 <moneromoooo> Mine also does, but has a bog standard network setup. Penty of INC.
12:10:52 <selsta> jberman has a node with this issue and we did some testing, manually connecting works fine. deleting p2pstate.bin and adding the node to the peer list with --add-peer also makes it connect
12:11:03 <selsta> so there's nothing inherently stopping nodes from connecting
12:15:03 <moneromoooo> Maybe you have an IP in an often banned range.
12:15:44 <moneromoooo> Or in a /8 or /16 with lots of other nodes (so other nodes won't connect to you if they already have a peer in that range).
12:16:28 <moneromoooo> Or maybe your ISP is an asshole.
12:17:10 <llacqie[m]> I have an IP from 149.154.71.0/24
12:17:44 <moneromoooo> Oh yes I meant /24 or /16 above.
12:18:16 <llacqie[m]> I can try to run a stagenet node on the same host that the mainnet node is currently on
12:18:18 <selsta> the same issue is on stagenet and testnet for some so I don't think it's too many nodes in this IP range
12:18:24 <moneromoooo> I hate how this /8 means 8 significants and not the size of the range, I make that mistake often.
12:18:32 <selsta> it's unintuitive
12:19:05 <llacqie[m]> But my stagenet node on another host is working fine
12:20:02 <selsta> llacqie[m]: both same ISP?
12:20:29 <moneromoooo> Reading above, you say "The nodes don't even try to request anything from my node, they just connect and disconnect", this is an OK behaviour, used to probe the grey list, separate from actually trying to connect to a peer for long term usage.
12:22:09 <moneromoooo> Though it could also be nodes connect to you and do not like the response.
12:22:27 <moneromoooo> In which case the peer's log would show why it disconnects. But not your log, unfortunately.
12:22:59 <selsta> People running wownero nodes on the same machine don't have this issue, wownero is still v0.17 based so it feels like a software bug in v0.18
12:23:14 <moneromoooo> I don't suppose you modified the code, right ?
12:23:16 <llacqie[m]> selsta: Yes, same ISP
12:24:23 <llacqie[m]> I also hosted node v0.17 earlier for a month and everything was fine
12:24:41 <llacqie[m]> moneromoooo: I downloaded the official builds
12:25:29 <moneromoooo> I suppose you could try building your own, see if it helps. If not, switch to a different verison of boost, say... 1.72.
12:26:10 <moneromoooo> Assuming the getmonero.org builds aren't on 1.72. I just use that one for a fork and it's been working good.
12:26:31 <selsta> we didn't change the boost version between v0.17 and v0.18 so i don't think it's related
12:26:35 <moneromoooo> A bit of a long shot though, any bug is likely to be in monero.
12:27:47 <moneromoooo> Do the "official" builds have the patches from perfect-daemon that change the KV serialization ?
12:29:58 <selsta> no, only the connection patch
12:31:15 <moneromoooo> Pfft. My logs are filled with bad_weak_ptr. I had fixed that :(
12:32:05 <moneromoooo> Well, feel free to remind me in a few days, I'll check my logs for that IP range to see if I see anything interesting. I purged my logs recently so nothing atm.
12:33:14 <moneromoooo> Is that node running now ?
12:35:54 <llacqie[m]> moneromoooo: No, I want to experiment with different ISP
12:36:07 <moneromoooo> Ah, barf. My connection log patch never got in.
12:36:46 <llacqie[m]> Height: 1218212/1218212 (100.0%) on stagenet, not mining, net hash 2.06 kH/s, v16, 25(out)+8(in) connections, uptime 0d 0h 16m 54s
12:36:57 <llacqie[m]> stagenet node works fine
12:37:17 <selsta> I assume mainnet would work fine too if you were able to run it on the same system
12:39:33 <llacqie[m]> It worked under the same IP as the stagenet node via NAT
12:43:13 <llacqie[m]> And there were no incoming connections either
12:44:01 <selsta> what do you mean it worked?
12:44:23 <selsta> i meant on the same system, not with the same IP
13:02:39 <sech1> llacqie[m] if you run behind a NAT, double check that you port forward port 18080 to your internal IP where you run the node
13:02:47 <sech1> stagenet uses different port number
13:10:45 <llacqie[m]> I checked
13:17:11 <sech1> online port checkers say that port 18080 is open on your external IP address?
13:20:26 <llacqie[m]> sech1: I connected from my local node without any problems
13:21:08 <sech1> your local node is behind node, it's irrelevant
13:21:14 <sech1> use https://portchecker.co/ to check your IP and port 18080
13:21:23 <sech1> *is behind NAT
13:22:37 <llacqie[m]> I'm too lazy to explain, but I guarantee you that the port was open
13:29:51 <moneromoooo> If you got connections that disconnect, it was open.
13:42:54 <llacqie[m]> Height: 46818/1218244 (3.8%) on stagenet, not mining, net hash 21 H/s, v7, 7(out)+9(in) connections, uptime 0d 0h 17m 16s
13:42:55 <llacqie[m]> stagenet node on the same host as mainnet with the same ip address
13:56:28 <selsta> hmmm
14:06:36 <llacqie[m]> So the fact that stagenet works does not mean that mainnet will work as well.
14:07:18 <selsta> other people in the linked issue have issues on both stagenet and mainnet
14:07:40 <selsta> I wonder if your incoming peers will drop once you are synced up
14:08:23 <selsta> another thing you can test is if you have incoming peers on mainnet while syncing from scratch
14:09:06 <selsta> e.g. exit monerod -> mv ~/.bitmonero/lmdb ~/.bitmonero/lmdb_old -> start syncing and check if you get incoming peers on mainnnet -> move back the old blockchain
14:56:41 <llacqie[m]> Height: 172064/2750627 (6.3%) on mainnet, not mining, net hash 21.95 MH/s, v1, 10(out)+0(in) connections, uptime 0d 0h 9m 17s
15:04:57 <selsta> llacqie[m]: stagenet and mainnet use the same exact same binary?
15:05:51 <selsta> i assume yes
15:23:01 <llacqie[m]> selsta: yes
15:43:21 <llacqie[m]> Height: 126151/1218309 (10.4%) on stagenet, not mining, net hash 480 H/s, v7, 16(out)+31(in) connections, uptime 0d 0h 43m 39s
15:55:04 <llacqie[m]> selsta: what distro do you use for your servers?
15:55:34 <selsta> Ubuntu 20.04
16:56:06 <llacqie[m]> I have started syncing on another host that is in a different location, and it looks like I have incoming connections (I also applied a ban-list, so these are not bots)
20:31:40 <riceandbeans> Is there a point to mixers existing for monero?
20:37:22 <selsta> I assume most monero mixers are a scam to steal your coins.
20:37:28 <rbrunner> Don't think so, and I claim that none exist. If somebody claims, I would say it's probably a scam.
20:42:03 <riceandbeans> Yeah that's pretty  much what I was thinking
20:43:04 <Rucknium[m]>   riceandbeans Look up TxTangle in Zero to Monero 2.0
20:43:47 <Rucknium[m]> Basically a CoinJoin for Monero. Later they figured out that there wasn't a good way to do it without revealing too much info to the other TxTangle participants.
21:52:37 <merope> <rbrunner> "Don't think so, and I claim that..." <- I do recall seeing at least one being advertised a few years ago, and yeah it was a blatant scam. No idea if it's still around