The memory ain’t quite like it should be, I’ve got this slight problem with the protocols around the 20-25 mark. It’s 20, 21 for ftp, 22 for ssh, 23 for telnet and 25 for smtp.What I’m wondering is who’s on 24? Apparently this port has fallen off the protocols use list. It’s been taken by the any private mail system, which I don’t think exists. Considering it’s one port shy of smtp, that kind of explains it just a tad. The only problem I’ve never encountered anything legitimate that has made use of this port.
Dodgy power supplies can cause problems with network switches. Given a choice, I’ll take a level 2 over level 3 switch for local networks. The reason is quite simple – when you have a level 2 switch when the power fluctuates and the switch resets it doesn’t have the annoying tendency to reset all the effing network connections on the network; whereas with the level 3 switch it has the annoying tendency to tell everything on the network that the connection has been reset. A bit like the Sun network terminal servers – the default configuration causes them to send a ‘brk’ to each of the connected machines if they are switched off and on. The best workaround we had when we had to move an NTS was to unplug all the machines, move the NTS and plug it back in. Because the machines weren’t sent to the OK prompt, they were able to work just fine for the 45 minutes it took to move the NTS.
One Reply to “Old Grey Mare”
Comments are closed.
you could disable the kybrd break sequence in /etc/default/kbd and then you don’t have to disconnect systems from the nts