ADSL setup

Linux pomoć Drajveri
1

imam osjecaj da niko nije primjetio ovaj post na bihnet adsl temi pa cu ponovo pitati ovdje:

eee vako…znam da je malo to sve drugacije…zapravo nalazim se u Austiriji…eh sad neznam kakav je ADSL kod nas i kako to fercera sve (ja koristim Cable)…pa me zanima jel se moze nekako putem ovog adsl-setup-a dodat nekako ovaj broj za biranje koji mi daju…

naime vamo dobijes neki korisnicki broj (tj username)
onda password i neki broj koji treba birat svaki put kad se konektujes…nesto slicno ko kod dial up…

i sad u adsl-setup samo me pita za pass i username, a zaovaj broj nista…e to me buni jer na winu kad god hocu na net moram kliknut na connect. pa da on mene onda spoji pa tek onda furam…

pls malo mi pomozite!!

ps
a internet im je skuuuuuuuuup u p.m. recimo da za 20 € dobijes paket od 400 MB i brzinu 256/64 kbps…smece stari moj !

rip

2

Ama ne znam sta bi ti rekao… Koliko ja znam nikakav dial-up ni u kakvoj kombinaciji ne postoji. Ono sto ima je vpi/vci parametri (8/35) kod Bihneta i HT-a, i eventualno naziv access koncentratora.

Daj ti nama malo vise informacija

3

da li si podesio svoj modem/router kako treba? (pogledaj malo uputstva sto su dosla s tim)…
vecina dsl konekcija se podesi jednom da se konfigurira u modemu i onda se kacis na internet kao na normalnu mrezu bez ikakvih pitanja ni o imenu/sifri niti kakvom broju…

4

Ja se k’o kroz maglu sjećam nećega oko nekog IDa koji se negdje ukuca, ali nije mi to trebalo jer se u BiH ne koristi.

5

vako …kao sto sam rekao…

na win-u imam konekciju preko koje se moram konektovat svaki put kad hocu na net…i tu upisem username, pass i broj na koji se konektujem…!!

a na linuxu mi vec prepozna modem i dodijeli mi ip i sve…i mogu pingat svoj IP …ali kad npr. ping www.google.com onda nista…

eh sad u adsl-setup sve napisem i DNS i username i pass…i kad idem adsl-start ono idu one tackice … i onda mi pise time out …

a de mi malo oko tog vpi/vci…dje je to kako radi itd???

6

a jel i ovo moguce da se desava?

http://www.linuxquestions.org/questions/showthread.php?s=&threadid=348860&highlight=adsl

7

[quote]a jel i ovo moguce da se desava?

http://www.linuxquestions.org/questions/showthread.php?s=&threadid=348860&highlight=adsl[/quote]

Ovo su obicno problemi sa krivim postavkama sa pppd demonom. Meni isto nije rpppoe radio iz prve dok nisam negdje ukljucio verbose rad i vidio da sam iskljucio podrsku za ppp u kernelu :oops:

Al moj je prijedlog haj daj screenshote sa windowsa kako kreiras konekciju, zivo me zanima jer se isto ne sjecam da na XP-u ima ikakav broj. Jel ima neki poseban softver za konekciju ili ode onaj windoze wizard ?

8

pazi…kad tek podesavam modem…ima neki cd sa njihovim softvare-om…ali on ti kreira konekciju onu obicnu na winu…to je radi automatizacije radi samo…e sad u ovom screenshotu se nevidi taj broj al me za njega pita kad to sve upisujem u tom “wizardu”…

evo slika: http://crypt.abshost.net/screen.jpg

9

heh…da nepovjerujes…greska u prevodjenju…naime neradi se niokakvom broju na koji se konektuje nego o nekom broju korisnika…

a evo slika setupa: http://crypt.abshost.net/setup.jpg

sto mrzim njemacki to nije normalno …

10

heheh benutzername je username :smiley:

ali ovaj kundennummer (iliti customer number) mi je nejasan i mislim da nije bitan za kreiranje konekcije (osim ako modem/router nije nesta posebno nastiman).

Vidi, s obzirom da mi ovo na windozama izgleda kao najobicnija pppoe konekcija (a tu nema nikakvih customer brojeva i dial up brojeva) ja bih ti savjetovao da pogledas /etc/ppp/options file koji sluzi za konfiguraciju pppd i da eventualno u njega upises debug u nekom redu pa da onda probas adsl-start.

