Adding the LAN range to the allow-fw.p2p will mean it's not passed to moblock and therefor any traffic that's being routed for the moblock host (In my case any traffic from a PC being NATed by the...
Type: Posts; User: noblem; Keyword(s):
Adding the LAN range to the allow-fw.p2p will mean it's not passed to moblock and therefor any traffic that's being routed for the moblock host (In my case any traffic from a PC being NATed by the...
OK, I've now defiantly got the latest moblock-control script, from the (from package 1.0-1 for debian/sid but shouldn't be any different for any other variant). The script adds the following lines...
@lovinglinux It sounds like your moblock-control script is creating different rules from mine and sounds like it might actually work.
I think the best advise we can give anyone would be to ensure...
The allow.p2p file may not have the desired effect as it creates iptables rules to allow traffic out to the allowed range, in from the allowed range and forwarded traffic from either a source or...
@typo99 The tbg Bogon list also includes the RFC1918 private ranges so you'll probably fine you've been blocking your internal network (the moblock logs should tell you what's being blocked). You...
@jre I'm know programmer either but I understand enough of the the code to be able to figure out what it's doing and with the help of google hopefully fix it :)
Only sending new packets to...
Just when I though I'd not seen the unbinding error on the RC of version 9, I got this after moblock did it's daily update the other morning;
Thu Nov 13 07:36:08| NFQUEUE: unbinding from queue...
I found this article about tuning netfilter performance;
http://www.inliniac.net/blog/2008/01/23/improving-snort_inlines-nfq-performance.html
The article is aimed at snort_inline users, but the...
Re: unbinding from NFQUEUE
The error message in the code has a queue number of 0 hard coded, so it's misreporting the queue it just unbound from. I've seen the error myself, with moblock the only...