Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.

First you need to download .deb package from here now you need to install this .deb file by double clicking on it or using the following command

sudo dpkg -i google-chrome-stable_current_i386.deb

If you see any dependency errors use the following command

sudo apt-get -f install

You can open google chrome from Applications > Internet -> Chromium Web Browser

Related posts

• No related posts.

But for some reasons the cookie-management has only 3 modes, without the ability to define whitelists or blacklist with specific domains, probably the google-boys knows who would be blacklist-chartleader. However, for me this is a knock-out criterion and as I couldn’t find a better solution, here is a quick and dirty workaround for a domain-blacklist, at least it prevents persistent cookies for special domains while cookies are generally accepted.

The chrome-cookies are stored in a sqlite database file, the following script deletes all cookies from defined domains before starting chrome (sqlite3 package is required), furthermore the “local state” file will be deleted (contains some client information) and the UserAgent ID can be faked (eg Safari/WinXP, commented out) .

Maybe this script it’s useful to someone, just customize it to your needs and save it to /usr/bin

#!/bin/sh
#satelietentier@gmx.de
#

CONFIG_DIR="$HOME/.config/google-chrome"
COOKIES_FILE="$CONFIG_DIR/Default/Cookies"
LOCAL_STATE_FILE="$CONFIG_DIR/Local State"

#delete cookies containing one of that strings in domain-name before starting chrome
COOKIES_BLACKLIST=(
'google'
'microsoft'
'bing.com'
'yahoo'
)

