 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2017/08/01
Uptime robot (free for 50 monitors every 5 minutes) is cool:
[Archive.is]
[Archive.is]
These are xs4all fiber connections in Amsterdam and Sassenheim. Despite not mentioned on the xs4all status page [WayBack] XS4ALL | Storingen en werkzaamheden, apparently there was some fiber down time in both places.
The HeldenVanNu fiber connection in Amsterdam was doing fine at that time; those downtimes below were planned on my side:
–jeroen
Posted in Monitoring, Power User | Leave a Comment »
Posted by jpluimers on 2017/03/13
I hadn’t done a lot with pfSense in the past, which I regret a bit since I discovered this really cool feature: Sniffers, Packet Capture – PFSenseDocs.
The coolness isn’t so much that you can capture packets, but that it’s compatible with tcpdump and Wireshark (which has become available natively for Mac like 2 years ago).
Which means that you can download captures and open them in Wireshark.
So it’s as easy as 1,2,3:
–jeroen
Posted in *nix, *nix-tools, Internet, Monitoring, pfSense, Power User, routers, tcpdump, Wireshark | Leave a Comment »
Posted by jpluimers on 2015/01/19
Interesting stuff: Zenoss Open Source Network Monitoring and Systems Management.
Stuff like monitoring NNTP, monitoring HTTP, monitoring DNS, etc.
–jeroen
Posted in *nix, Linux, Monitoring, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2014/07/21
Thanks to Using inotify-wait to check filesystem events I got pointed to How to use inotify-tools to trigger scripts on filesystem events which is now on my research list.
–jeroen
Note that Kristian later on commented this:
The solution shown in the article has race conditions and should not be used.
It is based on
while :
do
inotifywait $options && run-backup
doneand that means that while the backup runs, the directory in question is unmonitored. When the backup finishes, new changes may have been accumulating during backup run, but without being picked up by the backup.
A proper solution would do something like
inotifywait -m $options | while read line
do
do-something-that-logs-multile-changes-and-triggers-backup-once
doneThe important thing is that “inotifywait -m” does not terminate and hence no changes will be lost. It is wrong to run the backup once in full for each change, though.
Posted in *nix, *nix-tools, Linux, Monitoring, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2014/04/19
Reaver-WPS is an excellent tool to test the security of your WPA/WPA2 secured network against the WPS vulnerability.
Getting Reaver 1.4 (which contains wash to scan WiFi networks) to compile out of the box on OS X Mavericks (which is 10.9; why can’t they keep a successive version number in the product name?) didn’t work.
So I downloaded the adapted source pack from one of the comments in Issue 245 – reaver-wps – Support for Mac OS X? – Brute force attack against Wifi Protected Setup – Google Project Hosting (as the diff still not has been applied to the codebase)..
wash will detect most, but not all networks. I’ve net yet tried WireShark, wpscan and wspy yet (they re supposed to get all of them).
To speed up the checking process I tried on install aircrack-ng to associate a Mac with the target network. Compiling aircrack-ng on a Mac from source didn’t work at all. But after installing MacPorts, I could get the MacPorts version of aircrack-ng to work. The bad news: I could not get aircrack-ng to associate to the network.
So these were the commands I used: Read the rest of this entry »
Posted in *nix, *nix-tools, Apple, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, Monitoring, OS X 10.9 Mavericks, Power User | Leave a Comment »
The Wiert Corner - irregular stream of stuff 