Hinweis: Das Forum wird geschlossen! Neue Registrierungen sind nicht mehr möglich!

 Zurück zu Pro-Linux   Foren-Übersicht   FAQ     Suchen    Mitgliederliste
mldonkey und fli4l?

 
Neuen Beitrag schreiben   Auf Beitrag antworten    Pro-Linux Foren-Übersicht -> Software
Vorheriges Thema anzeigen :: Nächstes Thema anzeigen  
Autor Nachricht
templer



Anmeldungsdatum: 09.10.2001
Beiträge: 112
Wohnort: Gachenbach

BeitragVerfasst am: 06. Dez 2002 9:48   Titel: mldonkey und fli4l?

Hallo Leute,

langsam bin ich am verzweifeln!
Ich weiss nicht was ich immer falsch mache. Habe mir mldonkey herunter geladen als bz2-shared. Entpackt -> gehe in Verzeichnis und starte ./mldonkey. Danach fragt er mich ob ich die gui öffnen will, sage ich ja -> gui geht auf. Jetzt habe ich eine Ellenlange Liste mit Servern. Er fängt an die Liste durchzugehen, schreibt connect hin -> ca3-4 Sekunden später verschwindet connect wieder. Klicke ich speziell einen Server an und klicke auf connect, das gleiche Spiel.

Was mache ich denn schon wieder falsch? Liegt es an meinem Router? (486 mit fli4l?)

Kann mir bitte jemand helfen?

Danke Templer
_________________
OrdoMilitarisTempli-Moege das Licht mit euch sein
 
Benutzer-Profile anzeigen Private Nachricht senden Website dieses Benutzers besuchen

DummerKleinerNeuling
Gast





BeitragVerfasst am: 06. Dez 2002 14:20   Titel: Re: mldonkey und fli4l?

hi

also schließ erstmal die gui u. starte eine konsole. tipp dann telnet localhost 4000 ein! verbinden kann er sich wahrscheinlich nicht weil die server im a.... sind! deshalb: max_server_age 1 u. dann remove_old_servers. jetzt sollten nur noch aktuelle server drinn sein! stell am besten den serverupdater aus (set update_server_list false) u. hol dir die listen selbst (z.B. von saugstube). Sollte Adanet da nicht drin sein, dann googel weng danach - ist weit u. breit der beste server!

>> Liegt es an meinem Router?

solange du den port 4662 (sofern du ihn nicht umgestellt hast) offen hast liegts nicht daran!

greez
 

heinbloed
Gast





BeitragVerfasst am: 11. Dez 2002 10:03   Titel: Re: mldonkey und fli4l?

Hier mal den base.txt mit dem der router und der Esel läuft:
---------------------schnipp---------

##-----------------------------------------------------------------------------
## base.txt - fli4l configuration parameters 2.0.4
##
## You can edit/change this file with fliwiz V1.6 or any text editor.
##
## P L E A S E R E A D T H E D O C U M E N T A T I O N ,
## S E E R E A D M E . T X T
##
## B I T T E U N B E D I N G T D I E D O K U M E N T A T I O N
## L E S E N , S I E H E R E A D M E . T X T
##
## Creation: 26.06.2001 fm
## Last Update: $Id: base.txt,v 1.20.2.2 2002/02/22 09:00:14 fm Exp $
##
## Copyright (c) 2001-2002 Frank Meyer <frank@fli4l.de>
##
## This program is free software; you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation; either version 2 of the License, or
## (at your option) any later version.
##-----------------------------------------------------------------------------

#------------------------------------------------------------------------------
# General settings:
#------------------------------------------------------------------------------
HOSTNAME='fli4l' # name of fli4l router
PASSWORD='koelner' # password for telnetd, ftpd and sshd
MOUNT_BOOT='rw' # mount boot device (floppy): ro, rw, no

RAMSIZE='2048' # size of ramdisk for unzipped opt.tgz
# the variables MOUNT_OPT, PART_OPT and UPDATE_MODE will be ignored if
# RAMSIZE is not empty. see docu
MOUNT_OPT='ro' # mount opt device: ro, rw
PART_OPT='hda2' # location of opt-files? ram1 or disk-partition
UPDATE_MODE='full' # add, cfg, full, none, see documentation

