-
selsta
.merges
-
xmr-pr
8937 8938 8941 8976 8977 8988
-
selsta
pls merges so that we can put out the release
-
nioc
.merges
-
nioc
<xmr-pr> 8937 8938 8941 8976 8977 8988
-
xmr-pr
8937 8938 8941 8976 8977 8988
-
luigi1111w
ok
-
selsta
thank you, gui too please
-
m-relay
<0x1zxq7896lp2zero:matrix.org> what happen to the rust monero implementation
-
m-relay
<0x1zxq7896lp2zero:matrix.org> last i saw it still had 3 separate open source conflicting licensees
-
m-relay
<0x1zxq7896lp2zero:matrix.org>
github.com/rust-monero/xmr
-
m-relay
<0x1zxq7896lp2zero:matrix.org>
github.com/xmr-rs/xmr
-
m-relay
<0x1zxq7896lp2zero:matrix.org> is this working
-
m-relay
<0x1zxq7896lp2zero:matrix.org>
github.com/monero-rs
-
m-relay
<0x1zxq7896lp2zero:matrix.org> why multiple implementation
-
m-relay
<0x1zxq7896lp2zero:matrix.org>
github.com/rust-monero
-
rbrunner
Is it really necessary to continue to f*ck with testnet, keep it at 80 kH/s and then sometimes leave for hours on end, basically bringing the network to a standstill?
-
rbrunner
There were 10 blocks over the last *12 hours*
-
jackintosh157
Hello, I am trying to host a public monero node. However, I want to route my traffic through my VPS using TCP-Redir. This will allow my VPS ip to be used as a way for clients to connect to, instead of leaking my home ip address. The monerod instance is hosted on a physical server I have at my house, as the VPS does not have enough resources to host a public node. I found a public github issue describing the issue, but
-
jackintosh157
it is a few years old and no progress has been made on it:
monero-project/monero #5979. From what I can understand, I can redirect traffic (both p2p and RPC), however whenever my public IP address is advertised via P2P, it will give the IP of my home address (instead I want my VPS ip advertised). Any solutions? How does monerod get your public ip address?
-
jackintosh157
Why do this? The VPS has higher network bandwidth. This acts as a proxy, protecting my home IP from denial of service attacks. Individual services can be rate limited with TCP-Redir.
-
jackintosh157
I also believe when monerod tries to connect to other public nodes, it will leak my public IP (even if somehow we were able to find a solution to my problem above). This is an acceptable limitation. Clients that connect to my public node will use my VPS ip. Ie if I discover another node, I'll end up leaking my home IP as I'll be connecting with a random port outbound. But if another node discovers me, they will connect
-
jackintosh157
to my vps ip and use my specified P2P port.
-
moneromooo
--p2p-external-port arg (=0) External port for p2p network protocol
-
moneromooo
Use this with your VPS's public IP to override monerod's auto detected IP. Which IIRC it gets from a return message from peers in handshakes.
-
jackintosh157
thanks
-
moneromooo
Come to think of it, it cannot be, since the peer would see the VPS's IP. So I'm not sure how it gets the IP then.
-
moneromooo
Oh wait. It's port, not IP :S
-
moneromooo
Yeah, makes sense. If you route your traffic throiugh a VPS, peers should see your VPS' IP. If they see your home IP, your redirection is probably broken in the first place.
-
moneromooo
And you can still use --p2p-external-port if your out port is different from your local listening port.
-
moneromooo
Maybe someone remembers whether this "IP from return packet from peer" notion is correct. I'm not 100% sure it is.
-
jackintosh157
even if it correct, when I do discover other public nodes I'll be connecting to them with my home ip
-
jackintosh157
Thus they return my home ip, and by that notion monerod will advertise my home ID.
-
jackintosh157
IP*
-
jackintosh157
I'll be getting two sets of packets sent back to me, one where it says my IP is home IP (when I discover other nodes), and one where it says it is my VPS ip (when other nodes discover me).
-
jackintosh157
Honestly I don't think there is much benefit to try to route p2p traffic through my VPS if when I discover other public nodes I connect with my home IP. The P2P is already monitored, my home IP leaks when I try to discover other nodes. For instance I can find my node on MoneroHash even though I am not a public node and just leeching. So may as well just run a public node on home IP.
-
moneromooo
Ah. Then that's why they're getting your IP. I thought your redir was basically a personal VPN.
-
m-relay
<ofrnxmr:monero.social> thiking.. Does --p2p-bind-ip allow you to "override" the ip that is broadcast? Or..
-
m-relay
<ofrnxmr:monero.social> Can --proxy be used instead of tcp-redir
-
moneromooo
It selects the IP to bind to. Usually these are non routable IPs from your LAN (or loopback).
-
moneromooo
I guess it'd work if you're on the backbone directly. We need someone on the backbone to test :D
-
m-relay
<seikoqq1:matrix.org> Is Koe around ?
-
m-relay
<ofrnxmr:monero.social> Dontasktoask.com
-
m-relay
<ofrnxmr:monero.social> Whatsup?
-
rbrunner
seikoqq1:matrix.org: More frequently in the #monero-research-lab IRC channel than here, but yes, he follows development.
-
rbrunner
There is also a weekly meeting there, the last one 2 days ago was this one:
monero-project/meta #894
-
m-relay
<ofrnxmr:monero.social> if were being technical, Koe is on a haitus.
-
m-relay
<ofrnxmr:monero.social> Is he around? I guess it depends what you want to talk about. Aka, dontasktoask.com