billymg: !c testing...
billymg: awt: pest stations communicate with each other via their UDP ports, right? and the IRC port is just for the user to connect to the pest station with an IRC client?
billymg: should the UDP ports be open/listening?
asciilifeform: billymg: if yer pestron is on the racked box, no need to do anyffin in particular re port
asciilifeform: billymg: if it's behind a nat, can open the port, then will escape nat, but won't be needed after the nat driller implemented
awt[asciilifeform|billymg]: billymg: not sure I understand the question - perhaps asciilifeform's inference is correct. But to your first couple questions, yes, interpest comms all over udp. IRC port is only to be used to connect to a single IRC client.
asciilifeform: billymg: note that the irc frontend is entirely defenseless. see s. 2.5.
asciilifeform: 'Traditional IRC offers no provisions for secure authentication or encryption; hence, it is recommended that a Pest station and its IRC client reside in one physical machine. Alternatively, they may run on separate machines and connect via an SSH tunnel or similar mechanism.'
billymg: asciilifeform: yeah, for this reason i moved both the pest station and the bot to another server, rather than trying to keep the pest station running on one server and connect remotely via another
asciilifeform: aha, ideally oughta live on 1 box
billymg: awt: by "port open/listening" i meant show up in results of `ss -tuln | grep -i listen`
billymg: i noticed that when i ran that command the irc ports were listed, but not the udp ports. and since i've also had trouble peering with some other stations i thought perhaps i had something misconfigured
billymg: so now my issue is peering with the bot from my primary station (station and bot seem to be running fine otherwise)
asciilifeform: billymg: are both stations under nat ?
billymg: asciilifeform: one station is on the rk in your rack, i haven't done anything special with the network config afaik
asciilifeform: a then there not need to do anything re ports
billymg: (this one)
asciilifeform peered with that one, without any apparent issues
signpost[asciilifeform]: still wondering wtf is preventing peering with billymg on my end.
asciilifeform must bbl, meat chores
signpost[asciilifeform] peered with that one, without any apparent issues << doesn't this indicate that my node is trying to send his packets?
billymg: signpost: at least i'll have a chance to debug from both ends now, hoping i can get to the bottom of it
awt[asciilifeform|billymg] tests self reference
awt[asciilifeform|billymg]: signpost: you may not be on the latest version: 9978
signpost[asciilifeform]: nah looks like that's what I'm on
awt[asciilifeform|billymg]: signpost: ok. got a badly formatted message from you that used /me. thought I had fixed that bug.