Posts

Having some fun. Definitely need a better battery.

[ 0.184110] pci 0000:04:04.0: [10ec:8139] type 0 class 0x000200
[ 3.822258] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 3.822281] 8139cp 0000:04:04.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
[ 3.822574] 8139too: 8139too Fast Ethernet driver 0.9.28
[ 3.822625] 8139too 0000:04:04.0: Chip not responding, ignoring board
[ 3.822675] 8139too: probe of 0000:04:04.0 failed with error -5

On a Debian machine.

The solution was changing PCI slot , blowing away all the dust in the mobo PCI slot and on the pins of the PCI card, and gently inserting and removing it a couple of times.

Source.

He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you. -- Nietzsche

Best NSA related comment in weeks.

Rather simple script. Using log file instead of management interface.

Part has to run as Root (due to Munin most likely not having access to read the log files. Working with the management interface could solve this.

Create /usr/local/bin/getVpnUsers.sh:

#!/bin/bash
echo "VPN.value `cat /var/log/openvpn-status.log | sed -e '1,/Common Name/d' | 
sed -e '/ROUTING TABLE/,$d' | wc -l`" > /tmp/.vpn_munin.txt

You can change the name of VPN.value to the VPN name and/or add multiple lines (each with a different NAME.value if you’re running more than one VPN user. Be sure to cat the right log file).