21:1/100 HUB was not processing packets etc. for around
20 hours after I accidentally borked it's config when
delisting a node. Apologies for the quiet time in packet
flow. Normal service should have resumed now.
21:1/100 HUB was not processing packets etc. for around 20 hours after I
accidentally borked it's config when delisting a node. Apologies for the
quiet time in packet flow. Normal service should have resumed now.
Thanks Deon for letting me know something was amiss.
Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz
--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
I was wondering what was happening :)
21:1/100 HUB was not processing packets etc. for around 20 hours after I accidentally borked it's config when delisting a node. Apologies for the quiet time in packet flow. Normal service should have resumed now.
Thank you for solving this so quickly, Avon! Thanks again for all your work keeping us connected.
Thank you for solving this so quickly, Avon! Thanks again for all your work keeping us connected.
Did you forget to remove the route statement? I do that all the time, so I've grown into the habit to run 'tparser' after any kind of config change. :)
Yes, thank you Avon for all your work :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 16 (1 / 15) |
Uptime: | 02:15:44 |
Calls: | 500,920 |
Calls today: | 7 |
Files: | 109,372 |
D/L today: |
18,023 files (2,704M bytes) |
Messages: | 305,081 |
Posted today: | 7 |