208.115.223.167 Record Type: IP Address OrgName: PATRIOT MEDIA AND COMMUNICATIONS, LLC OrgID: PMC-67 Address: 100 Randolph Road City: Somerset StateProv: NJ PostalCode: 08873 Country: US
NetRange: 208.115.192.0 - 208.115.255.255 CIDR: 208.115.192.0/18 NetName: PATMEDIA-3 NetHandle: NET-208-115-192-0-1 Parent: NET-208-0-0-0-0 NetType: Direct Allocation NameServer: NSA.IBBSONLINE.COM NameServer: NSB.IBBSONLINE.COM Comment: RegDate: 2006-05-08 Updated: 2006-11-13 RTechHandle: SYSTE3-ARIN RTechName: System Administrator RTechPhone: +1-888-271-6551 RTechEmail: [EMAIL PROTECTED] OrgTechHandle: SYSTE38-ARIN OrgTechName: Network Engineering OrgTechPhone: +1-732-652-2700 OrgTechEmail: [EMAIL PROTECTED] Karl DeLyria 221 SW Texas St. Portland, OR 97219 503-245-4190 503-816-1127 cell -----Original Message----- From: Michael Richardson [mailto:[EMAIL PROTECTED] Sent: Sunday, July 29, 2007 6:01 PM To: support@pfsense.com Subject: RE: [pfSense Support] SNMP Monitoring of pfSense That attack has restarted from 208.115.223.167 !!!!!!!!!! -----Original Message----- From: Kelvin Chiang [mailto:[EMAIL PROTECTED] Sent: Thursday, June 07, 2007 9:12 PM To: support@pfsense.com Subject: RE: [pfSense Support] SNMP Monitoring of pfSense Hi Tim, Yes, the rrdtool seems to work fine in the graphing, it generates traffic graphs base on interface (but there is still a graph missing for iflabel0 or something like this, not sure whether this is opennms or pfsense problem). The OpenNMS seems to be able to identify it as the source for Trapd, but I have not tested with any event generation. However, OpenNMS can only assign a single "community string" to an IP address (at least this is what I realized), this means that the community string you set on your pfsense for both SNMP and Trapd must be using the same community string. About Router, I am not too sure what happened. I remember seeing OpenNMS identifying a cisco equipment as "router" once before but it does not recognized pfsense as "router". I hope these help, I do not know to much about SNMP and still in the process of exploring pfsense SNMP compatibility with varios open source NMS, currently, OpenNMS seems to do the job best. If it helps... May be we can talk more to see how can generate some documents regarding pfsense and NMS. Regards, Kelvin -----Original Message----- From: Tim Nelson [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:01 PM To: support@pfsense.com Subject: Re: [pfSense Support] SNMP Monitoring of pfSense When you say it doesn't recognize it as a router... in what regard? OpenNMS applies certain attributes to devices that it believes to be routers? Using OpenNMS are you able to poll individual interfaces on your box for graphing and logging purposes? --Tim Kelvin Chiang wrote: > Hi Tim, > > I do not know much to make any comments on what happened to the SNMP > daemon on your pfsense. I am using OpenNMS and it seems to work fine, > except that it does not recognize it as Router. I am using v2c for > SNMP polling. I have not tested the trapd though. > > Regards, Kelvin > > -----Original Message----- > From: Tim Nelson [mailto:[EMAIL PROTECTED] > Sent: Friday, June 08, 2007 10:35 AM > To: support@pfsense.com > Subject: Re: [pfSense Support] SNMP Monitoring of pfSense > > > Any word? > > --Tim > > Tim Nelson wrote: > >> Hello! I would like to monitor traffic totals with SNMP for each of >> my interfaces. I use JFFNMS as my network monitoring system. I enable >> SNMP and set the proper community strings. However, when I poll the >> pfSense box, SNMP does not show the interfaces. Does pfSense use >> nonstandard OIDs? Also, does the SNMP daemon allow for per interface >> monitoring or does it simply provide an aggregate of traffic going >> through the system? Thank you!!! >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]