TheBad
05-05-2005, 21:54
Ciao a tutti, ho letto un po' di post sull'abbinamento d-link g604t e adsl di libero, ma continuo a non saltarci fuori. Ora cercherò di fare una descrizione quanto più approfondita possibile della mia situazione, sperando che qualcuno riesca almeno a darmi una dritta almeno per circoscrivere il problema.
il router vede la portante (il led 'adsl' è sempre acceso, status lampeggia, lan1 è sempre acceso) ma non c'è verso di farlo connettere.
Il router è connesso al pc tramite cavo ethernet
Non prende l'indirizzo ip dal provider, infatti nello status della
connessione leggo sempre:
LAN
MAC address 00:0f:3d:b0:a6:3f
ip address 192.168.1.1
Subnet mask 255.255.255.0
DHCP server running
WAN
Description Type IP State
Connection1 pppoa N/A Disconnected
e premendo il tasto 'connect' che vi è accanto non accade nulla.
La connessione è configurata come segue:
protocollo pppoA
alla voce Protocollo: PPPoATM
Encapsulation: VC
VPI: 8
VCI: 35
come da specifiche libero
ho inserito username e password
nella finestra 'Status Information' ho:
System uptime 4 hour(s) 47 minute(s)
DSL status connected
DSL speed 320 kbps upstream, 800 kbps downstream
LAN IP address 192.168.1.1
Ethernet connected
DHCP server running
in DSL Status leggo:
Connection Status Connected
Upstream rate(kbps) 320
Downstream rate(kbps)800
US Margin 30
DS Margin 17
Modulation GDMT
LOS Errors 21
DS Line attenuation 57
US Line attenuation 42
Path mode interleaved
ho anche configurato i dns di libero.
Ho avuto modo di notare che ogni tanto, ma solo per pochi istanti, assume un ip del tipo 10.x.x.x che però credo essere di rete privata, quindi non vedo cosa c'entri.
Veniamo anche al discorso filtri:
in casa ho due prese del telefono, una all'ingresso, che chiameremo A, e una in camera, che chiameremo B.
su b ho la presa tripolare al muro alla quale ho collegato un filtro col cavetto adsl che entra dall'alto, e in cascata a questo ho inserito la presa del telefono. Sulla presa B ho la presa tripolare attaccata al muro, dalla quale fuoriesce un cavetto che va in un filtro adsl. In questo filtro ci sono due ulteriori prese, una col disegnino di una cornetta e una con scritto adsl. sulla cornetta ho collegato il cavo del telefono su quella adsl non cìè nulla.
Se la spia ADSL del router è accesa fissa ma provo a effettuare una chiamata dal telefono sulla presa B, questa comincia a lampeggiare, e già questo è strano.
Ho provato a staccare tutto dalla presa A, quindi a non collegare nulla, e se faccio così il telefono collegato sulla presa B non dà segni di vita.
Inoltre, ripeto, non riesco a connettermi neppure quando c'è il led adsl accesso fisso.
Vi allego anche un estratto del log:
May 5 22:27:54> pppd 2.4.1 started by root, uid 0
May 5 22:27:54> connect(8.35): Device or resource busy
May 5 22:27:54> System Call Error
May 5 22:27:54> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
per finire, in questo momento, in cui sono collegato alla presa B col modem 56k, il led adsl lampeggia e il log recita così:
May 5 22:28:26> DSL Carrier is down
May 5 22:28:36> DSL Carrier is training
May 5 22:29:18> Timeout on response: flan:settings//block
May 5 22:29:56> DSL Carrier is down
May 5 22:30:16> DSL Carrier is training
May 5 22:30:26> DSL Carrier is down
May 5 22:30:46> DSL Carrier is training
May 5 22:31:16> DSL Carrier is down
May 5 22:31:26> DSL Carrier is training
May 5 22:32:06> DSL Carrier is down
May 5 22:32:26> DSL Carrier is training
May 5 22:33:36> DSL Carrier is down
May 5 22:33:56> DSL Carrier is training
May 5 22:35:06> DSL Carrier is down
May 5 22:35:16> DSL Carrier is training
May 5 22:36:46> DSL Carrier is down
May 5 22:36:56> DSL Carrier is training
May 5 22:37:36> DSL Carrier is training
May 5 22:37:46> DSL Carrier is training
May 5 22:38:06> DSL Carrier is down
May 5 22:38:16> DSL Carrier is training
May 5 22:39:46> DSL Carrier is down
May 5 22:39:56> DSL Carrier is training
May 5 22:40:06> DSL Carrier is training
May 5 22:40:16> DSL Carrier is down
May 5 22:40:36> DSL Carrier is training
May 5 22:40:56> DSL Carrier is training
May 5 22:41:06> DSL Carrier is training
May 5 22:41:36> DSL Carrier is training
May 5 22:41:46> DSL Carrier is training
May 5 22:43:16> DSL Carrier is down
May 5 22:43:36> DSL Carrier is training
May 5 22:43:56> DSL Carrier is down
Ho cercato di dirvi tutto, ottenere risposta dal 155 o dal numero wind mi sembra impossibile, ormai ho perso il conto di quante volte ci abbia provato.
Grazie per le eventuali risposte.
il router vede la portante (il led 'adsl' è sempre acceso, status lampeggia, lan1 è sempre acceso) ma non c'è verso di farlo connettere.
Il router è connesso al pc tramite cavo ethernet
Non prende l'indirizzo ip dal provider, infatti nello status della
connessione leggo sempre:
LAN
MAC address 00:0f:3d:b0:a6:3f
ip address 192.168.1.1
Subnet mask 255.255.255.0
DHCP server running
WAN
Description Type IP State
Connection1 pppoa N/A Disconnected
e premendo il tasto 'connect' che vi è accanto non accade nulla.
La connessione è configurata come segue:
protocollo pppoA
alla voce Protocollo: PPPoATM
Encapsulation: VC
VPI: 8
VCI: 35
come da specifiche libero
ho inserito username e password
nella finestra 'Status Information' ho:
System uptime 4 hour(s) 47 minute(s)
DSL status connected
DSL speed 320 kbps upstream, 800 kbps downstream
LAN IP address 192.168.1.1
Ethernet connected
DHCP server running
in DSL Status leggo:
Connection Status Connected
Upstream rate(kbps) 320
Downstream rate(kbps)800
US Margin 30
DS Margin 17
Modulation GDMT
LOS Errors 21
DS Line attenuation 57
US Line attenuation 42
Path mode interleaved
ho anche configurato i dns di libero.
Ho avuto modo di notare che ogni tanto, ma solo per pochi istanti, assume un ip del tipo 10.x.x.x che però credo essere di rete privata, quindi non vedo cosa c'entri.
Veniamo anche al discorso filtri:
in casa ho due prese del telefono, una all'ingresso, che chiameremo A, e una in camera, che chiameremo B.
su b ho la presa tripolare al muro alla quale ho collegato un filtro col cavetto adsl che entra dall'alto, e in cascata a questo ho inserito la presa del telefono. Sulla presa B ho la presa tripolare attaccata al muro, dalla quale fuoriesce un cavetto che va in un filtro adsl. In questo filtro ci sono due ulteriori prese, una col disegnino di una cornetta e una con scritto adsl. sulla cornetta ho collegato il cavo del telefono su quella adsl non cìè nulla.
Se la spia ADSL del router è accesa fissa ma provo a effettuare una chiamata dal telefono sulla presa B, questa comincia a lampeggiare, e già questo è strano.
Ho provato a staccare tutto dalla presa A, quindi a non collegare nulla, e se faccio così il telefono collegato sulla presa B non dà segni di vita.
Inoltre, ripeto, non riesco a connettermi neppure quando c'è il led adsl accesso fisso.
Vi allego anche un estratto del log:
May 5 22:27:54> pppd 2.4.1 started by root, uid 0
May 5 22:27:54> connect(8.35): Device or resource busy
May 5 22:27:54> System Call Error
May 5 22:27:54> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:55> pppd 2.4.1 started by root, uid 0
May 5 22:27:55> connect(8.35): Device or resource busy
May 5 22:27:55> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:56> pppd 2.4.1 started by root, uid 0
May 5 22:27:56> connect(8.35): Device or resource busy
May 5 22:27:56> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
May 5 22:27:57> pppd 2.4.1 started by root, uid 0
May 5 22:27:57> connect(8.35): Device or resource busy
May 5 22:27:57> System Call Error
per finire, in questo momento, in cui sono collegato alla presa B col modem 56k, il led adsl lampeggia e il log recita così:
May 5 22:28:26> DSL Carrier is down
May 5 22:28:36> DSL Carrier is training
May 5 22:29:18> Timeout on response: flan:settings//block
May 5 22:29:56> DSL Carrier is down
May 5 22:30:16> DSL Carrier is training
May 5 22:30:26> DSL Carrier is down
May 5 22:30:46> DSL Carrier is training
May 5 22:31:16> DSL Carrier is down
May 5 22:31:26> DSL Carrier is training
May 5 22:32:06> DSL Carrier is down
May 5 22:32:26> DSL Carrier is training
May 5 22:33:36> DSL Carrier is down
May 5 22:33:56> DSL Carrier is training
May 5 22:35:06> DSL Carrier is down
May 5 22:35:16> DSL Carrier is training
May 5 22:36:46> DSL Carrier is down
May 5 22:36:56> DSL Carrier is training
May 5 22:37:36> DSL Carrier is training
May 5 22:37:46> DSL Carrier is training
May 5 22:38:06> DSL Carrier is down
May 5 22:38:16> DSL Carrier is training
May 5 22:39:46> DSL Carrier is down
May 5 22:39:56> DSL Carrier is training
May 5 22:40:06> DSL Carrier is training
May 5 22:40:16> DSL Carrier is down
May 5 22:40:36> DSL Carrier is training
May 5 22:40:56> DSL Carrier is training
May 5 22:41:06> DSL Carrier is training
May 5 22:41:36> DSL Carrier is training
May 5 22:41:46> DSL Carrier is training
May 5 22:43:16> DSL Carrier is down
May 5 22:43:36> DSL Carrier is training
May 5 22:43:56> DSL Carrier is down
Ho cercato di dirvi tutto, ottenere risposta dal 155 o dal numero wind mi sembra impossibile, ormai ho perso il conto di quante volte ci abbia provato.
Grazie per le eventuali risposte.