11

aha…mislis da samo dodam liniju debug il?

12

moj /etc/ppp/options:

debug
passive
asyncmap 0
name “TVOJ_BENUTZERNAME :)”

13

evo pppoe-debug file

[code]---------------------------------------------

  • The following section contains information about your system
    Wed Aug 10 17:16:36 CEST 2005
    Output of uname -a
    Linux aon 2.4.31 #6 Sun Jun 5 19:04:47 PDT 2005 i686 unknown unknown GNU/Linux
  • The following section contains information about your network
  • interfaces. The one you chose for PPPoE should contain the words:
  • ‘UP’ and ‘RUNNING’. If it does not, you probably have an Ethernet
  • driver problem.
    Output of ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:E0:4C:A1:CF:CD
    inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
    UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:322 (322.0 b) TX bytes:650 (650.0 b)
    Interrupt:11 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

  • The following section contains information about kernel modules
  • If the module for your Ethernet card is ‘tulip’, you might
  • want to look for an updated version at http://www.scyld.com
    Output of lsmod
    Module Size Used by Not tainted
    snd-pcm-oss 36736 0 (unused)
    snd-mixer-oss 12376 0 [snd-pcm-oss]
    usb-storage 62432 0 (unused)
    ohci1394 23888 0 (unused)
    ieee1394 41636 0 [ohci1394]
    uhci 24284 0 (unused)
    ehci-hcd 17516 0 (unused)
    usbcore 59148 1 [usb-storage uhci ehci-hcd]
    snd-via82xx 13376 0 (unused)
    gameport 1420 0 [snd-via82xx]
    snd-ac97-codec 58556 0 [snd-via82xx]
    snd-pcm 54344 0 [snd-pcm-oss snd-via82xx snd-ac97-codec]
    snd-timer 13764 0 [snd-pcm]
    snd-mpu401-uart 3136 0 [snd-via82xx]
    snd-rawmidi 12480 0 [snd-mpu401-uart]
    snd-seq-device 3812 0 [snd-rawmidi]
    snd 32772 0 [snd-pcm-oss snd-mixer-oss snd-via82xx snd-ac97-codec snd-pcm snd-timer snd-mpu401-uart snd-rawmidi snd-seq-device]
    snd-page-alloc 4712 0 [snd-mixer-oss snd-via82xx snd-pcm snd-timer snd-rawmidi snd-seq-device snd]
    soundcore 3396 4 [snd]
    via-rhine 12336 1
    mii 2272 0 [via-rhine]
    crc32 2880 0 [via-rhine]
    ntfs 51232 1 (autoclean)
    ide-scsi 9392 0
  • The following section lists your routing table.
  • If you have an entry which starts with ‘0.0.0.0’, you probably
  • have defined a default route and gateway, and pppd will
  • not create a default route using your ISP. Try getting
  • rid of this route.
    Output of netstat -n -r
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt Iface
    10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    0.0.0.0 10.0.0.138 0.0.0.0 UG 0 0 0 eth0

Contents of /etc/resolv.conf

  • The following section lists DNS setup.
  • If you can browse by IP address, but not name, suspect
  • a DNS problem.
    nameserver 10.0.0.138
    search lan
  • The following section lists /etc/ppp/options.
  • You should have NOTHING in that file.
    Contents of /etc/ppp/options

/etc/ppp/options

$Id: options,v 1.4 1996/05/01 18:57:04 alvar Exp $

Originally created by Jim Knoble jmknoble@mercury.interpath.net

Modified for Debian by alvar Bray alvar@meiko.co.uk

Modified for PPP Server setup by Christoph Lameter clameter@debian.org

Modified for Slackware by Pat Volkerding volkerdi@slackware.com

Use the command egrep -v ‘#|^ *$’ /etc/ppp/options to quickly see what

options are active in this file.

Specify which DNS Servers the incoming Win95 or WinNT Connection should use

Two Servers can be remotely configured

dns-addr 192.168.1.1

dns-addr 192.168.1.2

Specify which WINS Servers the incoming connection Win95 or WinNT should use

wins-addr 192.168.1.50

wins-addr 192.168.1.51

Run the executable or shell command specified after pppd has

terminated the link. This script could, for example, issue commands

to the modem to cause it to hang up if hardware modem control signals

