no start stop script needed 😀

##Debian / Ubuntu
##INSTALL

sudo apt-get update && sudo apt-get install gcc make -y

wget https://github.com/z3APA3A/3proxy/archive/0.8.12.tar.gz

tar zxvf 0.8.12.tar.gz

cd 3proxy-0.8.12

make -f Makefile.Linux

sudo cp src/3proxy /usr/local/bin/

##CONFIG
##NO LOGS - NO SOCKS - NO IP SELECTION
##IPv6 + IPv4 ENABLED

nano 3proxy.config

-------------------------------------------
nserver 1.1.1.1

nserver 9.9.9.9

nscache 65536

timeouts 1 5 30 60 180 1800 15 60

users username1:CL:password1

daemon

log /dev/null

authcache user 60

auth strong cache

allow * * * *

proxy -64 -n -a -p8182
-------------------------------------------

##START

3proxy 3proxy.config

 

DONE!

Instalation of IBM DB2 module should be very easy (refering to the installation instructions):

  1. First of all, we need to download the driver package from here
  2. unpack the package to the server at /opt/ibm_db2/dsdriver
  3. chmod 755 installDSDriver
  4. ./installDSDriver
  5. Install pecl and php-pear (may need ksh): yum install php-pear
  6. pecl install ibm_db2
  7. When asked, provide the path to the db2 driver (here /opt/ibm_db2/dsdriver)
  8. You may check if it is installed by: pecl list
  9. Last thing: chmod o+w /opt/ibm_db2/dsdriver/cfg
  10. Edit /etc/php.ini and add extension=ibm_db2.so
  11. service httpd restart

Then in PHP:

<?php
    $databaseName = "your_db_name";
    $hostName = "your_host_name";
    $port = 50001;
    $userName = "your_user_name";
    $password = "your_password";
    $conn_string = "DRIVER={IBM DB2 ODBC DRIVER};DATABASE=$databaseName;HOSTNAME=$hostName;PORT=$port;PROTOCOL=TCPIP;UID=$userName;PWD=$password;Security=ssl;";
    $conn = db2_connect($conn_string, '', '');

    if($conn) {
        echo "Connected!";
        db2_close($conn);
    } else {
        echo "Not connected<br>";
        echo db2_conn_errormsg();
    }
?>

Whole process with lot of pre-requisites for python is here (it works with little modifications for PHP too).

Hello,

you can fix that problem with an arping:

[root@hedodhedo ~] # arping -s 37.247.112.71 37.247.112.1
ARPING 37.247.112.1 from 37.247.112.71 eth0
Unicast reply from 37.247.112.1 [00:0B:45:80:C0:00] 1.846ms
Unicast reply from 37.247.112.1 [00:0B:45:80:C0:00] 1.483ms
^CSent 2 probes (1 broadcast(s))
Received 2 response(s)
[root@hedodhedo ~]# logout
Connection to 37.247.112.70 closed.

# ping 37.247.112.71
PING 37.247.112.71 (37.247.112.71) 56(84) bytes of data.
64 bytes from 37.247.112.71: icmp_seq=1 ttl=63 time=0.377 ms
64 bytes from 37.247.112.71: icmp_seq=2 ttl=63 time=0.205 ms

— 37.247.112.71 ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.205/0.291/0.377/0.086 ms

Kind Regards,

I have a WordPress website on my server. But when I upload its database to live server, I get error

#1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’

Solution:

sed -i 's/utf8mb4_unicode_520_ci/utf8mb4_unicode_ci/g' file.sql

Copy/Paste Information

mysql -u username -ppassword databasename < databasename.sql

 

files:

user.bayi1.kullaniciadi.tar.gz

user.bayi1.baskabirkullanici.tar.gz

must be renamed to:

user.bayi2.kullaniciadi.tar.gz

user.bayi2.baskabirkullanici.tar.gz

command:

for f in user.bayi1.*.tar.gz; do mv -v "$f" "${f/user.bayi1/user.bayi2}"; done;

Mikrotik router kullanarak kendi 6to4 tunel yapilandirmam ile datacenterdaki native ipv6 networkum uzerinden evde ipv6 kullanma deneyimim.

bu yazi basligi cok uzun oldu biliyorum.

Ancak bu konu ile ilgili bir suredir dusunmekte idim.

Kendi evimde kablonet uzerinden sabit ip adresimle he.net tunnel broker servisini kullarak uzun zamandir ipv6 kullanabilmekteydim.

Mikrotik ile bu isin nasil yapilacagi konusunda zaten 1 milyon tane dokumantasyon howto vb var.

 

Ancak benim yapmak istedigim verimerkezinde bulunan mikrotik routerimda hali hazirda bulunan native ipv6 baglantisi ve o lokasyonda anons ettigim /32 ipv6 icinden kendi evimde ipv6 kullanmak idi.

bu konu icin okudum arastirdim , uykusuz gecelerde kafa patlattim. Bosunaymis

aslinda yapilmasi gerekenler cok basitmis.

ben konuyu bos yere karmasik hale getiriyormusum.