#------------------------------------------------------------------------------
# Ethernet card drivers:
# uncomment your ethernet card
#------------------------------------------------------------------------------
ETH_DRV_N='1' # number of ethernet drivers to load, usually 1
#ETH_DRV_1='3c505' # ISA: 3COM Etherlink Plus (3c505)
#ETH_DRV_1='3c507' # ISA: 3COM Etherlink 16 (3c507)
#ETH_DRV_1='3c509' # ISA: 3COM EtherLinkIII (3c509)
#ETH_DRV_1='3c515' # ISA: 3COM EtherLink XL ISA (3c515)
#ETH_DRV_1='3c59x' # PCI: 3COM Vortex/Boomerang 3c59x,3c900,3c905
#ETH_DRV_1='82596' # Apricot Xen-II on board Ethernet
#ETH_DRV_1='3c503' # ISA: 3COM EtherLinkII (3c503)
#ETH_DRV_1='e2100' # ISA: Cabletron E21xx ISA
#ETH_DRV_1='hp' # ISA: HP PCLAN (27245, 27xxx) ISA
#ETH_DRV_1='hp-plus' # ISA: HP PCLAN+ (27247B and 27252A) ISA
#ETH_DRV_1='ne' # ISA: NE2000 ISA clone (eg. Realtek 8019,
# Accton 16xx, NatSemi 8390, UMC 9003/9008)
#ETH_DRV_1='ne2k-pci' # PCI: NE2000 PCI clone (eg. Realtek 8029,
# Winbond 89c940)
#ETH_DRV_1='smc-ultra' # ISA: SMC ULTRA
#ETH_DRV_1='smc-ultra32' # EISA: SMC ULTRA32 (NEW)
#ETH_DRV_1='wd' # ISA: SMC WD80*3
#ETH_DRV_1='at1700' # ISA: AT1700 (Fujitsu 86965) ISA
#ETH_DRV_1='cs89x0' # ISA: IBM Etherjet, cs89x0 based Cards (Option
io=0xnnn necessary!)
#ETH_DRV_1='de4x5' # PCI/EISA: Digital DE425, DE434, DE435, DE450,
DE500
#ETH_DRV_1='depca' # ISA: DEPCA, DE10x, DE200, DE201, DE202, DE422
#ETH_DRV_1='dgrs' # PCI: Digi International RightSwitch PCI/EISA
#ETH_DRV_1='dmfe' # PCI: DM9102 compatible PCI cards from Davicom
#ETH_DRV_1='elp486' # ISA: Intel Professional Workstation/panther
82596
#ETH_DRV_1='eepro' # ISA: Intel EtherExpress Pro/10
#ETH_DRV_1='eepro100' # PCI: Intel EtherExpressPro PCI 10+/100B/100+
#ETH_DRV_1='eexpress' # ISA: EtherExpress16 ISA
#ETH_DRV_1='epic100' # PCI: SMC EPIC/100 (EtherPower II) PCI
#ETH_DRV_1='eth16i' # ISA/EISA: ICL EtherTeam 16i/32
#ETH_DRV_1='ewrk3' # ISA: EtherWORKS 3 ISA (DE203, DE204, DE205)
#ETH_DRV_1='fealnx' # PCI: ASOUND LAN 8139 card - not RTL8139 (NEW)
#ETH_DRV_1='hp100' # ISA/EISA/PCI: HP 10/100VG PCLAN (ISA, EISA,
PCI)
#ETH_DRV_1='lance' # ISA: AMD LANCE and PCnet (AT1500, NE2100) ISA
#ETH_DRV_1='old_tulip' # PCI: Old DECchip Tulip (dc21x4x) PCI
#ETH_DRV_1='pcnet32' # PCI: AMD PCI PCnet32
#ETH_DRV_1='rtl8139-orig' # PCI: RealTek 8129/8139 (not 8019/8029!)
ETH_DRV_1='rtl8139' # PCI: RealTek 8129/8139 (not 8019/8029!) (NEW)
#ETH_DRV_1='8139too' # PCI: RealTek 8139 10/100 MB (NEW)
#ETH_DRV_1='sis900' # PCI: SiS 900/7016
#ETH_DRV_1='sundance' # PCI: DFE-550FX or DFE-530TXS (NEW)
#ETH_DRV_1='tlan' # PCI: TI ThunderLAN (Compaq Netelligent ...)
#ETH_DRV_1='tulip' # PCI: DECchip Tulip (dc21x4x) PCI
#ETH_DRV_1='natsemi' # PCI: Nat Semi
#ETH_DRV_1='starfire' # PCI: Starfire
#ETH_DRV_1='via-rhine' # PCI: VIA Rhine PCI (3043, VT86c100A,
dfe-530tx)
#ETH_DRV_1='winbond-840' # PCI: Winbond 840
#ETH_DRV_1='lanstreamer' # Token Ring: IBM Auto LANStreamer PCI Adapter
#ETH_DRV_1='olympic' # Token Ring: IBM cards (Pit/Pit-Phy/Olympic)
#ETH_DRV_1='ibmtr' # Token Ring: IBM 16/4
#ETH_DRV_1='pcnet_cs' # PCMCIA: NS8390-based cards (NE2000, DLINK etc)
#ETH_DRV_1='3c574_cs' # PCMCIA: 3Com 574
#ETH_DRV_1='3c575_cb' # PCMCIA: 3Com 575
#ETH_DRV_1='3c589_cs' # PCMCIA: 3Com 589
#ETH_DRV_1='airo' # PCMCIA: Airo 4500 & 4800 series cards
#ETH_DRV_1='airo_cs' # PCMCIA: Airo 4500 & 4800 series cards
#ETH_DRV_1='eepro100_cb' # PCMCIA: EtherExpress Pro 100
#ETH_DRV_1='epic_cb' # PCMCIA: SMC 83c170 EPIC/100
#ETH_DRV_1='ibmtr_cs' # PCMCIA: IBM Token Ring
#ETH_DRV_1='netwave_cs' # PCMCIA: Netwave AirSurfer Wireless LAN
#ETH_DRV_1='nmclan_cs' # PCMCIA: New Media Ethernet LAN
#ETH_DRV_1='ray_cs' # PCMCIA: Raylink wireless cards
#ETH_DRV_1='smc91c92_cs' # PCMCIA: SMC91c92-based cards
#ETH_DRV_1='tulip_cb' # PCMCIA: DEC 21040-family cards
#ETH_DRV_1='wavelan_cs' # PCMCIA: WaveLAN
#ETH_DRV_1='wavelan2_cs' # PCMCIA: WaveLAN2
#ETH_DRV_1='wvlan_cs' # PCMCIA: Lucent WaveLAN/IEEE 802.11
#ETH_DRV_1='xirc2ps_cs' # PCMCIA: Xircom: CE2, CEM28, CEM33, or CE3
#ETH_DRV_1='wl24_cs' # PCMCIA: ELSA Airlancer MC-2
#ETH_DRV_1='cs89x0_cs' # PCMCIA: IBM EtherJet Ethernet Adapter

