Hello Ben, this is the output the cmd you requested:
root@myrouter:~# grep -rw xt_recent /etc/modprobe.* /etc/modprobe.d/xt_recent.conf:options xt_recent ip_pkt_list_tot=1000 ip_list_tot=1000 It is difficult to say how I loaded the module last time, before rebooting the system. I know, that I added the iptables rules that use "recent" between 1-2 months ago, so it was after the previous restart - I am quite sure. the date on xt_recent.conf in /etc/modprobe.d confirms it: -rw-r--r-- 1 root root 56 Jul 13 13:18 xt_recent.conf now... since you mentioned /etc/modprobe.d/... I think I need to say that I am sorry for wasting your time. I double checked the ip_pkt_list_tot - it looks like its max is 255 ... I must of add a 0 at to 100, and add the conf in modprobe.d after the module was already loaded... after changing from 1000 to 100 everything is good - I really forgot about adding the options to the conf in modprobe.d... I am really sorry, and thank you Ben, Mike 30.08.2016, 16:36, "Ben Hutchings" <b...@decadent.org.uk>: > Control: tag -1 moreinfo > > On Tue, 2016-08-30 at 11:43 -0400, MikeF wrote: >> Package: src:linux ( not src - binary form ) >> Version: 3.16.7-ckt25-2+deb8u3 >> Severity: normal >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >> * What led up to the situation? >> - system failed to load xt_recent module, iptables rules failed to >> apply >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> - modprobe xt_recent failed - had to use insmod ( successful ) >> * What was the outcome of this action? >> - after successful insmod, iptables rules initialized fine >> * What outcome did you expect instead? >> - no need to insmod of xt_recent > > Please send the output of: > > grep -rw xt_recent /etc/modprobe.* > > What was the previous package version where this worked? > > Ben. > > -- > Ben Hutchings > All the simple programs have been written, and all the good names > taken.
