**** BEGIN LOGGING AT Wed Aug 10 02:59:57 2011 Aug 10 11:37:57 hi Aug 10 11:40:33 I have a problem: my fonera is undergoing an infinite number of connection attempts from IP addresses public (via ssh) Aug 10 11:40:39 http://pastebin.com/MzQCRm1m Aug 10 11:43:27 If I remember correctly, once there was a possible maximum number of attempts, after which incoming connections (by a determinate ip) were rejected Aug 10 11:44:41 maybe this control does not work if the fonera is set in bridge mode (once there was this problem, but I remember that he had been solved) Aug 10 11:47:12 the attack is continuing always by (for now) the same ip: http://pastebin.com/qPNeZ3jU Aug 10 11:58:43 Ey giuseppeg88 Aug 10 11:59:23 There should be hammer protection, limiting the maximum number TCP connections per minute or something like that Aug 10 12:00:12 hi blathijs Aug 10 12:00:27 giuseppeg88: http://trac.fonosfera.org/fon-ng/ticket/839 Aug 10 12:00:31 Ticket is stil open Aug 10 12:00:56 mmm Aug 10 12:01:28 I remembered that I had resolved in some way... Aug 10 12:01:35 The problem is that in bridge mode, connections really come from the LAN Aug 10 12:01:45 except when you apply port forwarding... Aug 10 12:02:14 giuseppeg88: Perhaps you're thinking of http://trac.fonosfera.org/fon-ng/changeset/1672 ? Aug 10 12:05:26 blathijs: I'm going to lunch, see you later... Aug 10 13:51:42 I'm back Aug 10 13:56:37 searching in the wiki, (maybe) I remembered how I had temporarily solved... Aug 10 13:56:39 if I remember correctly I used these commands: http://wiki.fon.com/wiki/Fonera_Development#Anti-hammering Aug 10 13:57:38 Ah, right Aug 10 13:57:54 but those commands are on the wiki from before the hammer protection was in the firmware Aug 10 13:57:58 I remember that after you set the bridge mode, if entered manually, the protection was beginning to work Aug 10 13:58:14 and it is unconditional, so it also "protects" from hosts on the LAN Aug 10 13:58:42 (e.g., if you make a few subsequent SSH connections, for example SSH, SCP, SSH, it locks you out as well) Aug 10 13:59:02 yes Aug 10 14:03:11 I just tried it: now unfortunately this solution doesn't work anymore... this may be due to some change that was made ​​recently? Aug 10 14:09:18 Not that I can think of, this looks like it should work (since it completely circumvents all chains and works on the INPUT chain directly) Aug 10 14:10:41 ok... I try again after a reboot Aug 10 14:17:03 yes!!! it works. now I do so that this protection starts by itself at startup. Thanks for your help Aug 10 14:26:26 You can put the commands in /etc/firewall.user (IIRC, check /etc/config/firewall) Aug 10 14:26:54 which is loaded automatically since 2.3.7.0 Aug 10 14:58:42 yes. I put the commands in /etc/firewall.user, I reboot and the it works **** ENDING LOGGING AT Thu Aug 11 02:59:56 2011