| 19:00 |
billymg |
!c testing... |
| 19:02 |
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? |
| 19:03 |
billymg |
should the UDP ports be open/listening? |
| |
~ 1 hours 49 minutes ~ |
| 20:52 |
asciilifeform |
billymg: if yer pestron is on the racked box, no need to do anyffin in particular re port |
| 20:53 |
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 |
| 21:08 |
awt |
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. |
| 21:20 |
asciilifeform |
billymg: note that the irc frontend is entirely defenseless. see s. 2.5. |
| 21:20 |
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.' |
| 21:21 |
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 |
| 21:21 |
asciilifeform |
aha, ideally oughta live on 1 box |
| 21:22 |
billymg |
awt: by "port open/listening" i meant show up in results of `ss -tuln | grep -i listen` |
| 21:22 |
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 |
| 21:24 |
billymg |
so now my issue is peering with the bot from my primary station (station and bot seem to be running fine otherwise) |
| 21:24 |
asciilifeform |
billymg: are both stations under nat ? |
| 21:25 |
billymg |
asciilifeform: one station is on the rk in your rack, i haven't done anything special with the network config afaik |
| |
↖ |
| 21:25 |
asciilifeform |
a then there not need to do anything re ports |
| |
↖ |
| 21:25 |
billymg |
(this one) |
| 21:26 |
* |
asciilifeform peered with that one, without any apparent issues |
| 21:26 |
signpost |
still wondering wtf is preventing peering with billymg on my end. |
| 21:26 |
* |
asciilifeform must bbl, meat chores |
| 21:27 |
* |
signpost peered with that one, without any apparent issues << doesn't this indicate that my node is trying to send his packets? |
| 21:34 |
billymg |
signpost: at least i'll have a chance to debug from both ends now, hoping i can get to the bottom of it |