Fernando, Yes it does, thanks. I'll look into fixing that. (ie, an IP:PORT) "ip" address.
But, this registration error is coming from your own local network (10.30.2.238), in the mean time, maybe you can fix that on your end. :-) Lonnie On Nov 20, 2011, at 5:51 PM, Fernando Fuentes wrote: > Lonnie, > > I hope this helps.: > > > Nov 20 16:21:41 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1004" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:21:41 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1004" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:21:52 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:21:52 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:22:55 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:22:55 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:53192' - No matching > peer found > Nov 20 16:24:40 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:25:18 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:45550' - No matching > peer found > Nov 20 16:25:18 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:45550' - No matching > peer found > Nov 20 16:25:43 pbx local0.notice asterisk[3064]: NOTICE[23702]: > app_queue.c:6492 in reload_queue_rules: queuerules.conf has not changed since > it was last loaded. Not taking any action. > Nov 20 16:25:46 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:45550' - No matching > peer found > Nov 20 16:25:46 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from '"1005" > <sip:A1000019493ba7@10.30.2.53>' failed for '10.30.2.238:45550' - No matching > peer found > Nov 20 16:26:41 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:26:44 pbx local0.notice asterisk[3064]: NOTICE[23927]: > app_queue.c:6492 in reload_queue_rules: queuerules.conf has not changed since > it was last loaded. Not taking any action. > Nov 20 16:28:43 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:30:13 pbx local0.notice asterisk[3064]: NOTICE[24473]: > app_queue.c:6492 in reload_queue_rules: queuerules.conf has not changed since > it was last loaded. Not taking any action. > Nov 20 16:30:44 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:30:56 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from > '<sip:fernando%20@10.30.2.53>' failed for '10.30.2.210:45848' - No matching > peer found > Nov 20 16:30:56 pbx local0.notice asterisk[3064]: NOTICE[3108]: > chan_sip.c:24331 in handle_request_register: Registration from > '<sip:fernando%20@10.30.2.53>' failed for '10.30.2.210:45848' - No matching > peer found > Nov 20 16:32:46 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:35:21 pbx local0.notice asterisk[3064]: NOTICE[25332]: > app_queue.c:6492 in reload_queue_rules: queuerules.conf has not changed since > it was last loaded. Not taking any action. > Nov 20 16:36:19 pbx daemon.info ntpd[2974]: synchronized to 38.229.71.1, > stratum 2 > Nov 20 16:36:48 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 16:55:31 pbx daemon.info ntpd[2974]: synchronized to 67.18.208.240, > stratum 2 > Nov 20 16:56:55 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 17:04:10 pbx daemon.info ntpd[2974]: synchronized to 38.229.71.1, > stratum 2 > Nov 20 17:04:59 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 17:14:12 pbx daemon.info ntpd[2974]: synchronized to 67.18.208.240, > stratum 2 > Nov 20 17:15:03 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 17:38:31 pbx daemon.info ntpd[2974]: synchronized to 38.229.71.1, > stratum 2 > Nov 20 17:39:12 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > Nov 20 17:47:04 pbx user.info firewall: ** Restarting Arno's Iptables > Firewall v2.0.0c ** > Nov 20 17:47:12 pbx user.info firewall: ** All firewall rules applied ** > Nov 20 17:47:55 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: (2) > iptables v1.4.9: host/network `10.30.2.238:53192' not found Try `iptables -h' > or 'iptables --help' for more information. > > Thank You Lonnie! > > On Sun, Nov 20, 2011 at 5:45 PM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> > wrote: > Fernando, > > Can you find an example log in /var/log/messages that is generating this > entry ? It would be an asterisk log with "10.30.2.238:53192" (or similar) in > it. > > I think I know what needs to be done to fix it, but I have never run across a > log that would cause this problem. > > Thanks. > > Lonnie > > > > On Nov 20, 2011, at 4:41 PM, Fernando Fuentes wrote: > > > Lonnie, > > > > As promise here is the message again about adpative ban spitting out > > message like crazy after a few fail attempts from my internal network. > > > > Under adaptive ban I have : > > > > ADAPTIVE_BAN_WHITELIST="10.30.2.0/255.255.255.0 10.30.3.0/255.255.255.0 > > 10.30.6.0/255.255.255.0" > > > > The below message is flooding my logs. > > > > What else do you need to see this to properly diagnose it? > > > > The only way to make the message go away is be rebooting and that is > > unacceptable. > > > > > > > > Nov 20 16:32:46 pbx user.info firewall: adaptive-ban: /usr/sbin/iptables: > > (2) iptables v1.4.9: host/network `10.30.2.238:53192' not found Try > > `iptables -h' or 'iptables --help' for more information. > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d_______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
