Skip to main content

Timeline for ipfw ruleset limit

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Jan 8, 2017 at 15:00 comment added charleslcso Sent! Please check
Jan 8, 2017 at 13:44 comment added klanomath @charleslcso So if you have a line containing 192.168.0.0/24 use aaa.bbb.ccc.ddd/ee but for an additional network 10.1.0.0/16 use aba.bab.ccc.ddd/ff or ggg.hhh.iii.jjj/ff. If you want to send it by email use my nickname_here(at)googlemail.com
Jan 8, 2017 at 13:39 comment added charleslcso It's too troublesome to create a 10k rule set, that's for sure! Will somehow send it to you!
Jan 8, 2017 at 13:37 comment added klanomath @charleslcso Can you send me the ruleset somehow (or publish it somehwere). I tried to find a >10k lines ruleset in the Internet but failed and I was too lazy to create one myself. To some extent you may mask your private IP addresses by using a aaa.xxx.yyy.zzz notation for different local IPs so I can easily replace them by IPs in my virtual network.
Jan 8, 2017 at 13:32 comment added charleslcso Anyone can help?
Jan 6, 2017 at 0:55 comment added charleslcso Edited the question with output from sysctl -a
Jan 5, 2017 at 15:46 comment added klanomath @charleslcso the *.static_count value can't be increased or decreased because it simply represents the number of all static rules but doesn't limit them. Please add the output of sysctl -A | grep net.inet.ip.fwto your question. You will also get some unrelated kern.* entries - remove them before adding the output.
Jan 5, 2017 at 15:32 comment added charleslcso Found out that putting the above in file survives reboots, but it has no effect on how many dyn rules ipfw can store. Found out that the number of active rules in ipfw is 9963, which coincides with the value net.inet.ip.fw.static_count=9963 from sysctl. But having a larger value stored in /etc/sysctl.conf won't make a difference... after reboot the active value is still 9963...
Jan 5, 2017 at 15:10 history answered klanomath CC BY-SA 3.0