NASIL YAPILIR konusuna gelince

adim adim yazayim belki yapmak isteyen bir baskasi olursa faydasi olsun.

 

1- DURUMUM NEDIR? 

Verimerkezinde bir mikrotik routerim var.

Bu router ile direk native olarak ipv6 internete cikabiliyorum.

Bu router uzerinde anons ettigim /32 ipv6 adres blogum var.

 

Evde kablonet kullaniyorum,

Kablomodemim bridge modda calisiyor,

Tum nat, dhcp ve benzeri isleri kablonet modem arkasindaki mikrotik routerim hallediyor.

Kablonet firmasindan sabit ipv4 ip adresim var.

Ve bunu kullanarak internete cikiyorum mikrotik routerim uzerinden.

 

2- YAPMAK ISTEDIGIM NEDIR?

Verimerkezindeki /32 ipv6 blogumdan bir /48 ipv6 blogunu evimde kullanmak istiyorum.

Bu sayede evimde ipv6 baglantim olmus olacak.

Direk yurt icindeki, hatta ayni sehirdeki verimerkezi uzerinden cikacagim icin dusuk ping ile ipv6 internete ulasabilir durumda olacagim.

 

3- E PEKI HE.NET ?  TUNNELBROKER ?

ipv6 he.net tunnelbroker ile uzun zamandir evde kullaniyorum.

ipv6 zaten var evimde yani.

Ancak

Frankfurt uzerinden yaptigim v6 tunel yaklasik 80ms overhead koyuyor ping surelerine.

ip adresin he.net almanya gozuktugunden ipv6 internetinde mesela facebook’a girerken veya youtube’a girerken beni Alman zannediyor.

Iyimi? Aslinda cok cok iyi 🙂 ama ben kendi ipv6 ip blogumu kullanmak arzusundayim

 

4- PEKI NASIL YAPTIN SONUNDA? HADI ARTIK LAF SALATASINI KES!

su sekilde yaptim:

4-1-  Verimerkezindeki mikrotik router uzerinde yapilan ayarlar (Winbox ile anlatilmistir)

Interfaces > Interface > EKLE (+) 6to4 Tunnel

Name: verimerkezinden-eve-v6

Local Address: Verimerkezindeki routerin v4 ip adresi: 93.88.11.1

Remote Address: Evimde kullandigim sabit kablonet v4 ip adresi: 94.66.21.23

YANI:

/interface 6to4
add local-address=93.88.11.1 name=verimerkezinden-eve-v6 remote-address=94.66.21.23

4-2- Evdeki mikrotik router uzerinde yapilan ayarlar

Interfaces > Interface > EKLE (+) 6to4 Tunnel

Name: verimerkezinden-eve-v6

Local Address: Evimde kullandigim sabit kablonet v4 ip adresi: 94.66.21.23

Remote Address: Verimerkezindeki routerin v4 ip adresi: 93.88.11.1

YANI:

/interface 6to4
add local-address=94.66.21.23 name=verimerkezinden-eve-v6 remote-address=93.88.11.1

BU KADAR 🙂 Ne kadar kolay degilmi 🙂 6to4 tunelimiz kuruldu.

su anda fe80 ile baslayan verimerkezindeki v6 ip adresimizi evden pingleyebilir durumdayiz.

/ping fe80:bla:bla test edebiliriz.

5- Verimerkezindeki mikrotik router uzerinden devam: /48 tanimlayalim.

verimerkezindeki anons ettigim ipv6 adres blogum 2a02:800::/32 oldugundan yola cikarak.

ipv6 > routes

Ekle (+)

Dst. Address: 2a02:800:b0b::/48

Gateway: verimerkezinden-eve-v6

YANI:

add dst-address=2a02:800:b0b::/48 gateway=verimerkezinden-eve-v6

 

6- Evdeki mikrotik router uzerinden devam: 

ipv6 > routes

Ekle (+)

Dst.Address: ::/0

gateway:verimerkezinden-eve-v6

Bi tane daha ekle:

Dst. Address: 2a02:800:b0b::/48

type: unreachable

YANI:

/ipv6 route
add dst-address=::/0 gateway=verimerkezinden-eve-v6
add dst-address=2a02:800:b0b::/48 type=unreachable

 

NOT: Bunu neden boyle ekledik:

prefixmimiz icin default gateway ve unreachable route cunku, paketler routerlar arasinda luzumsuz bounce etmesin. tamam?

7- Evdeki mikrotik router uzerinden devam: /48 imiz icinden /64 tanimlayalim bir kac tane hatta komsulara dagitalim:

ipv6 > Addressess > Ekle (+)

Address: 2a02:800:b0b::9/64

Interface: bridge-local

Asagida Advertise secili olacak kutucuk . Ki mikrotik arkasindaki lokal agimizdaki cihazlar bu blok uzerinden ipv6 larini alsinlar doya doya.

Ok Apply

Isimiz bitti .

Gule gule kullanalim 😀

tebrikler. Artik evinizde ipv6 var.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