were not available.

#disconnect “chat – d+++dc OK ath0 OK”

async character map – 32-bit hex; each bit is a character

that needs to be escaped for pppd to receive it. 0x00000001

represents ‘x01’, and 0x80000000 represents ‘x1f’.

asyncmap 0

Require the peer to authenticate itself before allowing network

packets to be sent or received.

For a PPP Server with script based logins not using PAP or CHAP

you need to disable this setting.

#auth

Do not require the other end of the connection to authenticate itself.

This option is dangerous if pppd is setuid.

If you also have ethernet and are having problems getting PPP to connect

over a modem, try this option.

#noauth

Use hardware flow control (i.e. RTS/CTS) to control the flow of data

on the serial port.

crtscts

Use software flow control (i.e. XON/XOFF) to control the flow of data

on the serial port.

#xonxoff

Specifies that certain characters should be escaped on transmission

(regardless of whether the peer requests them to be escaped with its

async control character map). The characters to be escaped are

specified as a list of hex numbers separated by commas. Note that

almost any character can be specified for the escape option, unlike

the asyncmap option which only allows control characters to be

specified. The characters which may not be escaped are those with hex

values 0x20 - 0x3f or 0x5e.

#escape 11,13,ff

Don’t use the modem control lines.

#local

Specifies that pppd should use a UUCP-style lock on the serial device

to ensure exclusive access to the device.

lock

Use the modem control lines. On Ultrix, this option implies hardware

flow control, as for the crtscts option. (This option is not fully

implemented.)

modem

Set the MRU [Maximum Receive Unit] value to for negotiation. pppd

will ask the peer to send packets of no more than bytes. The

minimum MRU value is 128. The default MRU value is 1500. A value of

296 is recommended for slow links (40 bytes for TCP/IP header + 256

bytes of data).

#mru 542

Set the interface netmask to , a 32 bit netmask in “decimal dot”

notation (e.g. 255.255.255.0).

#netmask 255.255.255.0

Disables the default behaviour when no local IP address is specified,

which is to determine (if possible) the local IP address from the

hostname. With this option, the peer will have to supply the local IP

address during IPCP negotiation (unless it specified explicitly on the

command line or in an options file).

#noipdefault

Enables the “passive” option in the LCP. With this option, pppd will

attempt to initiate a connection; if no reply is received from the

peer, pppd will then just wait passively for a valid LCP packet from

the peer (instead of exiting, as it does without this option).

#passive

With this option, pppd will not transmit LCP packets to initiate a

connection until a valid LCP packet is received from the peer (as for

the “passive” option with old versions of pppd).

#silent

Don’t request or allow negotiation of any options for LCP and IPCP

(use default values).

#-all

Disable Address/Control compression negotiation (use default, i.e.

address/control field disabled).

#-ac

Disable asyncmap negotiation (use the default asyncmap, i.e. escape

all control characters).

#-am

Don’t fork to become a background process (otherwise pppd will do so

if a serial device is specified).

#-detach

Disable IP address negotiation (with this option, the remote IP

address must be specified with an option on the command line or in an

options file).

#-ip

Disable magic number negotiation. With this option, pppd cannot

detect a looped-back line.

#-mn

Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.

1500).

#-mru

Disable protocol field compression negotiation (use default, i.e.

protocol field compression disabled).

#-pc

Require the peer to authenticate itself using PAP.

#+pap

Don’t agree to authenticate using PAP.

#-pap

Require the peer to authenticate itself using CHAP [Cryptographic

Handshake Authentication Protocol] authentication.

#+chap

Don’t agree to authenticate using CHAP.

#-chap

Disable negotiation of Van Jacobson style IP header compression (use

default, i.e. no compression).

#-vj

Increase debugging level (same as -d). If this option is given, pppd

will log the contents of all control packets sent or received in a

readable form. The packets are logged through syslog with facility

daemon and level debug. This information can be directed to a file by

setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If

pppd is compiled with extra debugging enabled, it will log messages

using facility local2 instead of daemon).

#debug

Append the domain name to the local host name for authentication

purposes. For example, if gethostname() returns the name porsche,

but the fully qualified domain name is porsche.Quotron.COM, you would

use the domain option to set the domain name to Quotron.COM.

#domain

Enable debugging code in the kernel-level PPP driver. The argument n

is a number which is the sum of the following values: 1 to enable