for (( i=0;i<${#COOKIES_BLACKLIST[@]};i++)); do
echo "delete from cookies where host_key like '%${COOKIES_BLACKLIST[${i}]}%';"
sqlite3 $COOKIES_FILE "delete from cookies where host_key like '%${COOKIES_BLACKLIST[${i}]}%';"
done

#set AGENT_ID to fake the user-agent identification
#AGENT_ID="Mozilla/5.0 (Windows; U; Windows NT 5.1; en) AppleWebKit/522.11.3 (KHTML, like Gecko) Version/3.0 Safari/522.11.3"

#rubbish
rm "$LOCAL_STATE_FILE"

if [ -n "$AGENT_ID" ]; then
exec `google-chrome --user-agent="$AGENT_ID"`
else
exec google-chrome
fi
exit 0


Related posts

• No related posts.

If you forgot your root password for your debian server use the following procedure to reset.

Boot to the GRUB menu. Then, press <e> (for edit) before Linux has a chance to boot.

Using your keyboard arrow keys, move the cursor down a line or so, and press <e> (for edit) again, you should now be on the kernel line, and press <End> to go out to the very end of that line. Now hit the spacebar once, if necessary, to add a space, and then add one of the folllowing:

init=/bin/bash

or

init=/bin/sh

Then press <Enter>, and you’re back at the kernel line, press <b> (for boot) and the computer will proceed to boot to a root prompt.

At this point, the root file system is still mounted read-only, so enter the following command:

mount -n -o remount,rw /

Then type:

passwd

Enter your new password. Retype if asked to confirm.
Then restart the machine by typing:

reboot

Now you should be able to login with your new root password as required.

Related posts

• forgot root password or reset root password in Debian (13)

Learn the basics of the Linux operating systems. Get to know what it is all about, and familiarize yourself with the practical side. Basically, if you’re a complete Linux newbie and looking for a quick and easy guide to get you started this is it.

You’ve probably heard about Linux, the free, open-source operating system that’s been pushing up against Microsoft. It’s way cheaper, faster, safer, and has a far bigger active community than Windows, so why aren’t you on it? Don’t worry, Makeuseof.com understands. Like many things, venturing off into a completely unknown world can seem rather scary, and also be pretty difficult in the beginning. It’s while adapting to the unknown, that one needs a guiding, and caring hand. This guide will tell you all you need to know in 20 illustrated pages, helping you to take your first steps. Let your curiosity take you hostage and start discovering Linux today, with this manual as your guide! Don’t let Makeuseof.com keep you any longer, and download the Newbie’s Initiation to Linux. With this free guide you will also receive daily updates on new cool websites and programs in your email for free courtesy of MakeUseOf.

Related posts

• No related posts.

The GNU/Linux systems have reached an important level of maturity, allowing to integrate them in almost any kind of work environment, from a desktop PC to the sever facilities of a big company.

In this ebook “The GNU/Linux Operating System”, the main contents are related with system administration. You will learn how to install and configure several computer services, and how to optimize and synchronize the resources using GNU/Linux.

The topics covered in this 500+ page eBook include Linux network, server and data administration, Linux kernel, security, clustering, configuration, tuning, optimization, migration and coexistence with non-Linux systems. A must read for any serious Linux system admin.

Related posts

• No related posts.

The Ubuntu Karmic Koala Bible is a guide that’s both great for Linux initiates, and invariably useful for Linux intermediates. With over fifty pages of copy-paste tutorials, this guide belongs in the virtual library of every Linux user.

Related posts

• No related posts.

This guide is designed to be as user-friendly and easy to follow as possible, it should provide the first point of reference to any Ubuntu newcomer with lots of information. The manual has step by step instructions and includes lots of screenshots to show you how to do tasks. It also includes a Troubleshooting section to help you solve common Ubuntu problems quickly. Download this 160+ page Lucid Lynx manual today.

Related posts

• No related posts.

The Ubuntu team is happy to bring you the latest and greatest software the Open Source community has to offer. Our newest release, the Ubuntu 10.04 LTS, brings a host of exciting new features for users.

This Screenshots Gallery includes installation process,Desktop screeshots

1

◄ Back

Next ►

Picture 1 of 54

Related posts

• No related posts.

** Guide Updated **

This guide is an evolution from this original guide. Unless the Kerrighed Team comes up with a substantially different version, this is the only update to this guide I will ever make as the steps are pretty much the same for all svn versions I have tested.

On this version:
- Added changes for the latest Kerrighed svn 5586
- Fixed some steps to make them more readable and error free.
- Added simple MPI example to see how your program interacts with the cluster.
- Added troubleshooting section for some situations in which the nodes do not receive the image from the controller.

Thank you all for your previous comments and emails.

Rodrigo Sarpi

————
| internet |
————
|
router1
|
v
+————————————————–+
| eth1 — controller: 192.168.1.106 (given by router1)|
| eth0 — controller: 10.11.12.1 (manually set) |
+————————————————–+
|
router2
| |
| + –>eth0–node1: 10.11.12.101 (static IP Address)
|
v
eth0–node2: 10.11.12.102 (static IP Address)

——————————————————–
Debian Lenny with default kernel 2.6.26-2-686

All steps done as root on the controller

==
Step 1:

- dhcp server will provide ip addresses to the nodes.
- tftpd-hpa will deliver the image to the nodes
- portmap converts RPC (Remote Procedure Call) program numbers into port numbers.
NFS uses that to make RPC calls.
- syslinux is a boot loader for Linux which simplifies first-time installs
- nfs will be used to export directory structures to the nodes

When installing these packages accept the default settings presented for dhcp3 and TFTP.

#apt-get install dhcp3-server tftpd-hpa portmap syslinux nfs-kernel-server nfs-common

These packages are for MPI (see under TESTING below). You can install them on the controller to compile your MPI programs, then move them to any of the nodes and start the program from the node; or you can create, compile, and execute your MPI programs on any of the nodes. Either way, you need these packages on the node to execute your MPI code no matter option you choose:

#apt-get install openmpi-bin openmpi-common libopenmpi1 libopenmpi-dev

==
Step 2:

Identify ethernet interfaces which will be used by the dhcp server.
For this setup, we are setting up “eth0″ as the network card that’s
feeding the nodes of the internal network.

#nano /etc/default/dhcp3-server

INTERFACES=”eth0″

==

Step 3:

General configuration for the DHCP server.
Make a backup of original configuration file in case you want to use it as a reference later on.
cat /etc/dhcp3/dhcpd.conf > /etc/dhcp3/dhcpd.conf.bkp

#nano /etc/dhcp3/dhcpd.conf

# General options
option dhcp-max-message-size 2048;
use-host-decl-names on;
deny unknown-clients;
deny bootp;

# DNS settings
option domain-name “nibiru_system”; # any name will do
option domain-name-servers 10.11.12.1; # server’s IP address: dhcp and tftp

# network
subnet 10.11.12.0 netmask 255.255.255.0 {
option routers 10.11.12.1; # server IP as above.
option broadcast-address 10.11.12.255; # broadcast address
}

# ip addresses for nodes

group {
filename “pxelinux.0″; # PXE bootloader in /var/lib/tftpboot
option root-path “10.11.12.1:/nfsroot/kerrighed”; # bootable system

#the other laptop
host node1 {
fixed-address 10.11.12.101; # first node
hardware ethernet 00:0B:DB:1B:E3:89;
}

#desktop
host node2 {
fixed-address 10.11.12.102;
hardware ethernet 00:16:76:C1:F7:D4;

}

server-name “nibiru_headnode”; # Any name will do
next-server 10.11.12.1; # Server IP where the image is. For this network it’s the same machine
}

==
Step 4:

Configure the TFTP server.

#nano /etc/default/tftpd-hpa

RUN_DAEMON=”yes”
OPTIONS=”-l -s /var/lib/tftpboot”

==
Step 5:

Configure inetd for TFTP server.

nano /etc/inetd.conf

tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot

==
Step 6:

This directory will hold the image for the nodes to boot from.

#mkdir /var/lib/tftpboot/pxelinux.cfg

==
Step 7:

Copy PXE bootloader to the TFTP server.

#cp -p /usr/lib/syslinux/pxelinux.0 /var/lib/tftpboot/

==
Step 8:

Fallback configuration. If the TFTP client cannot find a PXE bootload configuration
for a specific node, it will use this one.

#nano /var/lib/tftpboot/pxelinux.cfg/default

LABEL linux
KERNEL vmlinuz-2.6.20-krg
APPEND console=tty1 root=/dev/nfs nfsroot=10.11.12.1:/nfsroot/kerrighed ip=dhcp rw session_id=1

==
Step 9:

This step is optional but recommended.
In /var/lib/tftpboot/pxelinux.cfg create separate files for *each* node.
The filename should be the IP address of the node represented in HEX format.
Example: 10 –> A; 11 –>B; 12 –>C; 101 –>65.
So for 10.11.12.101 it should be 0A0B0C65.

#nano /var/lib/tftpboot/pxelinux.cfg/0A0B0C65

LABEL linux
KERNEL vmlinuz-2.6.20-krg
APPEND console=tty1 root=/dev/nfs nfsroot=10.11.12.1:/nfsroot/kerrighed ip=10.11.12.101 rw session_id=1

==
Step 10:

Future node system. This directory will have the node’s bootable files, etc.

#mkdir /nfsroot/ && mkdir /nfsroot/kerrighed

==
Step 11:

Tell NFS what to export

#nano /etc/exports

/nfsroot/kerrighed 10.11.12.0/255.255.255.0(rw,no_subtree_check,async,no_root_squash)

==
Step 12:

Tell NFS to export above file system

#exportfs -avr

==
Step 13:

Create bootable system.
some developers reported that they needed the trailing “/” after “kerrighed”
as in: debootstrap –arch i386 lenny /nfsroot/kerrighed/ http://ftp.us.debian.org/debian

#apt-get install debootstrap

debootstrap –arch i386 lenny /nfsroot/kerrighed http://ftp.us.debian.org/debian

You should get this output:
I: Retrieving Release
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages…
I: Resolving dependencies of base packages…
I: Checking component main on http://ftp.us.debian.org/debian…
I: Retrieving libacl1
I: Validating libacl1
[..]
I: Configuring tasksel-data…
I: Configuring tasksel…
I: Base system installed successfully.

==
Step 14:

Isolate our node system to configure Kerrighed.

#chroot /nfsroot/kerrighed

==
Step 15:

Set root password for isolated system

#passwd

Enter new UNIX password: (nibirucluster)
Retype new UNIX password: (nibirucluster)
passwd: password updated successfully

==
Step 16:

Use the /proc directory of the node’s image as the bootable system’s /proc directory


mount -t proc none /proc


==
Step 17:

You might get Perl related errors when installing packages on to the node. To suppress those errors, type in the console:


nano .profile


export LC_ALL=C

or

just copy and paste into console:

export LC_ALL=C


==
Step 18:

Add basic packages needed by the node to communicate with the controller


nano /etc/apt/sources.list


deb http://ftp.us.debian.org/debian/ lenny main non-free contrib
deb-src http://ftp.us.debian.org/debian/ lenny main non-free contrib

deb http://security.debian.org/ lenny/updates main
deb-src http://security.debian.org/ lenny/updates main


apt-get update
apt-get install automake autoconf libtool pkg-config gawk rsync bzip2 libncurses5 libncurses5-dev wget lsb-release xmlto patchutils xutils-dev build-essential subversion dhcp3-common nfs-common nfsbooted openssh-server


You need these packages on the node to compile and execute your MPI code (see under TESTING below).


apt-get install openmpi-bin openmpi-common libopenmpi1 libopenmpi-dev


libopenmpi-dev may not be required if you only want to execute your code on the node. However, it is needed if you want to compile your program on the node itself.

==
Step 19:

Preparing mount points


mkdir /config


==
Step 20:

Set mount points


nano /etc/fstab


# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc /proc proc defaults 0 0
/dev/nfs / nfs defaults 0 0
configfs /config configfs defaults 0 0

==
Step 21

Set hosts to lookup


nano /etc/hosts


127.0.0.1 localhost

10.11.12.1 nibiru_headnode
10.11.12.101 node1
10.11.12.102 node2

==
Step 22:

Create a symlink to automount the bootable filesystem.


ln -sf /etc/network/if-up.d/mountnfs /etc/rcS.d/S34mountnfs


==
Step 23:

Configure network interfaces


nano /etc/network/interfaces


auto lo
iface lo inet loopback
iface eth0 inet manual

==
Step 24:

The username you will be using to connect to the node.


adduser (clusteruser)


Adding user `clusteruser’ …
Adding new group `clusteruser’ (1000) …
Adding new user `clusteruser’ (1000) with group `clusteruser’ …
Creating home directory `/home/clusteruser’ …
Copying files from `/etc/skel’ …
Enter new UNIX password: (nodepasswd)
Retype new UNIX password: (nodepasswd)
passwd: password updated successfully
Changing the user information for clusteruser
Enter the new value, or press ENTER for the default
Full Name []:
Room Number []:
Work Phone []:
Home Phone []:
Other []:
Is the information correct? [Y/n] y

==
Step 25

Get latest svn version 5586 as of this writing.


svn checkout svn://scm.gforge.inria.fr/svn/kerrighed/trunk /usr/src/kerrighed -r 5586


[..]
A /usr/src/kerrighed/NEWS
A /usr/src/kerrighed/linux_version.sh
U /usr/src/kerrighed
Checked out revision 5586.

==
Step 26:

Kerrighed uses linux 2.6.0. Kerrighed ignores any other version.


wget -O /usr/src/linux-2.6.20.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.tar.bz2 && tar jxf /usr/src/linux-2.6.20.tar.bz2 && cd /usr/src/kerrighed && ./autogen.sh && ./configure && cd kernel && make defconfig


==
Step 27:

Make sure these settings are in place. By default, b), c), d) are
enabled but it wouldn’t hurt if you double-check. a) you have to pick
the network cards of your nodes and make sure they are loadable at boot
time (* not M)