ETH_DRV_1_OPTION='' # additional option, e.g. 'io=0x340' for ne

#------------------------------------------------------------------------------
# Ether networks used with IP protocol:
#------------------------------------------------------------------------------
IP_ETH_N='1' # number of ip ethernet networks, usually 1
IP_ETH_1_NAME='' # optional: other device name than ethX
IP_ETH_1_IPADDR='192.168.4.1' # IP address of your n'th ethernet card
IP_ETH_1_NETWORK='192.168.4.0' # network of your LAN
IP_ETH_1_NETMASK='255.255.255.0' # netmask of your LAN

#------------------------------------------------------------------------------
# Additional routes, optional
#------------------------------------------------------------------------------
IP_DEFAULT_GATEWAY='' # normally not used, read documentation!
IP_ROUTE_N='0' # number of additional routes
IP_ROUTE_1='192.168.7.0 255.255.255.0 192.168.6.99' # network netmask gateway

#------------------------------------------------------------------------------
# Masquerading:
#------------------------------------------------------------------------------
MASQ_NETWORK='192.168.4.0/24' # networks to masquerade (e.g. our LAN)
MASQ_MODULE_N='1' # load n masq modules (default: only ftp)
MASQ_MODULE_1='ftp' # ftp
MASQ_MODULE_2='h323' # h323 (netmeeting)
MASQ_MODULE_3='icq' # icq (use with caution!)
MASQ_MODULE_4='irc' # irc
MASQ_MODULE_5='raudio' # raudio
MASQ_MODULE_6='vdolive' # vdolive
MASQ_MODULE_7='quake' # quake
MASQ_MODULE_8='cuseeme' # cuseeme
MASQ_MODULE_9='mms' # MSN-Filetransfer
MASQ_MODULE_10='pptp' # pptp
MASQ_MODULE_11='ipsec' # ipsec
MASQ_MODULE_12='dplay' # dplay (direct play)
MASQ_MODULE_13='msn-0.02' # msn zone (use version 0.01 or 0.02)
MASQ_MODULE_14='udp_dloose' # pseudo mod: some internet games need it

