Ubuntu Server 11.10, vsFTPd uplod nicht möglich!

Falkenhorst · 22. April 2012

Guten Abend

Ich bin daran spasseshalber einen Linuxserver am aufbauen, um damit später ne eigene NAS mit FTP zugang zu ermöglichen.

Also Ubuntu Server 11.10 hab ich installiert, mit dem Ubuntu Desktop.

Wenn ich jetzt z.B. von meinem Laptop auf den FTP connecte ftp://192.168.1.41 oder ftps://192.198.1.41 kann ich mich einloggen und Dinge herrunterladen aber nichts Hochladen. Wenn ich was Hochladen will kommt das:

Hapt ihr da ne Idee wieso es nicht geht?

Hier mal die vsftp.conf:

Code:

# Example config file /etc/vsftpd.conf
  #
  # The default compiled in settings are fairly paranoid. This sample file
  # loosens things up a bit, to make the ftp daemon more usable.
  # Please see vsftpd.conf.5 for all compiled in defaults.
  #
  # READ THIS: This example file is NOT an exhaustive list of vsftpd options.
  # Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
  # capabilities.
  #
  #
  # Run standalone?  vsftpd can run either from an inetd or as a standalone
  # daemon started from an initscript.
  listen=YES
  #
  # Run standalone with IPv6?
  # Like the listen parameter, except vsftpd will listen on an IPv6 socket
  # instead of an IPv4 one. This parameter and the listen parameter are mutually
  # exclusive.
  #listen_ipv6=YES
  #
  # Allow anonymous FTP? (Disabled by default)
  anonymous_enable=NO
  #
  # Uncomment this to allow local users to log in.
  local_enable=YES
  #
  # Uncomment this to enable any form of FTP write command.
  #write_enable=YES
  #
  # Default umask for local users is 077. You may wish to change this to 022,
  # if your users expect that (022 is used by most other ftpd's)
  #local_umask=0077
  #
  # Uncomment this to allow the anonymous FTP user to upload files. This only
  # has an effect if the above global write enable is activated. Also, you will
  # obviously need to create a directory writable by the FTP user.
  #anon_upload_enable=NO
  #
  # Uncomment this if you want the anonymous FTP user to be able to create
  # new directories.
  #anon_mkdir_write_enable=NO
  #
  # Activate directory messages - messages given to remote users when they
  # go into a certain directory.
  dirmessage_enable=YES
  #
  # If enabled, vsftpd will display directory listings with the time
  # in  your  local  time  zone.  The default is to display GMT. The
  # times returned by the MDTM FTP command are also affected by this
  # option.
  use_localtime=YES
  #
  # Activate logging of uploads/downloads.
  xferlog_enable=YES
  #
  # Make sure PORT transfer connections originate from port 20 (ftp-data).
  connect_from_port_20=YES
  #
  # If you want, you can arrange for uploaded anonymous files to be owned by
  # a different user. Note! Using "root" for uploaded files is not
  # recommended!
  #chown_uploads=YES
  #chown_username=whoever
  #
  # You may override where the log file goes if you like. The default is shown
  # below.
  #xferlog_file=/var/log/vsftpd.log
  #
  # If you want, you can have your log file in standard ftpd xferlog format.
  # Note that the default log file location is /var/log/xferlog in this case.
  #xferlog_std_format=YES
  #
  # You may change the default value for timing out an idle session.
  #idle_session_timeout=600
  #
  # You may change the default value for timing out a data connection.
  #data_connection_timeout=120
  #
  # It is recommended that you define on your system a unique user which the
  # ftp server can use as a totally isolated and unprivileged user.
  #nopriv_user=ftpsecure
  #
  # Enable this and the server will recognise asynchronous ABOR requests. Not
  # recommended for security (the code is non-trivial). Not enabling it,
  # however, may confuse older FTP clients.
  #async_abor_enable=YES
  #
  # By default the server will pretend to allow ASCII mode but in fact ignore
  # the request. Turn on the below options to have the server actually do ASCII
  # mangling on files when in ASCII mode.
  # Beware that on some FTP servers, ASCII support allows a denial of service
  # attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
  # predicted this attack and has always been safe, reporting the size of the
  # raw file.
  # ASCII mangling is a horrible feature of the protocol.
  #ascii_upload_enable=YES
  #ascii_download_enable=YES
  #
  # You may fully customise the login banner string:
  #ftpd_banner=Welcome to blah FTP service.
  #
  # You may specify a file of disallowed anonymous e-mail addresses. Apparently
  # useful for combatting certain DoS attacks.
  #deny_email_enable=YES
  # (default follows)
  #banned_email_file=/etc/vsftpd.banned_emails
  #
  # You may restrict local users to their home directories.  See the FAQ for
  # the possible risks in this before using chroot_local_user or
  # chroot_list_enable below.
  #chroot_local_user=YES
  #
  # You may specify an explicit list of local users to chroot() to their home
  # directory. If chroot_local_user is YES, then this list becomes a list of
  # users to NOT chroot().
  #chroot_local_user=YES
  #chroot_list_enable=YES
  # (default follows)
  #chroot_list_file=/etc/vsftpd.chroot_list
  #
  # You may activate the "-R" option to the builtin ls. This is disabled by
  # default to avoid remote users being able to cause excessive I/O on large
  # sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
  # the presence of the "-R" option, so there is a strong case for enabling it.
  #ls_recurse_enable=YES
  #
  # Debian customization
  #
  # Some of vsftpd's settings don't fit the Debian filesystem layout by
  # default.  These settings are more Debian-friendly.
  #
  # This option should be the name of a directory which is empty.  Also, the
  # directory should not be writable by the ftp user. This directory is used
  # as a secure chroot() jail at times vsftpd does not require filesystem
  # access.
  secure_chroot_dir=/var/run/vsftpd/empty
  #
  # This string is the name of the PAM service vsftpd will use.
  pam_service_name=vsftpd
  #
  # This option specifies the location of the RSA certificate to use for SSL
  # encrypted connections.
  rsa_cert_file=/etc/ssl/private/vsftpd.pem
  #
  local_max_rate=0
  #
  ftp_data_port=20
  #
  listen_port=21
  #
  max_clients=5
  #
  max_per_ip=2
  #
  force_local_logins_ssl=YES
  #
  anon_root=/home/ftp
  #

