Raspbian (Jessie) | Debian install webmin

Open your terminal emulator or SSH session:

1.) sudo apt-get update && sudo apt-get upgrade -y

2.) sudo apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl apt-show-versions

3.) cd ~/Desktop/

Note:  You can download the package to any directory that you want however, I’m dropping it onto the Desktop so that I get a constant reminder to delete it when I see it.  **I like clean desktops!**

4.) wget https://sourceforge.net/projects/webadmin/files/webmin/1.810/webmin_1.810_all.deb

5.) sudo dpkg -i webmin_1.810_all.deb

6.) connect your browser to webmin by:  https://my-pi-ip:10000

Advertisements

Linux find & stop processes | syslog test logger

Restart

In order to accept a new configuration, you will need to restart your syslog server:

/etc/init.d/syslog stop
/etc/init.d/syslog start

Another way to do this is to find the syslog process and send a HUP signal to it:

ps -ax |grep syslog
6743 ??   0:00.40 /usr/sbin/syslogd
kill -HUP 6743

Testing syslog

To test if syslog has been set up correctly you can log an event to syslog using the “logger“` command:

logger -t test "Here's an example log entry"

Next check your logs configured in Logentries to see if any events have been recorded.

Top 20 Linux system monitoring tools for every admin

ref: http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html

Linux mounting an NFS .ISO to a directory

#step 1:
# mount -t nfs 192.168.255.15:/mnt/vol1/store4/iso1 /mnt/iso1

Ok, this way you’ll have all your ISO files at /mnt/iso1. Now, imagine you want to mount one of these ISOs in loopback:

#step 2:
# mount -o loop /mnt/isos/[isofilename].iso /tmp/blah
/mnt/isos/blah.iso: Permission denied

Permission denied??? Hmmm.. I got stuck with this problem for a bit the first time. Tried changing permissions and exporting parameters, Google, but no answer at all… then… fortunately…. I found it: -o loop,ro!

#step 2 (for real this itme):
# mount -o loop,ro /mnt/iso1/[isofilename].iso /tmp/blah

crafting MITM (Man-in-the-middle) redirects — via arp poisoning

Basic Linux bridging examples w/ iptables adjustments:
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig eth0 0.0.0.0 promisc up
ifconfig eth1 0.0.0.0 promisc up
ifconfig br0 netmask broadcast
iptables -A FORWARD -p all -i br0 -j ACCEPT
iptables -t mangle -A FORWARD -m physdev –physdev-in eth0 -j NFQUEUE –queue-num 0
iptables -t mangle -A FORWARD -m physdev –physdev-in eth1 -j NFQUEUE –queue-num 1

======
Tutorial #1 here:

Linux (LPIC1) skills – How-To get your WiFi runnin’ on Open Suse, Red Hat, Et Al

Tags: Linux, OpenSuse, RedHat, WiFi, Wireless, KDE, Dell, Studio, 1737, 1735
Hardware: Dell studio 1737; however this works in general on other hardware for the aforementioned OS’s by changing the grep statement to your hardware
OS: Opensuse
Issue resolved: WiFi driver
#
#summary of commands to resolve these issues
#lspci;dmesg | grep Broadcom;sudo /usr/instal_bm43xx_firmware
!
!
#step 1:
#find who your wifi manufacturer is, (hint: run the following command then look for wifi references):
!
!
suse253:~ # lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
…snipped output…
04:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
!
!
#step 2:
# grep for references to your wifi manufacturer (Broadcom in my case) in dmesg
!
!
suse253:~ # dmesg | grep Broadcom
[ 5.438335] b43-phy0: Broadcom 4322 WLAN found (core revision 16)
[ 5.461254] Broadcom 43xx driver loaded [ Features: PMNLS ]
[ 5.465063] b43-phy0 ERROR: Please open a terminal and enter the command “sudo /usr/sbin/install_bcm43xx_firmware” to download the correct firmware for this driver version. For an off-line installation, go to http://en.opensuse.org/HCL/Network_Adapters_(Wireless)/Broadcom_BCM43xx and follow the instructions in the “Installing firmware from RPM packages” section.
!
#step 3:
# now follow the instructions that the dmesg so conveniently output above (install wifi microcode)
!
suse253:~ # sudo /usr/sbin/install_bcm43xx_firmware
Downloading b43 firmware
######################################################################## 100.0%
Extracting b43 firmware
This file is recognised as:
filename : wl_apsta.o
version : 666.2
MD5 : e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
…snipped output…
Extracting b43/ht0bsinitvals29.fw

Downloading b43legacy firmware
######################################################################## 100.0%
Extracting b43legacy firmware
This file is recognised as:
filename : wl_apsta.o
version : 295.14
MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3
Extracting b43legacy/ucode2.fw
…snipped output…
Extracting b43legacy/a0g0bsinitvals5.fw

b43 firmware successfully installed.
b43legacy firmware successfully installed.
!
#congrats it should be working : now connect to a wifi ssid
!

Enter SANman!

Openfiler 2.99 Final-

NFS does NOT work:
Portmap and rpcbind are fighting for control. The portmap service has been replaced by rpcbind in most distros, so I don’t think both should be active. Stopping and disabling the portmap service, then restarting the other NFS-related services seems to fix the problem:

# Confirm that mountd is missing (NFSv3 is broken)
rpcinfo -p | grep mountd

# Stop running NFS-related services
service nfslock stop
service nfs stop
service portmap stop
service rpcbind stop

# Make sure NFS-related services start at boot
chkconfig rpcbind on
chkconfig nfs on
chkconfig nfslock on

# Prevent portmap from starting at boot
chkconfig portmap off

# Restart nfs related services without portmap
service rpcbind start
service nfs start
service nfslock start

# Confirm that mountd is available (NFSv3 is working)
rpcinfo -p | grep mountd

NFSv3 mounts (ESXi 4.1u1) should work now. I may be over simplifying the problem, so proceed with caution.

Backup Jobs:

RSYNC documentation:

rsync -avr –inplace –progress –delete /mnt/vol1/store1/vmstore1 /mnt/spare01/backup01/june12/

rsync -avr –inplace –progress –delete /mnt/vol1/store2/vmstore2 /mnt/spare01/backup01/june12/

rsync -avr –inplace –progress –delete /mnt/vol1/store4/iso1 /mnt/spare01/backup01/june12/

rsync -avr –inplace –progress –delete /mnt/vol1/store5/doogie /mnt/spare01/backup01/june12/

rsync -avr –inplace –progress –delete /mnt/vol1/store3/rsync2 /mnt/spare01/backup01/june12/

# rsync -avr –inplace –progress –delete /mnt/vol1/store5/s /mnt/spare01/backup01/june12/

#

Delete a directory and all of it’s contents:

rm -f -r /mnt/spare01/backup01/june12/*