MASQ_FTP_PORT_N='0' # using ftp masq-module on different ports
MASQ_FTP_PORT_1='21' # standard ftp port
MASQ_FTP_PORT_2='2021' # additional port

#------------------------------------------------------------------------------
# Optional package: PORTFW
#
# If you set OPT_PORTFW='yes', you can also edit opt/etc/portfw.sh
#------------------------------------------------------------------------------
OPT_PORTFW='yes' # install port forwarding tools/modules
PORTFW_N='3' # how many portforwardings to set up
#PORTFW_1='8080 192.168.4.15:80 tcp' # sample 1: forward ext. port 8080 to int.
# host 192.168.6.15 to port 80 (use tcp)
#PORTFW_2='3000-3010 192.168.4.15 tcp' # sample 2: forward portrange to int.
host
# 192.168.5.15 (use tcp)
PORTFW_1='4661 192.168.6.2:4661 tcp' # eDonkey tcp, connect to Server
PORTFW_2='4662 192.168.6.2:4662 tcp' # eDonkey tcp, connect to Client
PORTFW_3='4665 192.168.6.2:4665 udp' # eDonkey udp, send messages to Server

#------------------------------------------------------------------------------
# Routing without masquerading
#------------------------------------------------------------------------------
ROUTE_NETWORK='' # optional: route from/to network, no masq

#------------------------------------------------------------------------------
# Routing: internal hosts to deny forwarding
#------------------------------------------------------------------------------
FORWARD_DENY_HOST_N='0' # number of denied hosts
FORWARD_DENY_HOST_1='192.168.6.5' # optional: 1st denied host
FORWARD_DENY_HOST_2='192.168.6.6' # optional: 2nd denied host

#------------------------------------------------------------------------------
# Routing: ports to reject/deny forwarding (from inside and outside!)
#------------------------------------------------------------------------------
FORWARD_DENY_PORT_N='1' # no. of ports to reject/deny forwarding
FORWARD_DENY_PORT_1='137:139 REJECT' # deny/reject forwarding of netbios
FORWARD_TRUSTED_NETS='' # but allow forwarding between LANs

#------------------------------------------------------------------------------
# Firewall: ports to reject/deny from outside (all served ports)
#
# here we leave two ports untouched:
#
# 53 dns
# 113 auth
#------------------------------------------------------------------------------
FIREWALL_DENY_PORT_N='6' # no. of ports to reject/deny
FIREWALL_DENY_PORT_1='0:52 REJECT' # privileged ports: reject or deny
FIREWALL_DENY_PORT_2='54:112 REJECT' # privileged ports: reject or deny
FIREWALL_DENY_PORT_3='114:1023 REJECT' # privileged ports: reject or deny
FIREWALL_DENY_PORT_4='5000:5001 REJECT' # imond/telmond ports: reject or deny
FIREWALL_DENY_PORT_5='8000 REJECT' # proxy access: reject or deny
FIREWALL_DENY_PORT_6='20012 REJECT' # vbox server access: reject or deny

FIREWALL_DENY_ICMP='yes' # deny icmp (ping): yes or no
FIREWALL_LOG='yes' # log access to rejected/denied ports