a. Device Drivers -> Network device support –> Ethernet (10 or 100Mbit)

b. File systems -> Network File Systems and enabling NFS file system support,
NFS server support, and Root file system on NFS. Make sure that the NFSv3 options
are also enabled, and again, make sure they are part of the kernel and not loadable
modules (asterisks and not Ms).

c. To enable the scheduler framework, select “Cluster support” –> “Kerrighed
support for global scheduling” –> “Run-time configurable scheduler framework”
(CONFIG_KRG_SCHED_CONFIG). You should also enable the “Compile components needed
to emulate the old hard-coded scheduler” option to mimic the legacy scheduler
(CONFIG_KRG_SCHED_COMPAT). This last option will compile scheduler components
(kernel modules) together with the main Kerrighed module, that can be used to
rebuild the legacy scheduler, as shown below.

d. To let the scheduler framework automatically load components’ modules,
select “Loadable module support” –> “Automatic kernel module loading”
(CONFIG_KMOD). Otherwise, components’ modules must be manually loaded
on each node before components that they provide can be configured.
*/


make menuconfig


==
Step 28:

Kernel compilation with Kerrighed support


cd .. && make kernel && make && make kernel-install && make install && ldconfig


==
Step 29:

Configuring Kerrighed


nano /etc/kerrighed_nodes


