#asciilifeform | 2022-09-18

and not simple matter of 'they ordered' -- reich cannot operate w/out printolade; printer cannot operate w/out the 'kinetic' component of fiatola hegemony

00:42

http://logs.nosuchlabs.com/log/asciilifeform/2022-09-17#1113834 << pretty close to the '% who eat recycled food' neh

00:42

Logged on 2022-09-17 21:53:57 mats: in other news, TIL 73.6% of US adults over 20 are overweight or obese https://www.cdc.gov/nchs/fastats/obesity-overweight.htm

00:42

( lulzily in ru to this day most common reason for rejecting a conscript is 'underweight' )

00:43

http://logs.nosuchlabs.com/log/asciilifeform/2022-09-17#1113837 << ru lost these colonies in sovok collapse, so they were picked up (originally by usg, nao cn will)

00:43

Logged on 2022-09-17 21:55:14 mats: usg mouthpiece https://thediplomat.com/2022/07/china-kyrgyzstan-uzbekistan-railway-opportunities-and-challenges-for-china

00:45

mats: orthogonally, are you interested in getting on pestnet?

00:45

other folx would prolly comment interestingly re e.g. the noose linx mats digs up

~ 10 hours 36 minutes ~

11:22

awt, i seem to have lost peering. is your ip still 200.122.181.26?

11:23

actually not sure what happened but none of the peers on my list (ascii, trinque) respond

11:32

also i tried changing protocol versions, still nothing

11:33

phf: asciilifeform's current addr

11:33

(pest) 2022-09-14 asciilifeform: PeterL: 100.15.116.69:1337

11:34

*

asciilifeform rolled back to blatta 9973, which dun have addrcast yet

11:34

phf: does your cl pestron have it ?

11:35

to quote some 90s comedy "i ain't seeing shit"

11:35

phf: from all peers or only awt & asciilifeform ?

11:35

that's the only two peers i've ever really tested, so i'm not sure if other creds are still even legit

11:37

should be, if folx threw the keys in their stations, blatta dun have rekey yet

11:37

but i sent a couple of broadcast and prod messages to the ip you gave, with version FB, and i'm not getting any kind of reaction

11:37

phf: is yours in a nat ?

11:38

yes, but it's always been in a nat

11:38

hmm

11:38

i open up one socket, which i reuse for all things, and as soon as the socket is up, there's a 10s garbage packet going out to keep the outbound/inbound alive

11:39

but nothing has changed to this strategy

11:39

phf: in asciilifeform's at yer currently 137.103.133.228:16928 ( 17 july ) , which loox like an ephemeral port, it prolly closed

11:39

doesn't explain why not connects w/ asciilifeform's tho (oughta, asciilifeform put in a fwd rule)

11:39

the ip has also rotated, but that means that you're not getting anything from me, which should be at this point a mixture of garbage, broadcast and prod

11:40

what's the pest version number that your blatta.py says?

11:41

perhaps my upstream decided to filter suspicious udp packets

11:42

9973

11:43

no, pest protocol

11:43

a hm

11:43

0xfc

11:43

( lives in message.py )

11:44

well, that didn't make any difference

11:46

would you kindly mind posting your at table to a paste

11:46

i suspect you have fresh awt ip there also

11:47

when i finish my pest™ it'll have a web accessible at table, for bootstrapping

11:49

phf: try peering w/ dulapbot btw. key & addr.

11:51

asciilifeform: is 9973 the previous stable version? i.e. whatever you guys were running for weeks before?

11:51

asciilifeform's curr. at for phf

↖

11:52

phf: 9973 is current 'stable' blatta

11:52

on dulapbot still running 9976

11:52

right

11:53

phf: btw try port 38144 for asciilifeform's station ( loox like from dulapbot's pov he's on an ephemeral? and fwd rule is borked ? )

11:55

web config (or otherwise outtaband) at would be quite handy

11:56

dulapbot ftr dun have nat issue, it is in the rack, so oughta work

11:58

asciilifeform: yeah, i'm going to try dulapbot instead but need to get to machine with keys. i don't think sending to your ephemeral port, without you also sending to my ephemeral port will work. because and since we're both behind nat, we have to warm up connection state tables

11:59

phf: appeared to work w/ PeterL on 9973 (where addrcast), whether worx depends on what kinda nat (typically ignores origin, but some do not)

11:59

we'll need this, eventually, asciilifeform suspects, for 'final solution to nat'

↖

11:59

(pest) 2022-09-07 asciilifeform: afaik with 'symmetric' nats of the type apparently victimizing jonsykkel , the only drill that worx is to hammer random ports, from both directions, until match

12:00

*

asciilifeform must bbl

12:00

err, 9972 where addrcast

12:00

*

asciilifeform genuinely bbl

12:00

asciilifeform: addrcast as far as i understand by design (it's your design!) uses intermediary to tell both stations what corresponding epthemeral ports are. so that station start broadcast (of e.g. garbage) and there's a few packets lost, before mutual state table relationship is established

12:02

so e.g. a, ip 1, port 1, b ip 2, port 1: a sends to b, now a's router knows that there's 1:1 - 2:1 connection, but this packet is rejected by b, until b ALSO sends something to a, and now b's router knows 2:1 - 1:1 connection. b's packet will go through, if it went after a's packet. and after b sent his packet, a will start recieving packets also

12:03

(aka hole punching technique, but i've explained it in a detail above, because people might forget or not know what hole punching actually entails)

12:07

you could probably just send the whole 65536 range, but i like the idea of sitting there, trying to hit random ports. sort of like digging an prison escape tunnel with a robotic spoon

~ 38 minutes ~

12:46

blatta network is not being healthy. so i did a transmit through dulapbot, which appeared on logs.nsl about 2 minutes later, and it's been another 3 minutes and it's still not on bitdash

12:46

trying to send packets through awt, with updated AT and i'm not getting any reaciton

12:48

phf: loox like it got logged on bitdash in the end

12:48

yeah, 10 minutes later

12:48

phf: there's defo a bug w/ embargo logic in all blattas to date ( partly asciilifeform's fault, that section of spec is laughably incomplete )

12:49

phf: the random dig algo is not only aesthetically appealing but afaik actually faster, statistically, than any possible deterministic one

12:51

well, i'm getting packets from awt, but sending packets out seems to take Very Long Time™

12:51

phf: likely because he aint peered w/ dulapbot , and so it walks from the latter to asciilifeform then to him, and each time sits in the hearsay clink

12:52

i'm talking to him directly now

12:52

a and still slow?

↖

12:52

yeah, i sent "test", got back message type 3, and it's been sitting couple of minutes now (shouldn't that buffer be 10s?)

12:52