general debug messages, 2 to request that the contents of received

packets be printed, and 4 to request that the contents of transmitted

packets be printed.

#kdebug n

Set the MTU [Maximum Transmit Unit] value to . Unless the peer

requests a smaller value via MRU negotiation, pppd will request that

the kernel networking code send data packets of no more than n bytes

through the PPP network interface.

#mtu

Enforce the use of the hostname as the name of the local system for

authentication purposes (overrides the name option).

#usehostname

Set the assumed name of the remote system for authentication purposes

to .

#remotename

Add an entry to this system’s ARP [Address Resolution Protocol]

table with the IP address of the peer and the Ethernet address of this

system.

proxyarp

Use the system password database for authenticating the peer using

PAP. Note: mgetty already provides this option. If this is specified

then dialin from users using a script under Linux to fire up ppp wont work.

login

If this option is given, pppd will send an LCP echo-request frame to

the peer every n seconds. Under Linux, the echo-request is sent when

no packets have been received from the peer for n seconds. Normally

the peer should respond to the echo-request by sending an echo-reply.

This option can be used with the lcp-echo-failure option to detect

that the peer is no longer connected.

lcp-echo-interval 30

If this option is given, pppd will presume the peer to be dead if n

LCP echo-requests are sent without receiving a valid LCP echo-reply.

If this happens, pppd will terminate the connection. Use of this

option requires a non-zero value for the lcp-echo-interval parameter.

This option can be used to enable pppd to terminate after the physical

connection has been broken (e.g., the modem has hung up) in

situations where no hardware modem control lines are available.

lcp-echo-failure 4

Set the LCP restart interval (retransmission timeout) to seconds

(default 3).

#lcp-restart

Set the maximum number of LCP terminate-request transmissions to

(default 3).

#lcp-max-terminate

Set the maximum number of LCP configure-request transmissions to

(default 10).

#lcp-max-configure

Set the maximum number of LCP configure-NAKs returned before starting

to send configure-Rejects instead to (default 10).

#lcp-max-failure

Set the IPCP restart interval (retransmission timeout) to

seconds (default 3).

#ipcp-restart

Set the maximum number of IPCP terminate-request transmissions to

(default 3).

#ipcp-max-terminate

Set the maximum number of IPCP configure-request transmissions to

(default 10).

#ipcp-max-configure

Set the maximum number of IPCP configure-NAKs returned before starting

to send configure-Rejects instead to (default 10).

#ipcp-max-failure

Set the PAP restart interval (retransmission timeout) to seconds

(default 3).

#pap-restart

Set the maximum number of PAP authenticate-request transmissions to

(default 10).

#pap-max-authreq

Set the CHAP restart interval (retransmission timeout for

challenges) to seconds (default 3).

#chap-restart

Set the maximum number of CHAP challenge transmissions to

(default 10).

#chap-max-challenge

If this option is given, pppd will rechallenge the peer every

seconds.

#chap-interval

With this option, pppd will accept the peer’s idea of our local IP

address, even if the local IP address was specified in an option.

#ipcp-accept-local

With this option, pppd will accept the peer’s idea of its (remote) IP

address, even if the remote IP address was specified in an option.

#ipcp-accept-remote

  • The following section identifies your Ethernet interface
  • and user name. Some ISP’s need ‘username’; others
  • need ‘username@isp.com’. Try both
    ETH=eth0; USER=0624121000
  • The following section shows the pppd command we will invoke
    pppd invocation
    /usr/bin/setsid /usr/sbin/pppd pty '/usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth0 -T 80 -U -m 1412 ’ noipdefault noauth default-asyncmap defaultroute hide-password nodetach mtu 1492 mru 1492 noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp user 0624121000 lcp-echo-interval 20 lcp-echo-failure 3 debug