session=1 #Value can be 1 – 254
nbmin=2 #2 nodes starting up with the Kerrighed kernel.
10.11.12.101:1:eth0
10.11.12.102:2:eth0


nano /etc/default/kerrighed


# Start kerrighed cluster
ENABLE=true
#ENABLE=false

# Enable/Disable legacy scheduler behaviour
LEGACY_SCHED=true
#LEGACY_SCHED=false

==
Step 30:

Exit chrooted system


exit


==
Step 31:

Out of your chrooted system copy bootable kernel.


cp -p /nfsroot/kerrighed/boot/vmlinuz-2.6.20-krg /var/lib/tftpboot/


==
Step 32:

Configure the controller to use eth0 card.
eth0 will be used by the DHCP server to feed the nodes.


ifconfig eth0 10.11.12.1
/etc/init.d/tftpd-hpa start
/etc/init.d/dhcp3-server start
/etc/init.d/portmap start
/etc/init.d/nfs-kernel-server start


==
Step 33:

Make sure nodes are connected to the router.
From the controller do:


ssh clusteruser@10.11.12.101

Then from any connected node as “clusteruser”:


krgadm nodes


output:
101:online
102:online

Double-check as root from the node:


tail -f /var/log/messages


node1 kernel: Proc initialisation: done
node1 kernel: EPM initialisation: start
node1 kernel: EPM initialisation: done
node1 kernel: Init Kerrighed distributed services: done
node1 kernel: scheduler initialization succeeded!
node1 kernel: Kerrighed… loaded!

