On Wed, Dec 23, 2009 at 12:00 AM, Evgeny Yurchenko <[email protected]> wrote: > Hello, > # uname -a > FreeBSD 2.0-alpha-alpha 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Wed Aug 5 > 16:55:16 UTC 2009 > sullr...@releng_2_0__freebsd_7_2-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7 > i386 > > as soon as I connect to pfsense with the second ssh session I get blocked: > # pfctl -t sshlockout -T show > 192.168.7.113 > > Could somebody please explain this pfSense' behavior? If it is done > intentionally by developers then why?
Sounds like you're using a snapshot that was creating in the middle of the sshlockout changes that went in. At one point it was locking out IPs after 1 failed login attempt. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