#------------------------------------------------------------------------------
# Domain configuration:
#------------------------------------------------------------------------------
START_DNS='yes' # start dns server: yes or no
DNS_FORWARDERS='212.122.128.10 212.122.129.10' # DNS servers of your
provider, e.g. MSN
DNS_VERBOSE='no' # log queries in /usr/local/ens/ens.log
DOMAIN_NAME='lan.fli4l' # your domain name
DNS_FORBIDDEN_N='0' # number of forbidden domains
DNS_FORBIDDEN_1='foo.bar' # 1st forbidden domain
DNS_FORBIDDEN_2='bar.foo' # 2nd forbidden domain
HOSTS_N='4' # number of hosts in your domain
HOST_1='192.168.4.1 fli4l' # 1st host: ip and name
HOST_2='192.168.4.2 linux' # 2nd host: ip and name
HOST_3='192.168.4.3 client3' # 3rd host: ip and name
HOST_4='192.168.4.4 client4' # 4th host: ip and name

#------------------------------------------------------------------------------
# Special DNS configuration
#------------------------------------------------------------------------------
DNS_N='0' # number of special dns servers, normally 0
#DNS_1='firma.de 192.168.1.12' # 1st special dns server for firma.de
#DNS_2='lan.firma.de 192.168.2.12' # 2nd special dns server for lan.firma.de

#------------------------------------------------------------------------------
# imond configuration:
#------------------------------------------------------------------------------
START_IMOND='yes' # start imond: yes or no
IMOND_PORT='5000' # TCP-Port, see also FIREWALL_DENY_PORT_x!
IMOND_PASS='' # imond-password, may be empty
IMOND_ADMIN_PASS='' # imond-admin-password, may be empty
IMOND_LED='' # tty for led: com1 - com4 or empty
IMOND_BEEP='no' # beep if connection going up/down
IMOND_LOG='no' # log /var/log/imond.log: yes or no
IMOND_LOGDIR='/var/log' # log-directory, e.g. /var/log
IMOND_ENABLE='yes' # accept "enable/disable" commands
IMOND_DIAL='no' # accept "dial/hangup" commands
IMOND_ROUTE='no' # accept "route" command
IMOND_REBOOT='no' # accept "reboot" command

#------------------------------------------------------------------------------
# Generic circuit configuration:
#------------------------------------------------------------------------------
IP_DYN_ADDR='yes' # use dyn. ip addresses (most providers do)
DIALMODE='auto' # standard dialmode: auto, manual, or off

#------------------------------------------------------------------------------
# optional package: syslogd
#------------------------------------------------------------------------------
OPT_SYSLOGD='yes' # start syslogd: yes or no
SYSLOGD_DEST_N='1' # number of destinations
SYSLOGD_DEST_1='*.* /dev/console' # n'th prio & destination of syslog msgs
SYSLOGD_DEST_2='*.* @192.168.4.2' # example: loghost 192.168.4.2
SYSLOGD_DEST_3='kern.info /var/log/dial.log' # example: log infos

#------------------------------------------------------------------------------
# optional package: klogd
#------------------------------------------------------------------------------
OPT_KLOGD='yes' # start klogd: yes or no

#------------------------------------------------------------------------------
# optional package: y2k correction
#------------------------------------------------------------------------------
OPT_Y2K='no' # y2k correction: yes or no
Y2K_DAYS='' # correct hardware Y2K-Bug: add x days

#------------------------------------------------------------------------------
# Optional package: PNP
#------------------------------------------------------------------------------
OPT_PNP='no' # install isapnp tools: yes or no
---------------------schnapp-------------
Den Treiber der Netzwerkkarte anpassen unbd zur Not ne neue Diskette erstellen
Gruß Hein*
 

fli4l
Gast





BeitragVerfasst am: 13. Dez 2002 17:58   Titel: Re: mldonkey und fli4l?

hi ,schau dir den eintrag von heinbloed an ,so musst du deinen router konfigurieren Surprised)
zum 2ten ,es kann eine weile dauern bis der mldonkey connected ,also abwarten
zum 3ten ,es soll wohl ab und an probleme geben mit den libraries ,deshalb mal die static ziehen und nicht die shared von mldonkey ,das liest du aber mal besser auf der seite www.freesoftware.fsf.org/mldonkey nach ,vielleicht hat es auch damit etwas zu tun .


bye
 

Beiträge vom vorherigen Thema anzeigen:   
     Pro-Linux Foren-Übersicht -> Software Alle Zeiten sind GMT + 1 Stunde
Seite 1 von 1

 
Gehen Sie zu:  

Powered by phpBB © phpBB Group
pro_linux Theme © 2004 by Mandaxy