These commands are helpful. Do these as a regular node user “clusteruser”.


krgcapset -d +CAN_MIGRATE
krgcapset -k $$ -d +CAN_MIGRATE
krgcapset -d +USE_REMOTE_MEMORY
krgcapset -k $$ --inheritable-effective +CAN_MIGRATE


To monitor your cluster:

top

(toggle 1 to see cpus)

Also:

cat /proc/cpuinfo | grep “model name”
cat /proc/meminfo | grep “MemFree”
cat /proc/stat


==
Step 34:

This is step is needed so you do not have to enter a password when triggering your MPI programs from the node.
If you do not generate a key, you will have to enter the node[n] password manually in order to migrate the processes.

You may not need to enter a password when generating the key. The assumption is that the controller is secure enough from the outside (no rerouting packets from eth1 –the other network card.)

Alternatively, if you feel paranoid you may enter a password then tell ssh-agent to remember it. The password will remembered for that session only.

After you log on to one of the nodes via ssh

ssh-keygen -t dsa (don't enter password)
cp /home/clusteruser/.ssh/id_dsa.pub /home/clusteruser/.ssh/authorized_keys


or


ssh-keygen -t dsa (do enter password)
cp /home/clusteruser/.ssh/id_dsa.pub /home/clusteruser/.ssh/authorized_keys
eval `ssh-agent`
ssh-add /home/clusteruser/.ssh/id_dsa (type in password associated with keys)


==
Step 35 TESTING:

A simple ‘hello world’ programs that calls the MPI library.

I will create a config file where MPI can lookup information for running jobs on the cluster.
I am creating this config file on the home directory of the cluster user “clusteruser” –which is the same account we created earlier. It will be readable to the node so you can create the file as your own user from the controller. You can also log on to the any of the nodes where you will be triggering your programs from and create the file there using the “clusteruser” account:

In this situation, I opted for Door A
at controller as a regular user –your regular system username:


nano /nfsroot/kerrighed/home/clusteruser/mpi_file.conf


#Contents of mpi_file.conf. I’m listing the nodes of the cluster.
node1
node2

——–START CODE———
/*
hello world
This “hello world” program does not deviate much from any other hello world program you have seen before. The only difference is that it has MPI calls.
*/

#include
#include
#include

int main(int argc, char *argv[])
{
char *boxname;
int rank, processes;

MPI_Init(&argc, &argv);

MPI_Comm_rank(MPI_COMM_WORLD, &rank);
MPI_Comm_size(MPI_COMM_WORLD, &processes);

boxname = (char *)calloc(100,sizeof(char));
gethostname(boxname,100);

printf(“\n\nProcess: %i\nMessage: hello cruel world!\nCluster Node: %s \n\n”, rank, boxname, processes);

MPI_Finalize();

return(0);
}

——–END CODE———

On the controller compile your program using the MPI library:


mpicc hello_world.c -o hello_world


Put the MPI program in the user’s home directory on one of the nodes.
In this example, I put it in /nfsroot/kerrighed/home/clusteruser:


cp hello_world /nfsroot/kerrighed/home/clusteruser/


open another shell and ssh any of the nodes. Here I log on to node1:


ssh clusteruser@10.11.12.101


mpirun -np 2 --hostfile mpi_file.conf hello_world


output:
Process: 1
Message: hello cruel world!
Cluster Node: node2

Process: 0
Message: hello cruel world!
Cluster Node: node1

============
Troubleshooting:
============
“PXE-E32: TFTP open timeout” error. It can be either that your network card is not supported or that you have something blocking the way for the TFTP server to distribute the image.

Try booting your node from CD:


cd /tmp
wget http://kernel.org/pub/software/utils/boot/gpxe/gpxe-1.0.0.tar.bz2
bunzip2 gpxe-1.0.0.tar.bz2
tar xvpf gpxe-1.0.0.tar
cd /tmp/gpxe-1.0.0/src/bin/gpxe.iso
make bin/gpxe.iso


Then burn gpxe.iso to a CD and boot the client off of it.

If still no joy try below. It might that something is blocking the way to the TFTP server.

On the controller:

in.tftpd -l
tail -1 /var/log/syslog


recvfrom: Socket operation on non-socket
cannot bind to local socket: Address already in use
solution: you can use the package rcconf to disable dhcp, portmap, nfs server, and tftp-hpa at boot time. Then start manually each server when needed.

If problem persists try disabling firewall settings
(make a backup of existing rules iptables-save > /root/firewall.rules)

iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT


[ to restore after you find out what the problem is use iptables-restore < /root/firewall.rules]

You can also try this:


netstat -anp | grep 69

udp6 0 0 :::69 :::*

note: this output looks suspicious “udp6″?

Connect with any TFTP client from the controller and on a second shell do tail -f /var/log/syslog

tftp 127.0.0.1

tftp> get pxelinux.0
Transfer timed out


tail -f /var/log/syslog

in.tftpd[2881]: received address was not AF_INET, please check your inetd config
inetd[2441]: /usr/sbin/in.tftpd: exit status 0x4c00

note: Check inet.conf file and disable IPv6

To disable IPv6 add these lines to /etc/modprobe.d/aliases

alias net-pf-10 off
alias ipv6 off


Also in /etc/hosts put a comment on these lines:

#::1 localhost ip6-localhost ip6-loopback
#fe00::0 ip6-localnet
#ff00::0 ip6-mcastprefix
#ff02::1 ip6-allnodes
#ff02::2 ip6-allrouters
#ff02::3 ip6-allhosts


Reboot and try again from head node.


tftp 127.0.0.1

tftp> get pxelinux.0
Received 15987 bytes in 0.0 seconds

All ok now, try booting your nodes.

Related posts

• How to Set Up a High Performance Cluster (HPC) Using Debian Lenny and Kerrighed (8)

The Ubuntu developers are moving quickly to bring you the latest and greatest software the Open Source community has to offer. This is the first Ubuntu 10.04 beta release, which brings a host of exciting new features.

Note:- This is beta release. Do not install it on production machines. The final stable version will be released on April 29, 2010.

This Screenshots Gallery includes installation process and what is new in ubuntu 10.04

1

◄ Back

Next ►

Picture 1 of 37

Related posts

• No related posts.

This article describes the prerequisites and steps needed to replicate dynamic routing protocol routes (OSPF, BGP, RIP) to your passive firewall in an NSRP cluster

Procedure to follow

Starting in ScreenOS 6.0.0r1, you can use the command from ssh terminal of your firewall

set nsrp rto-mirror route

Which will replicate all dynamic routes from the active primary member to the backup NSRP member.  Without this command, if a fail over occurs, it may take several seconds for the dynamic adjacencies to re-establish, and sessions can be interrupted or dropped as a result.

Related posts

• No related posts.

The Ubuntu developers are moving quickly to bring you the absolute latest and greatest software the Open Source community has to offer. The Lucid Lynx Alpha 3 is the third alpha release of Ubuntu 10.04, bringing with it the earliest new features for the next version of Ubuntu.

Note:- This is an alpha release. Do not install it on production machines. The final stable version will be released on April 29, 2010.

Ubuntu 10.04 Login screen

◄ Back

Next ►

Picture 1 of 29

Related posts

• Ubuntu 10.04 (Lucid) Alpha 3 Screenshots Gallery (9)

The Ubuntu developers are moving quickly to bring you the absolute latest and greatest software the Open Source community  has to offer. The Lucid Lynx Alpha 3 is the third alpha release of Ubuntu 10.04, bringing with it the earliest new features for the next version of Ubuntu.

Note:- This is an alpha release. Do not install it on production machines. The final stable version will be released on April 29, 2010.

This Screenshots Gallery includes installation process and what is new in ubuntu 10.04

Ubuntu 10.04 CD starts Booting

◄ Back

Next ►

Picture 1 of 45

Related posts

• Ubuntu 10.04 (Lucid) Alpha 3 Screenshots Gallery (Updated with new wallpaper,theme) (26)

In order to reset the enable password on the ProxySG, you will need to have physical access to the ProxySG itself.  You will need a nine (9) pin null modem cable to connect to the serial console on the ProxySG.  Make sure the cable is connected to the ProxySG and to your laptop or desktop.  Make sure your serial connection has the following settings:

• Bits per second (bps): 9600
• Data bit: 8
• Parity: None
• Stop bits: 1
• Flow control: None
• Emulation: VT100

You can use Hyperterminal, PuTTY, or any other third-party terminal emulation software that can connect via the serial port.

Once connected via the serial port, press the “Enter” key three times to activate the serial console.  A menu similar to the following will appear:

Welcome to the SG Appliance Serial Console

Version: SGOS 5.4.2.2, Release id: 41580

------------------------- MENU -----------------------------

1) Command Line Interface
2) Setup Console

