log☇︎
3200+ entries in 0.001s
asciilifeform: mp_en_viaje: plox to share the 'undreamy' straight-logic then ?
asciilifeform: BingoBoingo: phf's logger dun echo. plox to use diana_coman's or lobbesbot
asciilifeform: BingoBoingo: any word from these ? even so much as a timetable for getting the service we're paying for ?
asciilifeform: http://logs.ericbenevides.com/log/trilema/2019-10-04#1940295 << the sea cable doesn't literally terminate in our cage, sadly
asciilifeform brb 10min,teatime
asciilifeform: mp_en_viaje: indeed. i'm relying on BB to get some fucknig answers (and the pipe, forfuxxsake)
asciilifeform: the idjicy of the upstream piper seems to weigh 9000x what 'attack' weighed.
asciilifeform: BingoBoingo are you alive in there ?!
asciilifeform: indeed!
asciilifeform: per asciilifeform's local scroller.
asciilifeform: mp_en_viaje: 10:48 new york time .
asciilifeform: bvt: 180 appears to work (tested for coupla hrs) but may need empirical test.
asciilifeform: lol why would BingoBoingo ask for such thing
asciilifeform: mp_en_viaje: possibly grandfathered. when asciilifeform experimented w/ no-sslism connect via own (cloakistic) nick, ended up w/ displayed ip.
asciilifeform: mp_en_viaje: per the letter of the contract, we are..
asciilifeform: mp_en_viaje: it's described further downlog -- appears to be the traditional rotating ddos
asciilifeform: when i wrote 1st draft of logotron, i initially made mistake where lines were displayed in order of timestamp. even very old logs became an adventure in wtf upon reading
asciilifeform: given how pc clock worx, and the existence of multiple loggers, timestamps in log are somewhere between 'mildly informative' and 'screamingly useless' imho
asciilifeform: ( and to add insult to injury, when importing logs externally, the peer's times are eaten )
asciilifeform: mp_en_viaje: timestamps (both current & historic) are all over the place. cuz clocks are shite.
asciilifeform: along with errything else in that cage.
asciilifeform: indeed
asciilifeform: ftr i did not put this in genesis because naively supposed that ordinary workings of tcp will in fact throw a connection if the pipe were to unplug. but apparently this aint so
asciilifeform has internal policy of not regrinding a patch for mistakes in comments; folx oughta read the actual proggy before connecting to live missiles
asciilifeform: 'To disable forced disconnects, set disc_t to zero' is wrong btw. will give actual off switch on next patch.
asciilifeform: i noticed last night that on none of the piz outages did the thing actually realize it's dead. hence this patch.
asciilifeform: tested just nao w/ this item.
asciilifeform: and yes bvt's reconnector worx a++.
asciilifeform: (at the very least, when live conn, will have pingism from fleanoad erry ~45s )
asciilifeform: diana_coman: the new one simply demands that ~something~ come down the pipe erry disc_t seconds. recc'd value 180 .
asciilifeform: diana_coman: the old one worx a++ on 'organic' i.e. fleanode-initiated disconnects. but sadly not on pipe death
asciilifeform: aite.
asciilifeform: mp_en_viaje: you had some a++ q's re syncism etc, but i'ma answer'em after piz not on fire .
asciilifeform would deploy nao, if had a working box to deploy to...
asciilifeform: if deploying, make sure to see readme & example config re knob.
asciilifeform: tested (by setting absurdly small interval; throws, reconnects, as expected; then by setting 3min -- operates normally, pings typically come erry 45s or so)
asciilifeform: ACHTUNG, panzers! logotron tree updated w/ detect_disconnect.kv.vpatch . << lobbesbot , diana_coman
asciilifeform meanwhile wrote patch for bot to make it actually detect disconnects. is in staging box locally.
asciilifeform: mp_en_viaje: it's a small ddos, as they come, but compounded by the hamfistedness of piz upstream. BB is in the cage atm bazaring w/em
asciilifeform: mp_en_viaje: nope. but iirc you're on a phased array of euro pipes, not individually routable to from outside also eh
asciilifeform: mp_en_viaje: seems like only folx regularly throwing ips in the log, affected.
asciilifeform: mp_en_viaje: summary : rotating ddos, not even limited to piz
asciilifeform: mp_en_viaje: whole thing in log ( diana_coman's and lobbes's, naturally ), it's reasonably compact
asciilifeform: a
asciilifeform: BingoBoingo: i thought whole cage were nullrouted ?
asciilifeform: !!up BingoBoingo
asciilifeform: 'свято место пусто не бывает'(tm)(r)
asciilifeform: incidentally, anyone else think this is not entirely accidentally coinciding with the start of the festivities ?
asciilifeform: http://logs.ericbenevides.com/log/trilema/2019-10-04#1940177 << i oughta expand re this. ddos is cheap but not free, if the 1e6 or whatnot winblowz boxen were evenly split to piss into 20 diff addrs, would not amount to much effect. so traditionally rotates, e.g. 3min to 1, then to next, and so on, in circle.
asciilifeform: does give a little support to the hypothesis that original demasking signal was via irc.
asciilifeform: asciilifeform's www ( still parked on ancient heathen hoster atm ) also not visibly dinged.
asciilifeform: ( either that, or simply outlandish margin of spare pipe bought from last time when he ~was~ included )
asciilifeform: mp's www fwiw doesn't seem visibly affected. so prolly not included on the magick list.
asciilifeform: diana_coman: i expect that before this is through, we'll find out just what tonnage of liquishit the moldavian folx are able to digest
asciilifeform: BingoBoingo: plox to post the next despatch from latch in cleartext, i see no reason to whisper these
asciilifeform: diana_coman: if latech is to be believed, it's a rotating ddos
asciilifeform: diana_coman: that being said, i also suspect that yer box is only standing because piz is taking 90% of the fire
asciilifeform: diana_coman: moldavia has advantage of not being on monkey continent and not relying on single pipe to civilization, i suspect
asciilifeform: diana_coman: seems to be that 'unplug customer' is the only way anybody mitigates ddos.
asciilifeform: diana_coman: indeed they did, i thought it was clear from last hr of #t
asciilifeform: what condition they were in prior to this event, i do not know
asciilifeform: diana_coman: well since latech appears to have in fact pulled our plug, it is no surprise that they're unreachable ~nao~
asciilifeform: even so, if incoming e.g. 50, that 50 oughta consist of a random sampling of the incoming. not 0.
asciilifeform: what, i wonder, would a '200Mb/s or we-pay-you' cost.
asciilifeform: BingoBoingo: i guess this is an illuminative experiment re the q of what it is we actually get for that ( pretty hefty, quite enuff to keep three bus-fuls of orcs in empanadas erry month ) pipe fee. turns out not 200Mb/s , but 'what we feel like aint too hard' ??
asciilifeform: for hr+ nao
asciilifeform: whole thing is offline
asciilifeform: diana_coman: they're both in piz house neh
asciilifeform: soo, open all but the actually used boxes , lol ??
asciilifeform: BingoBoingo: at the risk of repeating, what's yer plan for getting the pipe back ?
asciilifeform: see also this
asciilifeform: and no, per the docs, not optional, i.e. the naked ip is broadcast ~unless~ you log in 'in one shot' via their ssliquishit.
asciilifeform: BingoBoingo: there is already such delay.
asciilifeform: incidentally iirc fleanode only supports cloaks if user connects sslistically. which asciilifeform's bot does not.
asciilifeform: this supports BingoBoingo's hypothesis of 'shrapnel addressed to occupant' (vs 'bullet w/ name on it')
asciilifeform: it does seem that the box where 'uncloaked' lobbesbot connects from , was on the nuke rotation, whereas e.g. asciilifeform's local pipe -- not
asciilifeform: BingoBoingo: i still dun see the matter of 'from where' as settled -- it aint as if the addrs of tmsr www boxen are anyffin but public
asciilifeform: i suppose this could explain what these are for
asciilifeform: and in turn, piz subscribers are also paying for pretend-boxen ?!
asciilifeform: BingoBoingo: what's the plan on latech co's side ? we pay'em and they give us a pretend-pipe ?
asciilifeform: BingoBoingo: through what are you connected ? whole piz house seems to be unplugged
asciilifeform: ( and seems like ddos is only half the problem , the other half is pipe vendor's immunocascade ? )
asciilifeform: piz pipe still dead.
asciilifeform: BingoBoingo: i doubt any of this has anyffin to do with cheapo lurkbots or any similar
asciilifeform: atm that meter's fucking running but the taxi aint movin'!!
asciilifeform: so BingoBoingo what exactly are we paying these people for ? 'isp but if not too many packets' ?!
asciilifeform: and continuing.
asciilifeform: BingoBoingo: longest dulap outage since plugged in, as of nao.
asciilifeform: BingoBoingo: aaand my shells finally fell.
asciilifeform: BingoBoingo: ftr pipe still stone dead
asciilifeform: it aint as if the ips are any kinda seekrit, in all cases
asciilifeform: i dun think cloaks have anyffin to do with it
asciilifeform: seems like diana_coman's box in europistan may've been included in the festivities also
asciilifeform: BingoBoingo: pretty interesting. canhaz detail ?
asciilifeform: piz pipe down !!
asciilifeform: i'ma put the sync thing on backburner, will instead write a proper disconnection detector, cuz this is ridiculous
asciilifeform: really oughta have even moar logotrons, we were down to 1 working unit today
asciilifeform ate the log, will process after tea
asciilifeform: diana_coman: i got this from your logotron
asciilifeform: and loox like it'll need a disconnect detector (e.g. '5min w/out incoming pings or lines' would still be 9000x better than the current 'unplugged for hours and still thinks connected' )