-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-12-26 at 09:05 +0200, Andre Truter wrote: [ipt_recent]
Yes, this worked beautifully on my test box, but when I implemented it on my production box, the firewall permanently blocked all ssh access for some reson.
Ah!? :-O - From any IP? You probably typed something wrong, or perhaps it is an SLE with different things. I tried it locally, and it certainly allows my to connect, but then, I don't have several machines from which to log in and see if the rest are blocked as a side effect. It shouldn't be.
I have not been able to figure out why.
I don't know, I know very little about iptables. You can try the suse-security list, the firewall knowledgeable people are there. I copied the the idea from there, after all.
Being a production box, I cannot afford to play around with it too much, so I had to take option 2 (change ssh port) until I can find time again when fidgeting with the firewall won't affect service too much.
I understand, of course. Perhaps when people come back from holidays they can comment on this. Happy "past" Christmas, by the way ;-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDr9KxtTMYHG2NR9URAgAlAJ43HlteNuezh9UxADxFCOsY7iEL7ACffv2C HhkcV7HfXJ2Ms3HHSwC7Ag0= =klae -----END PGP SIGNATURE-----