------------------------------------------------------------

Enter option:

Please select option 2) Setup Console and follow the steps to setup the console.  There will be an option to setup the enable password.  That is where you will enter the new password to replace the unknown or forgotten password.

Related posts

• No related posts.

What is DNX?

It is a modest script created to install a few free and non-free libraries and packages for Debian GNU/Linux based on the ubuntu-restricted-extras Ubuntu’s package.

Why?

The main goal of this script is to have a one-step method to configure a Debian Workstation to decode mp3, avi, mpeg and work with flash, java and rar files.

Details

DNX will add the contrib, non-free and Debian Multimedia repositories to your APT configuration file and install all the required packages.

To get a complete list of the packages that will be installed check here

Install DNX in Debian

First you need to download the DNX script from here http://mey-online.com.ar/dnx/dnx-lenny-0.1.sh

or

Using the following command

# wget http://www.mey-online.com.ar/dnx/dnx-lenny-0.1.sh

Change de permissions to made it executable:

# chmode +x dnx-lenny-0.1.sh

And run:

# ./dnx-lenny-0.1.sh

If you already have configured the Debian Multimedia repository select the option 2, otherwise select the full instalation.

Related posts

• No related posts.

If you are looking for debian sourcelist generator try this

http://debgen.simplylinux.ch/