using channel 1
Using interface ppp0
Connect: ppp0 <–> /dev/pts/0
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x474ad7b7>]
LCP: timeout sending Config-Requests
pppoe: Timeout waiting for PADO packets
Script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth0 -T 80 -U -m 1412 -D /tmp/pppoe-debug-2590/pppoe-debug.txt-0 finished (pid 2660), status = 0x1
Modem hangup
Connection terminated.

  • The following section is an extract from your log.
  • Look for error messages from pppd, such as
  • a lack of kernel support for PPP, authentication failure
  • etc.
    Extract from /var/log/messages
    Jul 26 16:20:27 aon pppd[2733]: pppd 2.4.2 started by root, uid 0
    Jul 26 16:20:27 aon pppd[2733]: Using interface ppp0
    Jul 26 16:20:27 aon pppd[2733]: Connect: ppp0 <–> /dev/pts/0
    Jul 26 16:20:58 aon pppd[2733]: Connection terminated.
    Jul 26 16:21:02 aon pppd[2733]: Exit.
    Jul 26 16:22:22 aon pppd[3062]: pppd 2.4.2 started by root, uid 0
    Jul 26 16:22:22 aon pppd[3062]: Using interface ppp0
    Jul 26 16:22:22 aon pppd[3062]: Connect: ppp0 <–> /dev/pts/0
    Jul 26 16:22:53 aon pppd[3062]: Connection terminated.
    Jul 26 16:22:57 aon pppd[3062]: Exit.
    Jul 26 16:24:28 aon pppd[3388]: pppd 2.4.2 started by root, uid 0
    Jul 26 16:24:28 aon pppd[3388]: Using interface ppp0
    Jul 26 16:24:28 aon pppd[3388]: Connect: ppp0 <–> /dev/pts/0
    Jul 26 16:24:59 aon pppd[3388]: Connection terminated.
    Jul 26 16:25:03 aon pppd[3388]: Exit.
    Jul 26 16:25:21 aon pppd[3615]: pppd 2.4.2 started by root, uid 0
    Jul 26 16:25:21 aon pppd[3615]: Using interface ppp0
    Jul 26 16:25:21 aon pppd[3615]: Connect: ppp0 <–> /dev/pts/0
    Jul 26 16:25:52 aon pppd[3615]: Connection terminated.
    Jul 26 16:25:56 aon pppd[3615]: Exit.
    Jul 26 16:59:01 aon pppd[4143]: pppd 2.4.2 started by root, uid 0
    Jul 26 16:59:02 aon pppd[4143]: Using interface ppp0
    Jul 26 16:59:02 aon pppd[4143]: Connect: ppp0 <–> /dev/pts/2
    Jul 26 16:59:33 aon pppd[4143]: Connection terminated.
    Jul 26 16:59:37 aon pppd[4143]: Exit.
    Jul 29 17:32:43 aon pppd[2608]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:32:43 aon pppd[2608]: Using interface ppp0
    Jul 29 17:32:43 aon pppd[2608]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:33:14 aon pppd[2608]: Connection terminated.
    Jul 29 17:33:18 aon pppd[2608]: Exit.
    Jul 29 17:46:20 aon pppd[2921]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:46:20 aon pppd[2921]: Using interface ppp0
    Jul 29 17:46:20 aon pppd[2921]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:46:51 aon pppd[2921]: Connection terminated.
    Jul 29 17:46:55 aon pppd[2921]: Exit.
    Jul 29 17:49:04 aon adsl-stop: Killing pppd
    Jul 29 17:49:09 aon pppd[3120]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:49:09 aon pppd[3120]: Using interface ppp0
    Jul 29 17:49:09 aon pppd[3120]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:49:20 aon adsl-stop: Killing pppd
    Jul 29 17:49:20 aon pppd[3120]: Terminating on signal 15.
    Jul 29 17:49:26 aon pppd[3120]: Connection terminated.
    Jul 29 17:49:44 aon pppd[3120]: Exit.
    Jul 29 17:51:24 aon pppd[3338]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:51:24 aon pppd[3338]: Using interface ppp0
    Jul 29 17:51:24 aon pppd[3338]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:51:55 aon pppd[3338]: Connection terminated.
    Jul 29 17:51:59 aon pppd[3338]: Exit.
    Jul 29 17:52:04 aon pppd[3361]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:52:04 aon pppd[3361]: Using interface ppp0
    Jul 29 17:52:04 aon pppd[3361]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:52:09 aon adsl-stop: Killing pppd
    Jul 29 17:52:09 aon pppd[3361]: Terminating on signal 15.
    Jul 29 17:52:15 aon pppd[3361]: Connection terminated.
    Jul 29 17:52:39 aon pppd[3361]: Exit.
    Jul 29 17:56:26 aon pppd[3435]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:56:26 aon pppd[3435]: Using interface ppp0
    Jul 29 17:56:26 aon pppd[3435]: Connect: ppp0 <–> /dev/pts/0
    Jul 29 17:56:57 aon pppd[3435]: Connection terminated.
    Jul 29 17:57:01 aon pppd[3435]: Exit.
    Jul 29 17:58:08 aon pppd[3666]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:58:08 aon pppd[3666]: Using interface ppp0
    Jul 29 17:58:08 aon pppd[3666]: local IP address 10.112.112.112
    Jul 29 17:58:08 aon pppd[3666]: remote IP address 10.112.112.113
    Jul 29 17:58:13 aon adsl-stop: Killing pppd
    Jul 29 17:58:13 aon pppd[3666]: Terminating on signal 15.
    Jul 29 17:58:13 aon pppd[3666]: Exit.
    Jul 29 17:58:17 aon pppd[3729]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:58:17 aon pppd[3729]: Using interface ppp0
    Jul 29 17:58:17 aon pppd[3729]: local IP address 10.112.112.112
    Jul 29 17:58:17 aon pppd[3729]: remote IP address 10.112.112.113
    Jul 29 17:59:25 aon adsl-stop: Killing pppd
    Jul 29 17:59:25 aon pppd[3729]: Terminating on signal 15.
    Jul 29 17:59:25 aon pppd[3729]: Exit.
    Jul 29 17:59:32 aon pppd[3789]: pppd 2.4.2 started by root, uid 0
    Jul 29 17:59:32 aon pppd[3789]: Using interface ppp0
    Jul 29 17:59:32 aon pppd[3789]: local IP address 10.112.112.112
    Jul 29 17:59:32 aon pppd[3789]: remote IP address 10.112.112.113
    Jul 29 18:00:02 aon adsl-stop: Killing pppd
    Jul 29 18:00:02 aon pppd[3789]: Terminating on signal 15.
    Jul 29 18:00:02 aon pppd[3789]: Exit.
    Aug 4 19:15:23 aon pppd[2766]: pppd 2.4.2 started by root, uid 0
    Aug 4 19:15:23 aon pppd[2766]: Using interface ppp0
    Aug 4 19:15:23 aon pppd[2766]: Connect: ppp0 <–> /dev/pts/0
    Aug 4 19:15:54 aon pppd[2766]: Connection terminated.
    Aug 4 19:15:58 aon pppd[2766]: Exit.
    Aug 5 01:07:53 aon pppd[3135]: pppd 2.4.2 started by root, uid 0
    Aug 5 01:07:53 aon pppd[3135]: Using interface ppp0
    Aug 5 01:07:53 aon pppd[3135]: Connect: ppp0 <–> /dev/pts/0
    Aug 5 01:08:06 aon pppd[3135]: Terminating on signal 2.
    Aug 6 13:05:34 aon pppd[2746]: pppd 2.4.2 started by root, uid 0
    Aug 6 13:05:34 aon pppd[2746]: Using interface ppp0
    Aug 6 13:05:34 aon pppd[2746]: Connect: ppp0 <–> /dev/pts/0
    Aug 6 13:06:05 aon pppd[2746]: Connection terminated.
    Aug 6 13:06:09 aon pppd[2746]: Exit.
    Aug 8 12:50:48 aon pppd[2679]: pppd 2.4.2 started by root, uid 0
    Aug 8 12:50:48 aon pppd[2679]: Using interface ppp0
    Aug 8 12:50:48 aon pppd[2679]: Connect: ppp0 <–> /dev/pts/0
    Aug 8 12:51:23 aon pppd[2679]: Modem hangup
    Aug 8 12:51:23 aon pppd[2679]: Connection terminated.
    Aug 8 12:51:23 aon pppd[2679]: Exit.
    Aug 10 17:16:37 aon pppd[2658]: pppd 2.4.2 started by root, uid 0
    Aug 10 17:16:37 aon pppd[2658]: Using interface ppp0
    Aug 10 17:16:37 aon pppd[2658]: Connect: ppp0 <–> /dev/pts/0
    Aug 10 17:17:12 aon pppd[2658]: Modem hangup
    Aug 10 17:17:12 aon pppd[2658]: Connection terminated.
    Aug 10 17:17:12 aon pppd[2658]: Exit.
    Wed Aug 10 17:17:12 CEST 2005
  • The following section is a dump of the packets
  • sent and received by rp-pppoe. If you don’t see
  • any output, it’s an Ethernet driver problem. If you only
  • see three PADI packets and nothing else, check your cables
  • and modem. Make sure the modem lights flash when you try
  • to connect. Check that your Ethernet card is in
  • half-duplex, 10Mb/s mode. If all else fails,
  • try using pppoe-sniff.
    rp-pppoe debugging dump
    rp-pppoe-3.5
    17:16:37.315 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
    SourceAddr 00:e0:4c:a1:cf:cd DestAddr ff:ff:ff:ff:ff:ff
    01 01 00 00 01 03 00 04 64 0a 00 00 …d…