Hier noch die vsftp.log:

Code:

Sun Apr 22 02:47:06 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 02:47:08 2012 [pid 1] [anonymous] FAIL LOGIN: Client "127.0.0.1"
  Sun Apr 22 02:47:09 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 02:47:17 2012 [pid 1] [claude] OK LOGIN: Client "127.0.0.1"
  Sun Apr 22 02:53:06 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 02:53:07 2012 [pid 1] [anonymous] FAIL LOGIN: Client "127.0.0.1"
  Sun Apr 22 02:53:08 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 02:53:17 2012 [pid 1] [home] OK LOGIN: Client "127.0.0.1"
  Sun Apr 22 03:47:02 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 03:47:04 2012 [pid 1] [anonymous] FAIL LOGIN: Client "127.0.0.1"
  Sun Apr 22 03:47:05 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 03:47:12 2012 [pid 1] [home] OK LOGIN: Client "127.0.0.1"
  Sun Apr 22 03:47:26 2012 [pid 3] [home] OK DOWNLOAD: Client "127.0.0.1", "/home/home/../teamspeak/examples.desktop", 179 bytes, 11.90Kbyte/sec
  Sun Apr 22 04:02:46 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 04:02:46 2012 [pid 1] [claude] OK LOGIN: Client "127.0.0.1"
  Sun Apr 22 14:40:05 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:40:07 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:40:08 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:40:17 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:41:45 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:41:47 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:41:48 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:41:51 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:42:02 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:42:02 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:42:02 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:42:02 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:42:19 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:42:19 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:42:33 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:42:33 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:49:01 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:49:03 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:49:04 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:49:15 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:49:43 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:49:45 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:49:52 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:49:52 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:49:53 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:49:53 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:50:22 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:29 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:35 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:36 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:36 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:37 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:37 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:37 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:37 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:37 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:38 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:38 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:50:38 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:52:26 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:52:28 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:52:29 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:52:29 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:52:29 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:52:29 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:52:44 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:52:44 2012 [pid 1] [claude] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:52:58 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:52:58 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:01 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:02 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:02 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:02 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:02 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:03 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:03 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:04 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:04 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:04 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:05 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:05 2012 [pid 2] CONNECT: Client "192.168.1.110", "Connection refused: too many sessions for this address."
  Sun Apr 22 14:53:15 2012 [pid 3] [home] OK DOWNLOAD: Client "192.168.1.110", "/home/home/examples.desktop", 179 bytes, 8.91Kbyte/sec
  Sun Apr 22 14:55:09 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:55:11 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:55:12 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:55:12 2012 [pid 1] [claude] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:55:12 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:55:13 2012 [pid 1] [claude] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 14:55:22 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 14:55:22 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:10:19 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:10:21 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:10:28 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:10:28 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:10:28 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:10:28 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:10:45 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:10:45 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:13:03 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:13:03 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:13:17 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:13:19 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:13:25 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:13:25 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:13:25 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:13:25 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:13:35 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:13:35 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:22:21 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:22:23 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:22:29 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:22:29 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:22:30 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:22:30 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:22:46 2012 [pid 3] [home] OK DOWNLOAD: Client "192.168.1.110", "/home/home/examples.desktop", 179 bytes, 57.22Kbyte/sec
  Sun Apr 22 15:22:58 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:22:58 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:42:15 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:42:18 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:42:23 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:42:23 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:42:23 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:42:23 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 15:42:32 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 15:42:32 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 16:03:48 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 16:03:48 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 16:03:54 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 16:03:56 2012 [pid 1] [anonymous] FAIL LOGIN: Client "192.168.1.110"
  Sun Apr 22 16:04:01 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 16:04:01 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 16:04:08 2012 [pid 2] CONNECT: Client "192.168.1.110"
  Sun Apr 22 16:04:08 2012 [pid 1] [home] OK LOGIN: Client "192.168.1.110"
  Sun Apr 22 16:09:03 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 16:09:05 2012 [pid 1] [anonymous] FAIL LOGIN: Client "127.0.0.1"
  Sun Apr 22 16:09:06 2012 [pid 2] CONNECT: Client "127.0.0.1"
  Sun Apr 22 16:09:13 2012 [pid 1] [home] OK LOGIN: Client "127.0.0.1"

