-
llacqie[m]
The node worked for 12 hours, 128 outgoing and 0 incoming
-
ofrnxmr[m]
It works on your not Nat device, correct ?
-
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.
-
llacqie[m]
2. But now I don't do it and the mainnet node works without NAT through its public ip address
-
llacqie[m]
Stagenet node and mainnet node run on different machines with different public IP addresses
-
llacqie[m]
Is there at least someone in this chat whose node is working fine??
-
selsta
llacqie[m]: all my nodes work fine
-
selsta
can you clarify if the stagenet node also has the same issue with 0 incoming?
-
moneromoooo
Mine also does, but has a bog standard network setup. Penty of INC.
-
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
-
selsta
so there's nothing inherently stopping nodes from connecting
-
moneromoooo
Maybe you have an IP in an often banned range.
-
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).
-
moneromoooo
Or maybe your ISP is an asshole.
-
llacqie[m]
I have an IP from 149.154.71.0/24
-
moneromoooo
Oh yes I meant /24 or /16 above.
-
llacqie[m]
I can try to run a stagenet node on the same host that the mainnet node is currently on
-
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
-
moneromoooo
I hate how this /8 means 8 significants and not the size of the range, I make that mistake often.
-
selsta
it's unintuitive
-
llacqie[m]
But my stagenet node on another host is working fine
-
selsta
llacqie[m]: both same ISP?
-
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.
-
moneromoooo
Though it could also be nodes connect to you and do not like the response.
-
moneromoooo
In which case the peer's log would show why it disconnects. But not your log, unfortunately.
-
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
-
moneromoooo
I don't suppose you modified the code, right ?
-
llacqie[m]
selsta: Yes, same ISP
-
llacqie[m]
I also hosted node v0.17 earlier for a month and everything was fine
-
llacqie[m]
moneromoooo: I downloaded the official builds
-
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.
-
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.
-
selsta
we didn't change the boost version between v0.17 and v0.18 so i don't think it's related
-
moneromoooo
A bit of a long shot though, any bug is likely to be in monero.
-
moneromoooo
Do the "official" builds have the patches from perfect-daemon that change the KV serialization ?
-
selsta
no, only the connection patch
-
moneromoooo
Pfft. My logs are filled with bad_weak_ptr. I had fixed that :(
-
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.
-
moneromoooo
Is that node running now ?
-
llacqie[m]
moneromoooo: No, I want to experiment with different ISP
-
moneromoooo
Ah, barf. My connection log patch never got in.
-
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
-
llacqie[m]
stagenet node works fine
-
selsta
I assume mainnet would work fine too if you were able to run it on the same system
-
llacqie[m]
It worked under the same IP as the stagenet node via NAT
-
llacqie[m]
And there were no incoming connections either
-
selsta
what do you mean it worked?
-
selsta
i meant on the same system, not with the same IP
-
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
-
sech1
stagenet uses different port number
-
llacqie[m]
I checked
-
sech1
online port checkers say that port 18080 is open on your external IP address?
-
llacqie[m]
sech1: I connected from my local node without any problems
-
sech1
your local node is behind node, it's irrelevant
-
sech1
use
portchecker.co to check your IP and port 18080
-
sech1
*is behind NAT
-
llacqie[m]
I'm too lazy to explain, but I guarantee you that the port was open
-
moneromoooo
If you got connections that disconnect, it was open.
-
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
-
llacqie[m]
stagenet node on the same host as mainnet with the same ip address
-
selsta
hmmm
-
llacqie[m]
So the fact that stagenet works does not mean that mainnet will work as well.
-
selsta
other people in the linked issue have issues on both stagenet and mainnet
-
selsta
I wonder if your incoming peers will drop once you are synced up
-
selsta
another thing you can test is if you have incoming peers on mainnet while syncing from scratch
-
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
-
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
-
selsta
llacqie[m]: stagenet and mainnet use the same exact same binary?
-
selsta
i assume yes
-
llacqie[m]
selsta: yes
-
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
-
llacqie[m]
selsta: what distro do you use for your servers?
-
selsta
Ubuntu 20.04
-
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)
-
riceandbeans
Is there a point to mixers existing for monero?
-
selsta
I assume most monero mixers are a scam to steal your coins.
-
rbrunner
Don't think so, and I claim that none exist. If somebody claims, I would say it's probably a scam.
-
riceandbeans
Yeah that's pretty much what I was thinking
-
Rucknium[m]
riceandbeans Look up TxTangle in Zero to Monero 2.0
-
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.
-
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