Date: Fri, 16 Apr 2010 00:11:03 -0400 From: DAve <dave.list@pixelhammer.com> To: freebsd-pf@freebsd.org Subject: Re: Fwd: Issues with pf and snmp Message-ID: <4BC7E357.2070203@pixelhammer.com> In-Reply-To: <4BC72457.1000202@pixelhammer.com> References: <4BBF59E2.80303@pixelhammer.com> <m2r7731938b1004091234yeaf9eaa1i92a48fbf28610408@mail.gmail.com> <4BBF8629.1090109@pixelhammer.com> <h2s7731938b1004091716z2f460770w2eb2034c8d6a411c@mail.gmail.com> <q2m7731938b1004091718m17ab4750u66308a1120337065@mail.gmail.com> <4BC72457.1000202@pixelhammer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
DAve wrote: > Peter Maxwell wrote: >> Can't see anything obvious but have you tried these things in the event >> something strange is going on: >> >> - removing the scrub rule; >> >> - removing the antispoof rule; >> >> - add 'log' to the the pass rules and then check to see if there are any >> other snmp udp packets getting passed/dropped in the wrong place. > > A good idea. I will try to get that done this evening, though I am > running 100% until Monday. > Nope, no scrubbing no antispoof, same result exactly. I did check snmpget and it seemed to work. I will check which oid is next in line and see if I can get that value next. It appears some restriction on the snmpwalk, possibly a limit on how many results are being returned? (Shooting in the dark now). I use Cacti everywhere within our networks, no snmpwalk is a show stopper for me here... DAve -- "Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it." John Adams http://appleseedinfo.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BC7E357.2070203>