Link Aggregation + Bonding (Yük Dengeleme) Debian,Ubuntu

apt-get install ifenslave-2.6

modprobe bonding

Debian Link Aggregation (Network Bonding)
Here we are going setup link aggregation for Debian. Your system must have at least 2 network interfaces (but not limited to).
Bonding

Install ifenslave-2.6 package:

apt-get install ifenslave-2.6

Load bonding kernel module:

modprobe bonding

Note that you shouldn't have any configuration for eth0 and eth1, they are attached as slaves for bond0 interface. Network configuration (file /etc/network/interfaces):

auto bond0
iface bond0 inet static
address 192.168.10.14
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
gateway 192.168.10.1

slaves eth0 eth1

# Transmit packets in sequential order
# from the first available slave through
# the last. This mode provides load
# balancing and fault tolerance.
bond-mode balance-rr

# Only one slave in the bond is active.
# A different slave becomes active if,
# and only if, the active slave fails.
#This mode provides fault tolerance.
#bond-mode active-backup

bond-miimon 100
bond-downdelay 200
bond-updelay 200

Once above is complete you need to reboot your server so the network changes take place (that should be faster than bringing up/down network interfaces and restarting networking service).

Bridge
You can use link aggregation with network bridge, for example if you are using lxc / kvm virtualization. Here is network configuration (file /etc/network/interfaces):

auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond-mode balance-rr
bond-miimon 100
bond-downdelay 200
bond-updelay 200

auto br0
iface br0 inet static
address 192.168.10.14
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
gateway 192.168.10.1
bridge_ports bond0
bridge_fd 0
bridge_maxwait 0
bridge_stp off

Network Switch
If your switch supports port trunking you should add the switch ports used by eth0 and eth1 to a single trunk

link : http://mindref.blogspot.com/2011/05/debian-link-aggregation-bonding.html

ubuntu ve debian için postfix-mysql-dovecot-sieve-spamassasin için spamların spam foldera gönderilmesi

ubuntu ve debian için postfix-mysql-dovecot-sieve-spamassasin için spamların spam foldera gönderilmesi


işlemler :

1.

apt-get install pysieved sieve-connect


2.

edit /etc/dovecot/dovecot.conf

protocol lda { } bölümüe mail_plugins = sieve ekle veya başka modül varsa bir boşluk bırakarak sieve gir.

protocols bölümüne lda ekle

3.

plugin { } bölümüne aşağıdaki satırı gir.

sieve_global_dir = /var/lib/dovecot/sieve/global/

4. create /var/vmail/globalsieverc

edit :

require ["fileinto"];
# Move spam to spam folder
if header :contains "X-Spam-Flag" ["YES"] {
fileinto "spam";
stop;
}

5. chown vmail /var/vmail/globalsieverc

6. /etc/init.d/dovecot restart


Linkler :


http://wiki.dovecot.org/LDA/Sieve/Dovecot
http://workaround.org/ispmail/lenny/server-side-sieve-filtering
http://yvz.ath.cx/programs/postfix/postfix-postfixadmin-dovecot-mysql/
http://www.postfix.org/docs.html

Postfix Mesaj Limitini yükseltme

Postfix ön tanımlı olarak kurulduğunda mesaj limiti 10Mbdir.
Mesaj limitini 25 Mb yükseltmek için aşağıdaki işlemleri yapabilirsiniz.


postconf -e message_size_limit=25000000

/etc/init.d/postfix reload

işlem tamam

Postfix Ayarlarını görüntüleme

postconf -d

Postfix message limitlerini görüntüleme

postconf -d |grep size

isc dhcp server ile clientlara static route tanımlama

ISC DHCP v3 Sunucusu kullanıyorsanız ağınızda clientlara static route pramatereleri gönderebilirsiniz.

Aşağıdaki ms ve linux clientlar için oluşturulmuş static-route örneği bulunmaktadır.


Örnek : 10.45.1.0/24 networkunu 192.168.109.10 nolu ip adresine yönlendirelim.


/etc/dhcp/dhcpd.conf dosyasına aşağıdaki satırları ekleyiniz.

option ms-classless-static-routes code 249 = array of unsigned integer 8;
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
option ms-classless-static-routes 24, 10,45,1, 192,168,109,10;
option rfc3442-classless-static-routes 24, 10,45,1, 192,168,109,10;

sonra dhcp-v3 sunucusunu tekrar başlatınız.

/etc/init.d/dhcp-server restart

clieant tarafında ip isteğini tazeleyiniz.

işlem tamam.

Ubuntu 10.10 (64bit) VMware 2.0.2 (64bit) kurulumu

http://sistemipucu.blogspot.com/2010/11/vmware-20-for-ubuntu-104-and-1010.html adresindeki yönergeleri uygulayın.

Kurulumdan sonra vmware-config.pl dosyasını çalıştırmadan önce :

vmware-config.pl (64bit)

linkindeki vmware-config.pl dosasını indirip /usr/bin dizinindeki ile değişitirin.


ln -s /usr/src/linux-headers-`uname -r`/include/generated/autoconf.h /usr/src/linux-headers-`uname -r`/include/linux/autoconf.h

komutundan sonra vmware-config.pl çalıştırın vmware'yi düzenleyin.


Kaynak : http://risesecurity.org/2010/04/02/vmware-server-2-0-2-update-patch-2/

vmware 2.0 for Ubuntu 10.4 and 10.10

Download the VMware Server (VMware-server-2.0.2-203138.i386.tar.gz).

Download the VMware Server 2 update patch #2:

$ wget -N http://risesecurity.org/~rcvalle/VMware-server-2.0.2-203138-update-2.patch

Extract VMware Server:

$ tar -xzf VMware-server-2.0.2-203138.i386.tar.gz

Extract VMware Server modules:

Change working directory to vmware-server-distrib/lib/modules/source/
$ tar -xf vmci.tar
$ tar -xf vmmon.tar
$ tar -xf vmnet.tar
$ tar -xf vsock.tar

Apply the patch:

Change working directory to vmware-server-distrib/
patch -p1 < ../VMware-server-2.0.2-203138-update-2.patch

Archive VMware Server modules again:

Change working directory to vmware-server-distrib/lib/modules/source/
$ rm -f vmci.tar
$ rm -f vmmon.tar
$ rm -f vmnet.tar
$ rm -f vsock.tar
$ tar -cf vmci.tar vmci-only/
$ tar -cf vmmon.tar vmmon-only/
$ tar -cf vmnet.tar vmnet-only/
$ tar -cf vsock.tar vsock-only/

Run installer script as root:

Change working directory to vmware-server-distrib/
$ sudo ./vmware-install.pl

Note for Ubuntu users:

When asked for the current administrative user for VMware Server, specify your user as a different administrator.

Note about VMware Remote Console Plug-in:

The VMware Remote Console Plug-in does not work properly on Ubuntu 9.10, Fedora 12 and other newer distributions. A workaround for this is to set the environment variable VMWARE_USE_SHIPPED_GTK before running the VMware Remote Console Plug-in. To set this environment variable at login time, add the following line to your ~/.profile:

export VMWARE_USE_SHIPPED_GTK=yes


Alıntı :

http://risesecurity.org/2010/04/02/vmware-server-2-0-2-update-patch-2/