-
Lyza
vterd with #6973 / 6974 is that going to apply daemons that are set up to relay over tor / i2p? like, will they fluff over ip4 if no outbound available
-
vtnerd
no, if tor/i2p is enabled, it will never use ipv4/6 for origin txes unless the daemon is re-started without those modes
-
vtnerd
perhaps we need to add an RPC, but the thinking was that if you enabled i2p/tor, the intent was to never to use ipv4/6 for broadcasting origin txes
-
vtnerd
where origin means the tx originated at that node
-
Lyza
for sure I agree with not using ip4 when tor / i2p are enabled
-
gingeropolous
ah dangit none of these mitigations are in master are they
-
gingeropolous
*aren;t
-
gingeropolous
ugh whats the suite of PRs to make my node actually useful
-
gingeropolous
6973, 6972, 6962, 6961 (is there a master version of that already in?... perhaps im too tired to be doing tihis...)
-
gingeropolous
6946, 6944, 6943, 6940, 6939, 6936, 6935, 6933, ....i wonder if i can checkout multiple PRs in a list...
-
gingeropolous
"Should not be doing an octopus.
-
gingeropolous
" oh godamnit git
-
gingeropolous
give you a damn octopous
-
selsta
gingeropolous: you should checkout release branch
-
selsta
and then apply the PRs from the merge list
-
selsta
.merges
-
xmr-pr
6961 6962 6966 6967 6972 6974
-
gingeropolous
i managed to do something on top of master.... hopefully i don't have to nuke my repo. not the best with git.
-
gingeropolous
but thank you :)
-
gingeropolous
hrm, i just started a daemon with those PRs and no preset bans.
-
gingeropolous
it still hasn't banned any IPs
-
selsta
gingeropolous: we don't do automatic bans
-
selsta
or which PR did you merge exactly?
-
selsta
6936?
-
selsta
they updated their behavior to appear as synchronizing so 6936 ignores them
-
normo
Is here a list of monerod commands, like "bytes received for category command-1002 initiated by us"
-
selsta
.merges
-
xmr-pr
6961 6962 6966 6967 6972 6974
-
selsta
Snipa you maybe available? :)
-
Snipa
Not super so, I'm more tired than I'd like to be to do merges, been monitoring work tonight.
-
selsta
ok will wait for luigi
-
luigi1111w
.merges
-
xmr-pr
6961 6962 6966 6967 6972 6974
-
xmr-pr
moneroentusi opened issue #6976: Cannot create or restore wallet on Windows 7 virtual machine
-
xmr-pr
-
xmr-pr
mj-xmr opened pull request #6977: Clang-tidy integrated into CMakeLists.txt (mj-xmr)
-
xmr-pr
-
moneromooo
Is it just me or does it feel really off putting to add one's nick in every single commit message ?
-
asymptotically
author and committer fields in the commit just aren't good enough!
-
selsta
luigi1111: do you have time for merges today? we kinda have to release soo
-
selsta
soon
-
luigi1111w
.merges
-
xmr-pr
Merge queue empty
-
selsta
luigi1111w: there will be one more from mooo
-
selsta
and then gui merges
-
selsta
afterwards we can tag both
-
moneromooo
.merges
-
xmr-pr
Merge queue empty
-
moneromooo
.merge 6979
-
moneromooo
.merge+ 6979
-
xmr-pr
...
-
moneromooo
...
-
moneromooo
.merges
-
xmr-pr
6979
-
xmr-pr
moneromooo-monero opened pull request #6979: p2p: rewrite boost's make_address_v4 to cater for < 1.66
-
xmr-pr
-
xmr-pr
MNSTG opened issue #6980: Monero issue
-
xmr-pr
-
gingeropolous
alll right. all the goodies in master now?
-
gingeropolous
yaaaaas
-
gingeropolous
oh wait i don't see it it in git log. bah
-
dEBRUYNE
Can someone close 6980?
-
moneromooo
done
-
selsta
gingeropolous: no use release branch :D
-
selsta
master is super behind currently
-
gingeropolous
17.1.1?
-
selsta
git checkout release-v0.17
-
gingeropolous
aaaah i see yes thanks
-
asymptotically
why do we do the dual PR thing? could the maintainers not cherrypick from master into the releases?
-
moneromooo
We would not want code not signed by the author..
-
moneromooo
It *might* work before the two branches diverge too much. Feel free to try it out.
-
gingeropolous
im not not licking frogs
-
selsta
gingeropolous: make sure to use boost 1.66 or newer
-
selsta
else you will need 6979
-
gingeropolous
well im compilin. we'll see what happens
-
dEBRUYNE
asymptotically: Seems less risky to simply open the PR against both branches
-
asymptotically
yeah i guess that the pr author might find it easier to fix any conflicts
-
gingeropolous
well it build so i musta had goot boost
-
gingeropolous
aight, that release branch is running on xmrchain.net
-
gingeropolous
2020-11-04 21:40:36.948 I Monero 'Oxygen Orion' (v0.17.1.1-01606ee52)
-
gingeropolous
<<< look right?
-
selsta
gingeropolous: no it builds with wrong boost too
-
selsta
better to check
-
gingeropolous
ooooooh k. googling how to find boost version.
-
selsta
when you enter "make" it will say Found Boost Version
-
gingeropolous
well thats long gone in the screen buffer
-
selsta
git pull origin pull/6979/head
-
selsta
will apply 6979
-
gingeropolous
-- Found Boost Version: 106501
-
selsta
yep better apply 6979
-
selsta
or wait until luigi merges it
-
gingeropolous
i applied. building.
-
luigi1111w
we good/
-
selsta
yep you can tag v0.17.1.2
-
selsta
or wait
-
selsta
moneromooo: can you take a look if 6979 compiles on ubuntu?
-
selsta
-
selsta
error: ‘class boost::asio::ip::address_v4’ has no member named ‘to_uint’;
-
selsta
or maybe something else failed
-
selsta
-
selsta
ok same error, it wants to_ulong instead of to_uint
-
moneromooo
Haha, seriously...
-
moneromooo
Let's add this one too then.
-
selsta
this is net_node.inl:1504:63
-
moneromooo
Fucking assholes. They just renamed to_ulong to tpouint apparently.
-
moneromooo
So we got to work out which verison, and #if it.
-
selsta
ubuntu 18.04 has 1.65
-
selsta
mac and windows CI have boost 1.66 or newer
-
selsta
which both compile fine
-
moneromooo
Release notes for 1.66 don't mention this.
-
moneromooo
Well, if it works...
-
selsta
hmm
-
selsta
both win and mac have 1.74 or 1.73
-
selsta
so yea, it maybe did not get changed in 1.66 exactly
-
moneromooo
I'll see in.. ~4 mins.
-
asymptotically
-
moneromooo
ty
-
moneromooo
.merge+ 6981
-
xmr-pr
Added
-
xmr-pr
moneromooo-monero opened pull request #6981: p2p: make this work with boost <= 1.65 (pffff)
-
xmr-pr
-
selsta
luigi1111: ok all compiled now, 6981 and then v0.17.1.2 can be tagged