Screenshot

Related posts

• No related posts.

This tutorial will help you to install ATI drivers on Debian 5(lenny)

First you need to download ATI drivers from here and run the downloaded script as root

#sh ati-driver-installer-9-10-x86.x86_64.run

Follow the on screen instructions

Troubleshooting

If you got an error during the installation try the following:

#apt-get install build-essential module-assistant fglrx-driver fglrx-kernel-src

#m-a update

#m-a prepare

#m-a a-i fglrx

and then try to install the package again “sh ati-driver-installer-9-10-x86.x86_64.run”

It should be ok after this.

Related posts

• No related posts.

Wicd is an open source wired and wireless network manager for Linux which aims to provide a simple interface to connect to networks with a wide variety of settings.
Wicd’s features include

1. No Gnome dependencies (although it does require GTK), so it is easy to use in XFCE, Fluxbox, Openbox, Enlightenment, etc.
2. Ability to connect to wired (Ethernet only, no PPPoE/DSL support yet) and wireless networks
3. Profiles for each wireless network and wired network
4. Many encryption schemes, some of which include WEP/WPA/WPA2 (and you can add your own)
5. Remains compatible with wireless-tools
6. Tray icon showing network activity and signal strength
7. A full-featured console interface

Install wicd in Debian Lenny

First you need to edit /etc/apt/sources.list file.Open the terminal and run the following commands