NOT: ND nedir /48 nedir /32 Nedir ? Route ipv6 falan? Ha?

tabi azicik ne ile ugrastiginizi biliyor olmaniz gerekiyor dogal olarak.

v6 bu borumu?

DHCPv6 sucks ND varken stateless ne guzel 🙂

 

SONUC:

 

shukko@Kazandibi ~ $ ifconfig 
enp8s0    Link encap:Ethernet  HWaddr 70:65:eb:4a:e2:fe  
          inet addr:192.168.88.27  Bcast:192.168.88.255  Mask:255.255.255.0
          inet6 addr: fe80::e726:b820:3f73:f2b4/64 Scope:Link
          inet6 addr: 2a02:800:b0b:0:25b2:4e7f:1b9a:f1a2/64 Scope:Global
          inet6 addr: 2a02:800:b0b:0:48a7:e94f:985b:d3ba/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2058293 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1896972 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2395810724 (2.3 GB)  TX bytes:1095854661 (1.0 GB)
          Memory:f7500000-f751ffff 

 

BIR SONUC DAHA ?

ping6 ipv6.google.com
PING ipv6.google.com(fra15s11-in-x0e.1e100.net) 56 data bytes
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=57.2 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=2 ttl=54 time=56.4 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=3 ttl=54 time=57.3 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=4 ttl=54 time=56.5 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=5 ttl=54 time=57.4 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=6 ttl=54 time=57.6 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=7 ttl=54 time=56.8 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=8 ttl=54 time=56.8 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=9 ttl=54 time=58.4 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=10 ttl=54 time=56.6 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=11 ttl=54 time=56.3 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=12 ttl=54 time=57.9 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=13 ttl=54 time=61.5 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=14 ttl=54 time=60.3 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=15 ttl=54 time=59.5 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=16 ttl=54 time=60.7 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=17 ttl=54 time=58.7 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=18 ttl=54 time=56.5 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=19 ttl=54 time=57.6 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=20 ttl=54 time=56.9 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=21 ttl=54 time=57.4 ms
64 bytes from fra15s11-in-x0e.1e100.net: icmp_seq=22 ttl=54 time=57.7 ms
^C
--- ipv6.google.com ping statistics ---
22 packets transmitted, 22 received, 0% packet loss, time 21033ms
rtt min/avg/max/mdev = 56.338/57.868/61.511/1.435 ms

 

 

 

for DOMAIN in $(find /etc/virtual/* -maxdepth 0 -type d ! -type l ! -name '*_off' ! -name 'usage' ! -name 'majordomo' -printf '%f \n'); do { for USER in $(cut -d: -f1 /etc/virtual/${DOMAIN}/quota); do { echo ${USER}@${DOMAIN} >> /root/activePopAccounts.txt; }; done; }; done;

 

en hizli rsync nasil yapilir?

https://gist.github.com/KartikTalwar/4393116

adresinden yola cikarak yapilir evet.

ORIGINAL:


rsync -aHAXxv --numeric-ids --delete --progress -e "ssh -T -c arcfour -o Compression=no -x" user@<source>:<source_dir> <dest_dir>



FLIP:


rsync -aHAXxv --numeric-ids --delete --progress -e "ssh -T -c arcfour -o Compression=no -x" [source_dir] [dest_host:/dest_dir]

not:

bu siliyor yahu eski dosyalari

aman silmesin dikkat edelim 🙂

 

suda var birde

 

rsync -rtXx --numeric-ids --progress -e "ssh -T -c aes128-ctr -o Compression=no -x" <user>@<ip>:/<source-path>/ /<dest.path>/

 

bu bisi silmiyor – delete yok dogal olarak –  ama az daha yavas

 

buunu birde boyle denemek mi lazim acaba?

 

rsync -rtXx --numeric-ids --progress -e "ssh -T -c arcfour -o Compression=no -x" <user>@<ip>:/<source-path>/ /<dest.path>/

olabilir denemedim 🙂


 

az sonra edit

 

aynen denedim

 

en krali bu tamam ya bu is ..

 

bir daha yazalim mi ?

rsync -rtXx --numeric-ids --progress -e "ssh -T -c arcfour -o Compression=no -x" <user>@<ip>:/<source-path>/ /<dest.path>/

NOT: dogal olarak bunu ALICI makinada calistiriyoruz.

 

Centos 5 coktan EOL oldu.

ama inatla yuksetlmek istenilmeyen sunucular var.

Centos 5 repolari vaulta tasinmis

bu dosyayi asagidaki sekilde guncellersen

en azindan final 5.11 devam edersin.

tabi yukseltmek gerek eninde sonunda.

Sene 2018, Centos5 mi kaldi yahu…

##

nano /etc/yum.repos.d/CentOS-Base.repo

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the 
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=http://vault.centos.org/5.11/os/$basearch
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#released updates 
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=http://vault.centos.org/5.11/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=http://vault.centos.org/5.11/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
baseurl=http://vault.centos.org/5.11/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
baseurl=http://vault.centos.org/5.11/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5