@chirpy The only thin you have to watch is as mentioned, that the alternative SSH port is in the firewall
Thanks, I thought you might have been hinting there was something new
@chirpy You can go th extra steps of changing /etc/apf/firewall and pre* and post* scripts to have their settings applied to the new SSH port, but it's not required.
That got me looking around. In /etc/apf/firewall (.9.4-7) I find the following lines around 174
Code:
# SSH
$IPT -A INPUT -i $IN_IF -p tcp --sport 22 --dport 513:65535 -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPT -A INPUT -i $IN_IF -p tcp --sport 1024:65535 --dport 22 --syn -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPT -A INPUT -i $IN_IF -p udp --dport 22 -m state --state ESTABLISHED -j ACCEPT
... is changing 22 to my custom port an added measure then? I've had to leave 22 open in my outgoing in the conf, because sometimes I do have to SSH to this box, and then use it to SSH to another one, which does use 22 for SSH. I'd have to be careful not to interfere with that. I'm not sure what you're referring to by 'pre* and post* scripts'?
One last thing... am I correct in my understanding that I can easily lock myself out and shouldn't use BFD if I don't have a fixed IP at my local workstation?
salut,