The commands given below will allow you to create a compressed image of a complete hard disk. Under normal circumstances I would boot from a Linux Live-CD prior to performing these tasks:

dd if=source_disk | gzip > /destination.gz

For example /dev/sda is the source disk and /mnt/usb/image.gz is the destination:

dd if=/dev/sda | gzip > /mnt/usb/hd_image.gz

Then to restore the image:

gzip -dc /mnt/usb/hd_image.gz | dd of=/dev/sda

The format of these commands is very important and if used incorrectly will result in data loss, for which I take no responsibility.

—

Found some of my old Linux discs tonight … thought they deserved a mention… dating from 1997 & 1998.

—

Had a good day Friday, after failing to get relevant information from the manufacturer (been requesting for what seems to be a lifetime). Finally manged to get the 2D barcode imager functional under Linux, what a feeling of accomplishment.

All other significant hardware is supported by the 2.6.30 Gentoo Kernel.  However the finger print reader, camera and HSDPA modem have not been tested as they are not required for the application the unit is going to be used for.

—-

Just a quick post to save some time when updating your Gentoo system (Portage 2.2_rc51) , please note this is just a starting point, feel free to extend these.

nano ~/.bashrc

if [ -e /etc/bashrc ] ; then
 source /etc/bashrc
fi
alias esync='emerge --sync'
alias eupdate='emerge -uavDN --nospinner --quiet --keep-going --with-bdeps=y world'

To update your system just call the following two commands:

esync
eupdate

—

Usually when I need to merge avi files I use avimerge (part of the transcode package), however recently the output of this suffered some serious audio sync issues. So along comes mencoder (part of the mplayer package):

mencoder -oac copy -ovc copy input_1.avi  input_2.avi -o output.avi

—

I’ve had quite a bit of fun over the last couple of nights configuring a VPN connection using Gentoo Linux and the following simplified set-up:

   Home PC  <=> Ethernet ADSL Router <=> Internet <=>   VPN Server
192.168.1.x <=>      192.168.1.1     <=>          <=> xxx.xxx.xxx.xxx

Firstly ensure your kernel has ppp support (2.6.30 kernel configuration options):

# cd /usr/src/linux ; make menuconfig
Device Drivers ->
    Network device support ->
    [*]   PPP (point-to-point protocol) support
    <*>     PPP support for async serial ports
    <*>     PPP support for sync tty ports
    <*>     PPP Deflate compression
    <*>     PPP BSD-Compress compression
    <*>     PPP MPPE compression (encryption)
    <*>     PPP over Ethernet

Next emerge the ppp and pptpclient packages:

echo "net-dialup/ppp mppe-mppc" >> /etc/portage/package.use

emerge --ask --verbose ppp pptpclient

Once you have both ppp and pptpclient successfully installed upon your system edit the /etc/ppp/options.pptp file so that it resembles the one located below (only a few changes are required to this file):

Example options.pptp file for IPREDator

Next edit the /etc/ppp/chap-secrets file so that it resembles the one located below, be sure to add your IPREDator User name and Password to this file replacing the place holders contained within the example file):

Example chap-secrets file for IPREDator

Next create the /etc/ppp/peers/Ipredator file so that it resembles the one located below, again be sure to add your IPREDator User name to this file replacing the place holder contained within the example file):

Example Ipredator file for IPREDator

Now essentially all that is required is getting the routing set up correctly so that traffic flows to the correct place on the network. What I have below are some modified ip-up and ip-down scripts that may be used, some minor modifications maybe required to tailor the scripts to your specific network settings. These scripts are based upon those from the All Traffic Through Tunnel section of the PPTP Client website (many thanks to the original author as it pointed me in the right direction). I believe that both of these scripts should be set as being executable (chmod +x /etc/ppp/ip-up.d/60-ip-up-tunnel.sh).

ip-up script (/etc/ppp/ip-up.d/60-ip-up-tunnel.sh):

#!/bin/bash
# pppd ip-up script for all-to-tunnel routing

# name of primary network interface (before tunnel)
PRIMARY=eth0

# address of tunnel server
SERVER=$5

# gateway ip address (before tunnel - adsl router ip address)
GATEWAY="192.168.1.1"

# provided by pppd: string to identify connection aka ipparam option
CONNECTION=$6
if [ "${CONNECTION}" = "" ]; then CONNECTION=${PPP_IPPARAM}; fi

# provided by pppd: interface name
TUNNEL=$1
if [ "${TUNNEL}" = "" ]; then TUNNEL=${PPP_IFACE}; fi

