Simon Michuki | 9 Jun 19:34 2012
Picon

Re2:


http://www.driversrun.com/onoace.html?to=532
Ch00se the freed0m t0 w0rk fr0m h0me d0ing w0rk y0u I0ve

___
Another way to express it would be tocall the angle of the blade a five, or six, or a sevenfoot pitch, as the
pitches are measured in feet. siena aeccestane
Sat, 9 Jun 2012 18:34:23

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Simon Michuki | 9 Jun 19:35 2012
Picon

(no subject)


Earn money at home via the Internet
http://www.broadcastproducciones.es/onoace.html?kysjnumberID=785

            Sat, 9 Jun 2012 18:35:01
____________
"  The same if you shook thetable-cloth after sundown." (c) althena winslowe

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
jjeffries | 12 Jun 04:50 2012
Picon

some interfaces won't add?!?

Hey jffnms-folks, I've got a problem that results in some detected
interfaces not being added/addable. Perhaps someone has seen this before?

To start, I am kicking off a "manual" autodiscover from the hosts menu.
All the interfaces on the host will be detected and I can select them,
but only some of them will show up under the post-autodiscover screen
and get added to the db. The rest are ignored as if I didn't check them. 
It's not a browser thing, firefox and chromium both do it.

This happens both on a jffnms install on debian stable that I've had
around forever, and a fresh/current one I installed on a VM just to test
for this problem. I have two cisco 6509s that have rather a bunch of
interfaces in/on them that I've been testing with--they have different
supervisors, card configurations, OS versions, etc, but both elicit this 
behavior.

I did a discover and 'mark all interfaces' on my test install and it 
ends up adding all of the detected/marked interfaces down to some 
certain point, after which nothing else will add.

If I remove one of these hosts and add it back in, then detect 
interfaces and add one or more of the choice of un-addable interfaces 
(for instance a bgp neighbor "interface", I just tried it) the next page 
declares "no interfaces found."

Any idears?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
(Continue reading)

Craig Small | 13 Jun 07:38 2012
Picon

Re: some interfaces won't add?!?

On Mon, Jun 11, 2012 at 10:50:38PM -0400, jjeffries wrote:
> Hey jffnms-folks, I've got a problem that results in some detected
> interfaces not being added/addable. Perhaps someone has seen this before?

Hi,
  You've described the problem well except for one important omission.
What version of JFFNMS are you using?

Debian stable uses JFFNMS 0.8.5 so if it is that one I think there 
were table problems.

 - Craig
--

-- 
Craig Small VK2XLZ   http://enc.com.au/          csmall at : enc.com.au
Debian GNU/Linux     http://www.debian.org/      csmall at : debian.org
GPG fingerprint:     5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Schmitt, David A. | 16 Jun 03:33 2012
Picon

Network Autodiscover broken in 0.9.3

I've been futzing with an install of 0.9.3 (as found on SourceForge) on CentOS 6 for a few weeks as time allows
and finally got to the point where I wanted to set up network autodiscovery. I have around 100 hosts on two
nets that I want to monitor so I figured this would be the easiest way to get baseline hosts info into jffnms.

Well...in 0.9.3 network autodiscover just doesn't work out of the box. I've debugged the code and found (so
far) two major logic errors (one in the nad class and one in the nad admin panel code). After correcting them
I have autodiscover working and can add discovered hosts/interfaces to the monitoring system. I
currently have a large chunk of the host discovery code in the autodiscover_network engine commented out
to circumvent another bug that sometimes keeps hosts and IPs from being inserted into the nad_hosts and
nad_ips tables; I'll look at that later.

How do I submit the code changes? Some of the changes are probably more along the lines of customizations
than bug fixes: I changed the discovery engine's timeout to 30 minutes and allow network blocks as large as
/16 to be searched...I have a big, sparse server block. It takes about 5 minutes to NMAP the /16.

I'm coming back to jffnms after running OpenNMS for about 6 months. THAT is some complex code...

Dave Schmitt

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Gmane