Plesk – Scripting




Delete DNS


Disable mail for all domains


Add Dns sec in OVH


Pulls email password out of Plesk database for given email address


Recovery all mail accounts


Add SPF records to all domains


WordPress – Url Rewriting


Choosing your permalink structure

In the Settings → Permalinks panel (Options → Permalinks before WordPress 2.5), you can choose one of the “common” structures or enter your own in the “Custom structure” field using the structure tags.


Create .htaccess file



Installation on CF Card

Software installation As everybody knows, the installation process of Vyatta Core is simple and well-documented. However we need to install Vyatta Core on Compact Flash media that will be later used on ALIX.3D2 board. So what’s a problem? Xo-Xo, you can not just install Vyatta directly on ALIX.3D2-based system, it has no VGA, and it can not boot from external media, like USB-CDROM. We need to use another PC system for initial Vyatta installation! I advice you to use VMware Workstation or VMware Player, create a virtual machine with CD-ROM, USB Controller, without hard drive and WITHOUT any network interface. Remember, if there will be any network interface on a virtual machine, your initial config.boot will be messed up a little bit!

Grab latest VC6.0 – Live CD ISO from Use it as VMware CDROM, power on Virtual Machine, connect CF card to your PC using card reader,

connect CF card as removable device in VMWare,

log in to Vyatta Live CD and just run

Your CF installed in card reader will appear as /dev/sda or /dev/sdb or something and it should be autodetected by Vyatta installation script as default destination device for installation. Yes, it’s really that simple.Smile I advise you to NOT use your real (physical) PC for this CF installation trick, cause you may accidentally install Vyatta on your real HDD and destroy your host system. You have been warned!


Avant l’installation,

Passer en root

Editer le fichier

Changer ext3 en ext2 pour enlever la journalisation Installer vyatta

Avant de redemarrer Mount la CF

Editer le fichier

Mettre la CF dans le router

Disable syslog

Voir le fichier /etc/syslog.conf

  • .notice



Squid en High Anonymous

Doc Squid


Reload Squid




Open Gtalk and MSN


Tips & Tricks

No cache for domain


Linux – NFS Client/Server






If you make changes to /etc/exports on a running NFS server, you can make these changes effective by issuing the command



This will install all the required packages for nfs client

Mounting manually

Example to mount to /files. In this example is the name of the server containing the nfs share, and files is the name of the share on the nfs server

The mount point /files must first exist on the client machine.

Create files directory using the following command

You need to mount the share using the following command

Now you may need to restart services using the following command

Mount in fstab


Linux – trick


Bash color

  • \e[ – Start color scheme
  • \e[m – Stop color scheme
  • \u – Username. The original prompt also has \h, which prints the host name.
  • x;y – Color pair to use (x;y)
  • $PS1 – is your shell prompt
  • \w – Current absolute path. Use \W for current relative path
  • \t -the current time in 24-hour HH:MM:SS format


Bash shell shortcuts

CTRL – Key bound

Key Description
CRTL + a Start line
CTRL + e End line
CTRL + u Delete backward from cursor
CTRL + d Delete character under the cursor
CTRL + h Delete character before the cursor
CTRL + y Paste

ALT – Key bound

Key Description
ALT + c Capitalize word
ALT + l Lowercase
ALT + e Delete word

Iptables – Rewrite ip for output

Une des solution consiste à réécrire tous les paquets sortant en leur réattribuant votre adresse IP failover. Pour ceci, nous allons utiliser le flux SNAT de Iptables (Source NAT).

Commençons par écire une règle de réécriture des paquet (nous supposons que l’interface réseau est eth0, que votre IP physique est et que votre IP failover est

Kill TCP connexion

  • Kill on connexion on port 21


  • Kill all connexion (in/out) on host


Cisco feature set upgrade


Error: The image in the archive which would be used to upgrade Error: system number 1 does not support the same feature set.

Cisco it seems included this sanity check,as of 12.2(35), to prevent you from accidentally changing the feature set during a IOS upgrade, not a nice thing to happen on a production switch, when things go belly up.

You will get the above error when upgrading the IOS and changing the feature set. IE if you upgrade the image from IPBASE 12.2(35)SE5 to ADVIPSERVICESK9 12.2(25)SEE4.

So to bypass this, you can add the /allow-feature-upgrade parameter, to the archive download-sw command.

Example :

If you need more info on how to upgrade the IOS on a Cisco 3560, visit

How to fix your Windows MBR with an Ubuntu liveCD


You need to install ms-sys for ubunut

Edit the source list and add

Update and install

Cisco – Spanning Tree


Identifying a Bridging Loop

Suspect a loop if you see the following:

  • You capture traffic on a link and see the same frames multiple times.
  • All users in a bridging domain have connectivity problems at the same time.
  • There is abnormally high port utilization.

To remedy a loop quickly, shut redundant ports and then enable them one at a time. Some switches enable debugging of STP to help in diagnosing problems. The following commands are useful for isolating a bridging loop


Spanning-Tree Best Practices

To optimize data flow in the network, design and configure Spanning Tree in the following ways:

  • Statically configure switches to be the primary and secondary root bridges by setting priority values.
  • Consider which interfaces will become designated and root ports (possibly set port priorities/path cost).
  • Tune STP using the tools detailed in this section.
  • Enable UDLD aggressive mode on all fiber interfaces.
  • Design STP domains that are as simple and contained as possible by using multilayer switches and routed links.
  • Use PVRST+ or MST for the fastest convergence times.



Master account

Il est parfois utile de pouvoir se connecter sur une des boites mails hébergées sans connaître son mot de passe pour diverses raisons:

  • via un script pour analyser d’éventuels mails identifiés comme spam/ham par l’utilisateur;
  • via un script pour archiver des emails anciens;
  • directement afin de reproduire un bug signalé par l’utilisateur.

Il est évident que cette technique ne peut être utilisée simplement pour consulter les emails des utilisateurs à leur insu; c’est une atteinte à la vie privée qui peut être poursuivie par les tribunaux. Vous êtes donc prévenu, et comme pour tous les articles de ce blog, vous mettez ce qui suit en oeuvre sous votre entière responsabilité et en assumez pleinement les éventuelles conséquences.

Cette mise en garde étant faite, le concept est donc de définir un couple login/mot de passe ayant accès à toutes les boites mails hébergées sur votre serveur. Cet utilisateur master n’a rien à voir avec les utilisateurs mail déjà existants.

Dans le fichier /etc/dovecot/dovecot.conf, rajoutez la directive auth_master_user_separator=*. Puis, recherchez la section auth default et complétez-la pour qu’elle ressemble à ce qui suit:

Le fichier /etc/dovecot/passwd.masterusers est de type htaccess. Voici les commandes pour le générer:

Vous donnez alors le mot de passe de l’utilisateur admin. Vous pouvez répeter la dernière ligne autant de fois que désiré avec d’autres noms d’utilisateurs. Les utilisateurs master pourront alors se connecter au moyen de*admin et du mot de passe associé au compte admin.

Page 4 of 512345
Go to Top