#vi /etc/apt/sources.list

Add the following line

deb http://www.backports.org/debian lenny-backports main contrib non-free

Save and exit the file

Update the source list

#apt-get update

Install wicd using the following command

#apt-get -t lenny-backports install wicd

Troubleshooting Tip

If Wicd fails to connect after you install it, make sure that the only entry in your /etc/network/interfaces file is

auto lo
iface lo inet loopback

You can change the contents of this file by pressing alt + f2, then typing

gksudo gedit /etc/network/interfaces

if you are using Gnome, or replace gedit with kate if you are using KDE. This will allow you to view and edit the /etc/network/interfaces.You can ignore lines that start with.

Starting Wicd

If you are using a desktop environment without a notification area, you can run the Wicd GUI by running

wicd-client -n

If you are using a desktop environment with a notification area, you can start the tray icon by running

wicd-client

If you are using a desktop environment such as GNOME or KDE, you can start the Wicd GUI by opening the Application menu.

This is really good compare to default network manager

Related posts

• No related posts.

This tutorial will explain Configuring an SSG model firewall into Transparent Mode.This will make the firewall a Layer 2 device.
Procedure to follow

1) First you need to connect to your SSG firewall using console cable

2) Now run “get interface” (without quotes) command

SSG550M-> get interface

You should see similar to the following output

A – Active, I – Inactive, U – Up, D – Down, R – Ready
Interfaces in vsys Root:
Name           IP Address         Zone        MAC            VLAN State VSD
eth0/0         192.168.1.1/24     Trust       0012.1eac.7380    -   U   -
eth0/1         0.0.0.0/0          DMZ         0012.1eac.7385    -   D   -
eth0/2         0.0.0.0/0          Untrust     0012.1eac.7386    -   D   -
eth0/3         0.0.0.0/0          Null        0012.1eac.7387    -   D   -

In the above output any interface that has an IP defined or a Zone defined will have to be removed.

For example:

unset interface e0/0 ip   ——(This will remove the IP address from e0/0)

unset interface e0/0 zone    ——-(This will place e0/0 interface in the Null zone)

Repeat the above steps until all interfaces are 0.0.0.0 and in the Null Zone.  Issue get interface to verify.

Now configure the VLAN1 IP address

set interface vlan1 ip 10.1.1.1/24   —— (This provides a Layer 3 IP address on a device in Layer 2)

Now configure a zone. For example:

set interface e0/0 zone v1-trust

You should see a message reporting “Changed to pure l2 mode”.

Save the changes you made.

Type save, press Enter.

Reset the Juniper Firewall.

Type reset, press Enter.

After the SSG reboots, you should now be able to manage the Juniper Firewall from the WebUI to configure the remaining zones, policies, default route, etc…

Related posts

• No related posts.

Some times you may not be able to delete the static routes in cisco catalyst switches so this tutorial will explain how to fix this problem

When you run the following comamnd will show you the existing routing table

switch# show ip route

The static routes cannot be deleted no ip route … command

switch(config)# no ip route ….

or

switch# clear ip route *

or

switch# clear ip cache *

Solution

You need to disable and enable the “ip routing” service.

Disable IP Routing

switch(config)#no ip routing

Enable IP Routing

switch(config)#ip routing

Related posts

• No related posts.