Nagios is a free, open-source web-based network monitor developed by Ethan Galstad. Nagios is designed to run on Linux, but can be also be used on Unix variants. Nagios monitors the status of host systems and network services and notifies the user of problems.
In common with many open source utilities, installation requires a degree of system administrator experience. Nagios is definitely not for the novice, unless you are prepared to put the effort in learning the basics. But with a wide range of features, including a number of web interfaces, Nagios is a very useful, feature rich monitoring tool.
A large number of plug-ins available from the Nagios Library, means you can design its capabilities to your own requirements. Amongst others, Nagios monitors services such as SMTP, POP3, HTTP, PING and resources such as disk and memory usage, log files, processor load and so on and integrates with the Sensatronics IT Temperature Monitor to allow monitoring and alerting of server room and device temperature to your own parameters.
Nagios will also allow scheduling so that for instance if you planned network outage you can suppress host and service notifications. Nagios also allows users the flexibility to develop custom host and service checks. All the plug-ins are available for download from the Nagios library. It is also possible to set up a hierarchy of alerts for instance if alerts are not responded to.
How does Nagios work?
The monitoring daemon runs intermittent checks on hosts and services you specify using external plugins which return status information to Nagios. When problems occur Nagios alerts you via email, instant message, SMS. Current status information, historical logs, and reports can all be accessed via a web browser.
Supported Nagios Platforms
Nagios runs on Linux and Unix variants. Nagios does not support Microsoft Windows.
Nagios is licensed under the GNU (General Public Licence) which means that it is free for personal or commercial use and you may copy, distribute and/or modify Nagios. If you create a Nagios distribution, you must retain the GPL licence terms and you must obtain written permission from Nagios Enterprises to use the Nagios trademark.
As with other open source projects, support is available and given freely by developers and users via mailing lists, forums and FAQs. In addition, there are a number of companies who offer consulting and support contracts for Nagios.
If you have the skill and the time to install Nagios and get it up and running, it offers excellent value (ie for nothing) and functionality perfect for the small to medium enterprise that would balk at the cost of traditional monitoring systems.
Article to install NAgios will be posted soon !.....
So you want to hack your 360. Have no idea where to start?
This thread should give you a general idea on what you can do with your 360.
Lets get started. First of all you'll need to determine the age of your console. This will give you a general idea of what hack you can apply.
On the back of the 360 there is a sticker near the AV port (Phat*&Slim*) On that you'll find the MFR date as well as the Console Serial and Product ID.
Determining the age of the 360
You'll need to write down your MFR date. This will roughly tell you what board you have in your 360.
Xenon: 2005 - 2007 203w power supply, can be JTAGged and RGH'd (14699 only) & R-JTAGged.
Zephyr: 2007 - 2008 203w power supply, can be JTAGged and RGH'd (Hard to achieve) & R-JTAGged.
Opus: Only from RRoD Repairs from MS (rare revisions) 203/175w power supply, can be JTAGged and RGH'd & R-JTAGged.
Falcon: 2007 - 2009 175w power supply, can be JTAGged and RGH'd & R-JTAGged.
Jasper: 2008 - 2010 …
You'll need a Wii remote or "Wiimote" to start with. Normally they are about $40, in the end that is not too bad for a pretty awesome sensor. Otherwise you can check out ebay or elsewhere for used or broken Wii remotes.
You'll need to rip apart the case. It has some crazy three pronged screws. I didn't want to completely trash the case so I made a small tool to take it apart.
Now you need to desolder the 8 pins and the 2 struts holding the camera on the board. I used some desoldering braid. It wicks the solder away and makes it easy to get the camera out. Be careful, don't break the camera!
You might want to keep the rest of the parts. You might be able to scrap other parts. Also, If you decide later to use the Wiimote again, you could always put the camera back in.
Step 2: Interface Circuitry
Im back with the second part of the post. At the end of the last post, we successfully re-routed all the traffic from the victim’s computer to the router through our computer.Next, we have to capture their facebook cookies through wireshark. So How do you go about doing that? It’s very simple actually. Open up wiresharkGoto capture – > Interfaces in the top menu and select your interface. It’s usually the one which has an IP address and a certain number of packets flowing through it.Next goto capture and click on start.. It should look something like this.
This window has all the packets sent from the victim’s/victims’ computer to the router and all the packets sent from the router to the victim.
Next in the filter type “http.cookie contains datr”. You ask why? Because, when a user logs in to facebook, he is given some cookies which is unique to him. If we replace our cookies with the victim’s cookies, we can login to his account as then facebook wont know the di…