# if we are being called as part of the tunnel startup
if [ "${CONNECTION}" = "Ipredator" ] ; then

 # direct tunneled packets to the tunnel server
 route del ${SERVER} dev ${TUNNEL}
 if [ "${GATEWAY}" = "" ] ; then
   route add -host ${SERVER} dev ${PRIMARY}
 else
   route add -host ${SERVER} gw ${GATEWAY} dev ${PRIMARY}
 fi

 # direct all other packets into the tunnel
 route del default ${PRIMARY}
 route add default dev ${TUNNEL}
fi

ip-down script (/etc/ppp/ip-down.d/60-ip-down-tunnel.sh):

#!/bin/bash
# pppd ip-down script for all-to-tunnel routing

# name of primary network interface (before tunnel)
PRIMARY=eth0

# server ip address (for tunnel)
SERVER=$5

# gateway ip address (before tunnel - adsl router ip address)
GATEWAY="192.168.1.1"

# provided by pppd: string to identify connection aka ipparam option
CONNECTION=$6
if [ "${CONNECTION}" = "" ]; then CONNECTION=${PPP_IPPARAM}; fi

# provided by pppd: interface name
TUNNEL=$1
if [ "${TUNNEL}" = "" ]; then TUNNEL=${PPP_IFACE}; fi

# if we are being called as part of the tunnel shutdown
if [ "${CONNECTION}" = "Ipredator" ] ; then

 # direct packets back to the original interface
 route del default ${TUNNEL}
 route del ${SERVER} dev eth0
 if [ "${GATEWAY}" = "" ] ; then
   route add default dev ${PRIMARY}
 else
   route add default gw ${GATEWAY} dev ${PRIMARY}
 fi
fi

Here is what the original routing table looks like, you will notice that all traffic is routed to the ADSL Gateway (in this case 192.168.1.1):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
loopback        127.0.0.1       255.0.0.0       UG    0      0        0 lo
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

Here is what the routing table looks like when the tunnel is running, you will now notice that traffic to the VPN Server is routed to the ADSL Gateway (192.168.1.1), all local network traffic (192.168.1.xxx) is routed to the associated network interface (eth0), and that all other traffic is routed to the VPN interface (ppp0):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
xxx.xxx.xxx.xxx 192.168.1.1     255.255.255.255 UGH   0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
loopback        127.0.0.1       255.0.0.0       UG    0      0        0 lo
default         *               0.0.0.0         U     0      0        0 ppp0

To start the connection open a terminal window and enter the following command:

pon Ipredator

To enable debug inorder to diagnose connection issues use the following command:

pon Ipredator debug dump logfd 2 nodetach

I hope this has been of some use to you, not only for configuring IPREDator but for other VPN connections that use the PPTP protocol..

—

Following on from my post late last year, there is another excellent BitTorrent client for the GNOME Desktop, and that is Deluge. To be honest with you  I had a few issues with Transmission and download speed. These issues were resolved instantly by Deluge, and I have been using this as my preferred BitTorrent Client for several months now.

Currently at version 1.1.7 it should service all your BitTorrent needs (emerge -av deluge). The only negative I have with this application is that of high CPU usage.

Update: The high CPU usage has been resolved with version 1.1.8, seems it was due to displaying the torrent speeds on the title bar of the main application window. So either upgrade to 1.18 or disable this option within the configuration options window.

Update: Another good feature of this application is the ability to import block lists into it, such as the level1.gz from http://blocklistpro.com/. This helps reduce nasties connecting to you while you are downloading your favourite Linux Distribution (Gentoo Minimal x86 / Gentoo LiveCD i686).

—

I have some Linux compatible PCMCIA/PCCard WiFi adapters available for purchase.  They are all in good condition (some are as new, only used for testing purposes). They are detailed below, if you require any further information then please feel free to contact me.

15 11 x Cisco Aironet 350 Series – AIR-PCM352 (AIR PCM350 Series) – PCMCIA – WEP (64/128).

3 x Cisco Aironet 350 Series – AIR-LCM352 (AIR LCM350 Series) – PCMCIA – WEP (64/128) – Without detachable antenna.

1 x Cisco Aironet 350 Series – AIR-LCM352 (AIR LCM350 Series) – PCMCIA – WEP (64/128) – With detachable antenna.

6 4 x Cisco Aironet 802.11a/b/g - AIR-CB21AG-E-K9 – PCCard (32bit) – WEP (64/128)/WPA/WPA2.

3 2 x Orinoco Gold – PC24E-H-FC (Lucent Technologies) – PCMCIA (16bit) – WEP (64/128).

—