17:16:42.307 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:e0:4c:a1:cf:cd DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 64 0a 00 00 …d…

17:16:52.307 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:e0:4c:a1:cf:cd DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 64 0a 00 00 …d…[/code]

14

O majko… :o

Sad stvarno nemam ideje…

Vidi koliko iz svega ovoga mogu skontat

  1. probaj sa mojim /etc/ppp/options

  2. Cini mi se sa eth0 mora biti UP ali NE SMIJE imati ip adresu.

  3. Rekao bih da imas Speedtouch 510. Ako sam u pravu zasto ga ne koristis kao router ?!

15

sad cu malo ispast “glup” … al nerazumijem se puno u mrezu i oko toga svega…

to kad kazes da ga koristim kao router…sta trebam da uradim da bi radio kao router?..google-o sam malo ali nisam bas nasao nista sto mi je objasnilo stvar…

16

  1. nadji upute od svog isp-a kako se konfigurise router/modem i prouci ih.

  2. idi na 10.0.0.138 -> easy setup i tamo umjesto bridged ethernet stavi pppoe i stavi svoj username/password i vpi/vci (valjda je 8/35 ali bogzna sta je).

ifconfig eth0 10.0.0.138 netmask 255.255.255.0
route add default gw 10.0.0.138
echo “nameserver 10.0.0.138” >> /etc/resolv.conf

  1. potrazi brate na guglu kako tvoj isp radi sa linuxom, mora nesta bit.