Wenn ihr noch was braucht, einfach schreiben!
Gruss
Falkenhorst

mitcharts · 22. April 2012

Mit welchem User willst du den FTP denn nutzen?

Über "Anonymous" z.B. wird das mit der Config nicht funktionieren. Du solltest dafür folgende Einträge in der cfg haben:
anonymous_enable=YES (in deiner cfg NO)
anon_upload_enable=YES (in deiner cfg auskommentiert und NO)
anon_mkdir_write_enable=YES (in deiner cfg auskommentiert und NO)

Falkenhorst · 22. April 2012

Ich will das ich mit dem Benutzer "home" drauf zugreifen kann.

mitcharts · 22. April 2012

Ich geh davon aus, dass dieser Nutzer existiert. Dann solltest du mal den Eintrag "write_enable=YES" auskommentieren und den Upload nochmal probieren.

Falkenhorst · 22. April 2012

Ja, der Nutzer exisitiert.

Auskommentieren??? Bin noch Linux anfänger!

Anonym will ich nicht, da der Server mal öffentlich sein soll, für meine Dateien die ich in der Schule mache und zuhause auch brauche.

Klar, da wäre Dropbox besser aber so weiss ich was mit meinen Daten passiert und wo die sind!

mitcharts · 22. April 2012

Einfach das Rautezeichen am Anfang der Zeile entfernen und den Dienst neustarten (sudo restart vsftpd).

Schau auch mal hier nach, da steht vieles zu dem von dir genutzten Dienst:
vsftpd > Wiki > ubuntuusers.de

cracker · 22. April 2012

ich würde da aber netzwerk-intern samba empfehlen...

BdMdesigN · 22. April 2012

Ändere mal in der vsftp.conf:

# Uncomment this to enable any form of FTP write command.
#write_enable=YES

zu

# Uncomment this to enable any form of FTP write command.
write_enable=YES

Dann sollte auch das schreiben klappen.

MfG

Peter

Falkenhorst · 22. April 2012

Danke mitcharts, es hat geklappt!
Für was sind denn die #-Zeichen gut? Ob ein Befehl Aktiv ist oder nicht?

@cracker: samba werd ich auch noch testen, keine Angst!

Hab aber noch ne frage, zwar nicht zu vsFTPd sondern zur IP.
Ich habe meinem Server die Statische IP 192.168.1.45 gegeben. Starte ich den Server neu, hb ich nachher keine Verbindung, da eht0 nicht an ist. Erst wenn ich
Code:
sudo ifconfig eth0 192.168.1.45
eingebe funktionierts! Intern funtktioniert nachher alles, komm auf die Synology ect. nur hab ich keine Verbindung nach aussen, sprich kein Internet. Lass ich ihn per dhcp beziehen, klappt alles Wunderbar, nur kloppt mich mein Vater zusammen! Aber eben, für FTP wäre ja ne Statische IP von Vorteil, denn sonst müsst ich jede IP in der Fritte Weiterleiten!

