usb modem kurulumunda Timed out hatası

Başlatan npolat, 13 Ağustos 2008 - 20:59:26

« önceki - sonraki »

0 Üyeler ve 1 Ziyaretçi konuyu incelemekte.

npolat

usb modem kurulumunu aşağıdaki linkte anlatıldığı gibi yaptım
http://forum.ubuntu-tr.net/index.php?topic=39.0

......TIMED OUT  diyor bağlanmıyor

pppoe-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe)
master@ubuntu:~/rp-pppoe-3.8$ sudo pppoe-start
................TIMED OUT

burdaki sorunu nasıl aşabilirim


master@ubuntu:~/rp-pppoe-3.8$ sudo ./go
Running ./configure...
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ranlib... ranlib
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/dlpi.h usability... no
checking sys/dlpi.h presence... no
checking for sys/dlpi.h... no
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking net/if_arp.h usability... yes
checking net/if_arp.h presence... yes
checking for net/if_arp.h... yes
checking netinet/if_ether.h usability... yes
checking netinet/if_ether.h presence... yes
checking for netinet/if_ether.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking sys/uio.h usability... yes
checking sys/uio.h presence... yes
checking for sys/uio.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for fcntl.h... (cached) yes
checking net/bpf.h usability... no
checking net/bpf.h presence... no
checking for net/bpf.h... no
checking netpacket/packet.h usability... yes
checking netpacket/packet.h presence... yes
checking for netpacket/packet.h... yes
checking net/ethernet.h usability... yes
checking net/ethernet.h presence... yes
checking for net/ethernet.h... yes
checking asm/types.h usability... yes
checking asm/types.h presence... yes
checking for asm/types.h... yes
checking linux/if_packet.h usability... yes
checking linux/if_packet.h presence... yes
checking for linux/if_packet.h... yes
checking linux/if_ether.h usability... yes
checking linux/if_ether.h presence... yes
checking for linux/if_ether.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/cdefs.h usability... yes
checking sys/cdefs.h presence... yes
checking for sys/cdefs.h... yes
checking net/if.h usability... yes
checking net/if.h presence... yes
checking for net/if.h... yes
checking net/if_dl.h usability... no
checking net/if_dl.h presence... no
checking for net/if_dl.h... no
checking net/if_ether.h usability... no
checking net/if_ether.h presence... no
checking for net/if_ether.h... no
checking net/if_types.h usability... no
checking net/if_types.h presence... no
checking for net/if_types.h... no
checking for netinet/if_ether.h... (cached) yes
checking for net/if_types.h... (cached) no
checking for net/if_dl.h... (cached) no
checking for linux/if.h... yes
checking for linux/if_pppox.h... no
checking for an ANSI C-conforming const... yes
checking for pid_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct sockaddr_ll... yes
checking for N_HDLC line discipline... no
checking for working memcmp... yes
checking for function prototypes... yes
checking whether setvbuf arguments are reversed... no
checking return type of signal handlers... void
checking for select... yes
checking for socket... yes
checking for strerror... yes
checking for strtol... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for unsigned short... yes
checking size of unsigned short... 2
checking for unsigned int... yes
checking size of unsigned int... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking for pppd... /usr/sbin/pppd
checking for echo... /bin/echo
checking for setsid... /usr/bin/setsid
checking for id... /usr/bin/id
checking for Linux 2.4.X kernel-mode PPPoE support... no
checking packing order of bit fields... reversed
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libevent/Makefile
config.status: creating ../scripts/pppoe-connect
config.status: creating ../scripts/pppoe-start
config.status: creating ../scripts/pppoe-stop
config.status: creating ../scripts/pppoe-init
config.status: creating ../scripts/pppoe-init-suse
config.status: creating ../scripts/pppoe-init-turbolinux
config.status: creating ../scripts/pppoe-setup
config.status: creating ../gui/Makefile
config.status: creating ../gui/tkpppoe
config.status: creating config.h
config.status: config.h is unchanged
On this platform, the following targets will be built:
pppoe pppoe-server pppoe-sniff pppoe-relay
Type 'make' to compile the software.
Running make...

Type 'make install' as root to install the software.
Running make install...