17

[quote]
3.
ifconfig eth0 10.0.0.138 netmask 255.255.255.0
route add default gw 10.0.0.138
echo “nameserver 10.0.0.138” >> /etc/resolv.conf

.[/quote]
Možeš li objasniti po kojoj logici se ovo upisuje ???

18

  1. jah…da ovaj ISP ima ista o tome nebi ja ni postavio pitanje ovdje na forumu!

  2. ovaj ISP jasno naglasio da “ne daje” podrsku za bilo koji OS osim za Windows.

19

Evo ovako:
I ja sam blizu (u Njemačkoj) i koristim DSL.
Već sam ga podešavao surno 30 x i uvijek idem istim putem:
Prvo podesim mrežnu sa ifconfig, tj. dodijelim joj jednu adresu iz privatnog područja npr:

ifconfig eth0 10.0.0.5 netmask 255.255.255.0 up
Defaultni Gateway ti nije potreban jer ga pppd automatski postavi.
Sada otvoriš YaSt i ideš na ADSL konfiguraciju. Tamo Staviš eth0 kao mrežni interface, staviš taj broj koji si dobio kao “Benutzername” i upišeš svoju lozinku tako da te ne pita svaki puta za nju kad se hoćeš konektovati. Sada zatvori YaST i probaj se konektovati.
Važno je da podesiš eth0 prije konekcije.

PS:
Ich kann nicht glauben das es in Österreich ISP-s gibt die dir keine unterstützung für Linux bieten. Sollte das der Fall sein, überlege ob du lieber einen besseren ISP nimmst. Billig ist offt mit Ärger verbunden. Hier in Deutschland findet man bei allen ISP-s Beschreibung für Linux. Außerdem behaupten die Österreicher immer besser, in allem, zu sein.

20

[quote][quote]
3.
ifconfig eth0 10.0.0.138 netmask 255.255.255.0
route add default gw 10.0.0.138
echo “nameserver 10.0.0.138” >> /etc/resolv.conf

.[/quote]
Možeš li objasniti po kojoj logici se ovo upisuje ???[/quote]
pa valjda iz gornjeg debug posta ?..?
vecina isp-a ima neku standardnu konfiguraciju i ova veoma lici na takvu…
http://linuxnewbies.editthispage.com/tips/20020219