Hier mal die /etc/networks/interfaces:
Code:
 # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).
   
  # The loopback network interface
  auto lo
  iface lo inet loopback
   
  # The primary network interface
  auto eth0
  # Beim Bootvorgang automatisch starten
  iface eth0 inet static
  adress 192.168.1.45
  netmask 255.255.255.0
  gateway 192.168.1.1
  dns-nameserver 157.161.9.7 157.161.9.6
  

mitcharts · 22. April 2012

Zitat von Falkenhorst: ↑

Für was sind denn die #-Zeichen gut? Ob ein Befehl Aktiv ist oder nicht?
Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen.

Kurz und knapp: Japp.

Falkenhorst · 22. April 2012

Ah, habs auch von meinem Vater erfahren, der hatt mich ausgelachen als ich ihm gesagt habe das es am Ausklammern lag!

Habt ihr ne Idee zum IP Problem oder soll ich kurz nen neuen Thread aufmachn?

cracker · 22. April 2012

zu welchem ip-problem?

Falkenhorst · 22. April 2012

Zitat von Falkenhorst: ↑
Hab aber noch ne frage, zwar nicht zu vsFTPd sondern zur IP.
Ich habe meinem Server die Statische IP 192.168.1.45 gegeben. Starte ich den Server neu, hb ich nachher keine Verbindung, da eht0 nicht an ist. Erst wenn ich
Code:
sudo ifconfig eth0 192.168.1.45
eingebe funktionierts! Intern funtktioniert nachher alles, komm auf die Synology ect. nur hab ich keine Verbindung nach aussen, sprich kein Internet. Lass ich ihn per dhcp beziehen, klappt alles Wunderbar, nur kloppt mich mein Vater zusammen! Aber eben, für FTP wäre ja ne Statische IP von Vorteil, denn sonst müsst ich jede IP in der Fritte Weiterleiten!

Hier mal die /etc/networks/interfaces:
Code:
 # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).
   
  # The loopback network interface
  auto lo
  iface lo inet loopback
   
  # The primary network interface
  auto eth0
  # Beim Bootvorgang automatisch starten
  iface eth0 inet static
  adress 192.168.1.45
  netmask 255.255.255.0
  gateway 192.168.1.1
  dns-nameserver 157.161.9.7 157.161.9.6
  
Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen.
Dieses Problem!

Wenn ich mit
Code:
sudo /etc/init.d/networking restert
nen Netzwerkrestart mache kommt immer am schluss:
Code:
 Don't seem to have all the variables for eth0/inet.
Failed to bring up eth0

cracker · 22. April 2012

ja ein server läuft normalerweise 24/7 ..
Du könntest auch ein kleines c-programm schreiben dass den befehl enthält dass du dann in den "autostart" von linux packst.. wie das mit dem Autostart geht weiß ich nicht. Allerdings wäre das Programm fast keine Arbeit.

Falkenhorst · 22. April 2012

ja, schon klar das ein Server normalerweise 24/7 läuft aber ich will später ne Zeitsteuerung machen, sprich der Server fährt z.B um 24 Uhr runter und wird um 6 Uhr mit einem WOL gestartet.

Aber eben, ich hab das doofe Problem mit der IP, denn auch ohe die kann ich kein WOL einrichten, wenn die IP immer ändert.

Edit: Wenn ich die Adresse per DHCP beziehe gehts, wenn ich die Fix vergebe und einen Network Restart mache kommt immer Failed to bring up eth0. Hab alles bedänkliche gelesen un probiert, komplette Einträge ür die Interfaces genommen und angepasst, geht aber alles nicht! Treiber scheinen auch aktuell zu sein, jedenfalls sagt er mir das er keine Findet.

Vieleicht frisst meine Netzwerkkarte das auh nicht, denn der PC ist ja bisschen älter! Morgen kireg ich was Leistungsstärkeres mit Haufen Festplatten und dann werd ich meinem Vater zeigen das man da nicht n Haufen Kohle für ein 4 Bay NAS ausgeben muss und man sogar die gleichen fuktionen wie bei der Synology hat, sind halt einfach sehr, sehr gut versteckt!

Ubuntu Server 11.10, vsFTPd uplod nicht möglich!

Ubuntu Server 11.10, vsFTPd uplod nicht möglich!

SysProfile Windows Foren

Hardware Foren