Type 'make install' as root to install the software.
mkdir -p /usr/sbin
/usr/bin/install -c -m 755 pppoe /usr/sbin
/usr/bin/install -c -m 755 pppoe-server /usr/sbin
if test -x licensed-only/pppoe-server-control ; then /usr/bin/install -c -m 755 licensed-only/pppoe-server-control /usr/sbin; fi
if test -x pppoe-relay ; then /usr/bin/install -c -m 755 pppoe-relay /usr/sbin; fi
if test -x pppoe-sniff; then /usr/bin/install -c -m 755 pppoe-sniff /usr/sbin; fi
/usr/bin/install -c -m 755 ../scripts/pppoe-connect /usr/sbin
/usr/bin/install -c -m 755 ../scripts/pppoe-start /usr/sbin
/usr/bin/install -c -m 755 ../scripts/pppoe-status /usr/sbin
/usr/bin/install -c -m 755 ../scripts/pppoe-stop /usr/sbin
/usr/bin/install -c -m 755 ../scripts/pppoe-setup /usr/sbin
mkdir -p /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../doc/CHANGES /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../doc/KERNEL-MODE-PPPOE /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../doc/HOW-TO-CONNECT /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../doc/LICENSE /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../README /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../SERVPOET /usr/share/doc/rp-pppoe-3.8
/usr/bin/install -c -m 644 ../configs/pap-secrets /usr/share/doc/rp-pppoe-3.8
mkdir -p /usr/man/man8
for i in pppoe pppoe-server pppoe-sniff pppoe-relay ; do \
      if test -f ../man/$i.8 ; then \
         /usr/bin/install -c -m 644 ../man/$i.8 /usr/man/man8 || exit 1; \
      fi; \
   done
/usr/bin/install -c -m 644 ../man/pppoe-start.8 /usr/man/man8
/usr/bin/install -c -m 644 ../man/pppoe-stop.8 /usr/man/man8
/usr/bin/install -c -m 644 ../man/pppoe-status.8 /usr/man/man8
/usr/bin/install -c -m 644 ../man/pppoe-connect.8 /usr/man/man8
/usr/bin/install -c -m 644 ../man/pppoe-setup.8 /usr/man/man8
mkdir -p /usr/man/man5
/usr/bin/install -c -m 644 ../man/pppoe.conf.5 /usr/man/man5
mkdir -p /etc/ppp
mkdir -p /etc/ppp/plugins
echo "# Directory created by rp-pppoe for kernel-mode plugin" > /etc/ppp/plugins/README
NOT overwriting existing /etc/ppp/pppoe.conf
NOT overwriting existing /etc/ppp/firewall-standalone
NOT overwriting existing /etc/ppp/firewall-masq
NOT overwriting existing /etc/ppp/pppoe-server-options
# L2TP

Type 'pppoe-setup' to configure the software.




























Welcome to the Roaring Penguin PPPoE client setup.  First, I will run
some checks on your system to make sure the PPPoE client is installed
properly...

Looks good!  Now, please enter some information:

USER NAME

>>> Enter your PPPoE user name (default vahit0719@ttnet): vahit0719@ttnet

INTERFACE

>>> Enter the Ethernet interface connected to the DSL modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethn, where 'n' is a number.
(default eth0): nas0

Do you want the link to come up on demand, or stay up continuously?
If you want it to come up on demand, enter the idle time in seconds
after which the link should be dropped.  If you want the link to
stay up permanently, enter 'no' (two letters, lower-case.)
NOTE: Demand-activated links do not interact well with dynamic IP
addresses.  You may have some problems with demand-activated links.
>>> Enter the demand value (default no):

DNS

Please enter the IP address of your ISP's primary DNS server.
If your ISP claims that 'the server will provide DNS addresses',
enter 'server' (all lower-case) here.
If you just press enter, I will assume you know what you are
doing and not modify your DNS setup.
>>> Enter the DNS information here: server

PASSWORD

>>> Please enter your PPPoE password:   
>>> Please re-enter your PPPoE password:

FIREWALLING

Please choose the firewall rules to use.  Note that these rules are
very basic.  You are strongly encouraged to use a more sophisticated
firewall setup; however, these will provide basic security.  If you
are running any servers on your machine, you must choose 'NONE' and
set up firewalling yourself.  Otherwise, the firewall rules will deny
access to all standard servers like Web, e-mail, ftp, etc.  If you
are using SSH, the rules will block outgoing SSH connections which
allocate a privileged source port.

The firewall choices are:
0 - NONE: This script will not set any firewall rules.  You are responsible
          for ensuring the security of your machine.  You are STRONGLY
          recommended to use some kind of firewall rules.
1 - STANDALONE: Appropriate for a basic stand-alone web-surfing workstation
2 - MASQUERADE: Appropriate for a machine acting as an Internet gateway
                for a LAN
>>> Choose a type of firewall (0-2): 0

** Summary of what you entered **

Ethernet Interface: nas0
User name:          mhan1234@ttnet
Activate-on-demand: No
DNS addresses:      Supplied by ISP's server
Firewalling:        NONE

