On Fri, 3 Mar 2006, Laurentiu Coica wrote:
On 3/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Incearca sa te uiti cu tcpdump cit mai verbose pe interfata aia. Ca poate
mai afli ceva nou.
In timp ce in /var/log/messages am:
Mar 3 23:29:37 server kernel: device nas0 entered promiscuous mode
Mar 3 23:29:45 server kernel: device nas0 left promiscuous mode
Mar 3 23:30:05 server pppd[20677]: pppd 2.4.2 started by root, uid 0
Mar 3 23:30:05 server pppoe[20680]: Changed pty line discipline to
N_HDLC for synchronous mode
Mar 3 23:30:05 server pppd[20677]: Using interface ppp0
Mar 3 23:30:05 server pppd[20677]: Connect: ppp0 <--> /dev/pts/7
Mar 3 23:30:10 server kernel: device nas0 entered promiscuous mode
Mar 3 23:30:36 server pppd[20677]: LCP: timeout sending Config-Requests
Mar 3 23:30:36 server pppd[20677]: Connection terminated.
Mar 3 23:30:40 server pppoe[20680]: Timeout waiting for PADO packets
Mar 3 23:30:40 server pppd[20677]: Exit.
Mar 3 23:33:25 server kernel: device nas0 left promiscuous mode
cu tcp dump mai vad si:
# tcpdump -vi nas0
tcpdump: listening on nas0, link-type EN10MB (Ethernet), capture size 96 bytes
23:30:10.951309 PPPoE PADI [Service-Name] [Host-Uniq 0xC8500000]
Hm. Aici linga service name ar trebui parca sa apara numele serviciului.
Tu ce ai folosit ca sa-ti setezi conexiunea pppoe ?
cu rp-pppoe vine un adsl-setup care ar trebui rulat inainte de a incerca
sa te conectezi si care-ti face mai tot.
Afaik pppoe are nevoie de service name ca sa se poata conecta altfel te
chinui degeaba.
DIn cite am vazut eu faza cu "LCP: timeout sending config requests" o face
in 2 cazuri:
1. Providerul isi doarme somnul de veci
2. Cind service name-ul din pachetele PADI nu coincide cu ala din
pachetele PADO si pppoe le ignora pe astea din urma.
--
"frate, trezeste-te, aici nu-i razboiul stelelor"
Radu R. pe offtopic at lug.ro
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
