View previous topic :: View next topic |
Author |
Message |
Beme n00b
Joined: 12 Nov 2004 Posts: 7
|
Posted: Wed Oct 04, 2006 2:02 am Post subject: [solved] MySQL Port 3306 nach außen freigeben? |
|
|
Hallo Leute, weiß im Moment nicht mehr weiter..
Ich will einen Datenbankzugriff von außen (mit Hilfe von Borland Delphi und der MySQL-C-API ) auf MySQL realisieren. User mit Leserechten etc. etc. habe ich schon in MySQL (mysql-4.1.21) eingerichtet. Leider bekomme ich auch schon im internen Netzwerk keinen Connect ("Can't connect to MySQL-Server, error 10061").
Es scheint so, als sei der Port nicht richtig offen. Habe mal testweise in meinem Router den MySQL Port 3306 auf meinen Gentoo Server geöffnet, um dann von außen einen Portscan durchzuführen (http://www.heise.de/security/dienste/portscan/).
Dieser meldet aber: "3306 mysql geschlossen". Auch ein lokaler Portscanner auf dem Windows-Rechner im lokalen Netz zeigt den Port 3306 nicht als offen an.
Die "skip-networking" Option habe ich schon in der my.cnf auskommentiert. Hier trotzdem mal die my.cnf:
Code: | # /etc/mysql/my.cnf: The global mysql configuration file.
# $Header: /var/cvsroot/gentoo-x86/dev-db/mysql/files/my.cnf-4.1,v 1.3 2006/05/05 19:51:40 chtekk Exp $
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysql]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[mysqladmin]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[mysqlcheck]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[mysqldump]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[mysqlimport]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[mysqlshow]
character-sets-dir=/usr/share/mysql/charsets
default-character-set=utf8
[myisamchk]
character-sets-dir=/usr/share/mysql/charsets
[myisampack]
character-sets-dir=/usr/share/mysql/charsets
# use [safe_mysqld] with mysql-3
[mysqld_safe]
err-log = /var/log/mysql/mysql.err
# add a section [mysqld-4.1] or [mysqld-5.0] for specific configurations
[mysqld]
character-set-server = utf8
default-character-set = utf8
user = mysql
port = 3306
socket = /var/run/mysqld/mysqld.sock
pid-file = /var/run/mysqld/mysqld.pid
log-error = /var/log/mysql/mysqld.err
basedir = /usr
datadir = /var/lib/mysql
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
language = /usr/share/mysql/english
# security:
# using "localhost" in connects uses sockets by default
# skip-networking
bind-address = 127.0.0.1
log-bin
server-id = 1
# point the following paths to different dedicated disks
tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
# you need the debug USE flag enabled to use the following directives,
# if needed, uncomment them, start the server and issue
# #tail -f /tmp/mysqld.sql /tmp/mysqld.trace
# this will show you *exactly* what's happening in your server ;)
#log = /tmp/mysqld.sql
#gdb
#debug = d:t:i:o,/tmp/mysqld.trace
#one-thread
# uncomment the following directives if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# the following is the InnoDB configuration
# if you wish to disable innodb instead
# uncomment just the next line
#skip-innodb
#
# the rest of the innodb config follows:
# don't eat too much memory, we're trying to be safe on 64Mb boxes
# you might want to bump this up a bit on boxes with more RAM
innodb_buffer_pool_size = 16M
# this is the default, increase it if you have lots of tables
innodb_additional_mem_pool_size = 2M
#
# i'd like to use /var/lib/mysql/innodb, but that is seen as a database :-(
# and upstream wants things to be under /var/lib/mysql/, so that's the route
# we have to take for the moment
#innodb_data_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
#innodb_log_group_home_dir = /var/lib/mysql/
# you may wish to change this size to be more suitable for your system
# the max is there to avoid run-away growth on your machine
innodb_data_file_path = ibdata1:10M:autoextend:max:128M
# we keep this at around 25% of of innodb_buffer_pool_size
# sensible values range from 1MB to (1/innodb_log_files_in_group*innodb_buffer_pool_size)
innodb_log_file_size = 5M
# this is the default, increase it if you have very large transactions going on
innodb_log_buffer_size = 8M
# this is the default and won't hurt you
# you shouldn't need to tweak it
set-variable = innodb_log_files_in_group=2
# see the innodb config docs, the other options are not always safe
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
# uncomment the next directive if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
|
und hier die Ausgabe von "netstat":
Code: | hannibal ~ # netstat -an | grep LISTEN
...
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
...
unix 2 [ ACC ] STREAM LISTENING 8275 /dev/log
unix 2 [ ACC ] STREAM LISTENING 18228 /var/run/cgisock
unix 2 [ ACC ] STREAM LISTENING 12683 /var/run/clamav/clamd-socket
unix 2 [ ACC ] STREAM LISTENING 34179 /var/run/mysqld/mysqld.sock
|
Also ist laut netstat der Port offen. Bekomme aber definitiv so keine Connection hin.
Hat jemand fixe Ideen? Dann raus damit
Last edited by Beme on Wed Oct 04, 2006 11:39 am; edited 1 time in total |
|
Back to top |
|
|
Beme n00b
Joined: 12 Nov 2004 Posts: 7
|
Posted: Wed Oct 04, 2006 2:19 am Post subject: |
|
|
sorry Leute, lesen bildet
Einfach mysql nicht an localhost binden, sondern an eine bestimmte Adresse oder einfach ganz auskommentieren:
Code: | #bind-address = 127.0.0.1 |
Ich danke euch trotzdem, und hoffe, dass es trotz allem noch dem ein oder anderen hilft. |
|
Back to top |
|
|
toralf Developer
Joined: 01 Feb 2004 Posts: 3925 Location: Hamburg
|
Posted: Wed Oct 04, 2006 11:09 am Post subject: |
|
|
Du solltest den threat noch auf "[solved]" setzen. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|