>>> Accept these settings and adjust configuration files (y/n)? y
Adjusting /etc/ppp/pppoe.conf
Adjusting /etc/ppp/pap-secrets and /etc/ppp/chap-secrets
  (But first backing it up to /etc/ppp/pap-secrets-bak)
  (But first backing it up to /etc/ppp/chap-secrets-bak)



Congratulations, it should be all set up!

Type 'pppoe-start' to bring up your PPPoE link and 'pppoe-stop' to bring
it down.  Type 'pppoe-status' to see the link status.
master@ubuntu:~/rp-pppoe-3.8$ pppoe-status
pppoe-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe)
master@ubuntu:~/rp-pppoe-3.8$ sudo pppoe-start
................TIMED OUT
master@ubuntu:~/rp-pppoe-3.8$

heartsmagic

Genelde bu timed out hatası , eksik yapılandırmadan kaynaklanıyor. Tüm adımları bir daha gözden geçirmeni tavsiye ederim. Eğer eksiksizse ne yazık ki benden pas.
Hayattan çıkarı olmayanların, ölümden de çıkarı olmayacaktır.
Hayatlarıyla yanlış olanların ölümleriyle doğru olmalarına imkân var mıdır?


Böylece yalan, dünyanın düzenine dönüştürülüyor.

npolat

can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe

var/run/ aldında pppoe.conf diye bir dosya yok ayrıca yukarıda verdiğim

çıktıda no olarak belirtilenler eksik olanlarmı

atomkarinca

#3
Alıntı yapılan: npolat - 13 Ağustos 2008 - 22:50:57
can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe

pppoe kapatmak istemiş.Ama zaten başlamamış durumdaymış önemli değil bu satır. Bence @heartsmagic'in söyledikleri önemli ona göre davranmak gerekir. Yol olarakda; nerde hata var yolunu izlemeyin sizin durumunuzda herşeyi sıfırdan dikkatle tekrar yapmak gerekebilir.

npolat

can't read PID file /var/run/pppoe.conf-pppoe.pid.pppoe diyor

ben var / run altında pppoe.conf diye bir dosya göremedim

can't read read yani var/run altında pppoe.conf.pid.pppoe den pidleri okuyamıyor anlamına gelmezmi

atomkarinca


Linux

#6
br2684ctl paketini yüklediniz mi ? bir çok kullanıcı bunu yüklemeyi unutuyor, brtcl yüklenmedigi zamanda, timed out hatası ile karşılaşılıyor.

caadas

#7
Konuyu hortlattığımın farkındayım ama birebir aynı sorunla karşı karşıyayım. Tüm adımları eksiksiz yaptım. br2684ctl paketini de indirip yükledim. Kurulum sırasında hiç hata vermediği için Ubuntu cd'sine gerek kalmadı. Ancak bende de timed out hatası veriyor. Aynen arkadaşın dediği gibi,
can't read PID file /var/run/pppoe.conf-pppoe.pid.pppoe
gibi bir hata çıkıyor.

Modemim Speedcom 4 port ethernet + usb bağlantılı. Ubuntu 9.4 kullanıcısıyım. Modemi ayrıca tanıtmaya gerek var mı bilmiyorum. Ben direk usb'yi taktım, buradaki yönergeleri izledim, sonuç başarısız oldu. Yardımcı olur musunuz?

Khan

Ubuntu'nun modeminizi tanımadığına emin misiniz?
Nitekim, Ethernet girişi olan her modemi USB'den de tanıyor.

caadas

Tanıyıp tanımadığını bilmiyorum ki...
forumda gözüme çarpan lsusb koduna ait çıktı şöyle:
cagdas@cagdas:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 007: ID 0572:cb01 Conexant Systems (Rockwell), Inc. GeekADSL Promax Q31 ADSL Modem
Bus 002 Device 006: ID 0ac8:303b Z-Star Microelectronics Corp. ZC0303 WebCam
Bus 002 Device 005: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 004: ID 046d:ca03 Logitech, Inc. MOMO Racing
Bus 002 Device 003: ID 0079:0006 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Sanki tanınmış gibi görünüyor ama emin olamadım.

Khan

Tanınmış değil de sistem, aygıtı görmüş sadece.
Benim bir başlığım vardı.

http://forum.ubuntu-tr.net/index.php?topic=9175.0

Ayrıca yönetici arkadaşlar bu konuyu "Conexant Modem Tanıtımı" gibi bir şekilde sabitlerlerse sevinirim.

caadas

Bence sabitlenmesin, ortada çözülmüş bir mesele yok.