320T morto dopo Tiupgrade

  • 15 Risposte
  • 7272 Visite

0 Utenti e 1 Visitatore stanno visualizzando questo topic.

Offline darkmater

  • Nuovo Iscritto
  • *
  • 18
Re: 320T morto dopo Tiupgrade
« Risposta #15 il: 23 Settembre 2008, 19:48 »
.. chiedo scusa.. il log sopra e del 300t con fw 7.05. Cmq avevo gli stessi problemi con il 320T.
Questo Ŕ il logádel 320 (fw 7.05) (per il momento ness disconnessione ma ieri ne ho avute parecchie..)

Janá 1 12:00:09 cfgmgr(sar):á Could not get oam_ping_interval from boot loader envá
Janá 1 12:00:09 cfgmgr(sar):á Trying to retreive the value from Configurationá
Janá 1 12:00:09 cfgmgr(sar): oamPingInterval(20)(20)
Janá 1 12:00:09 cfgmgr(pppoa-107): Valid Configuration Tree
Janá 1 12:00:10 cfgmgr(resolver): stat successfull for /etc/resolv.conf.
Janá 1 12:00:10 cfgmgr(resolver): Resolver Polling Timer Started succesfully.
Janá 1 12:00:10 cfgmgr(sar): DSL Polling Timer Started succesfully.
Janá 1 12:00:11 cfgmgr(fdb): Firewall NAT service started
Janá 1 12:00:11 cfgmgr(lanbridge0): Bridge Created: br0
Janá 1 12:00:13 cfgmgr(lanbridge1): Bridge Created: br1
Janá 1 12:00:14 cfgmgr(lanbridge0): Bridge Interface Added: eth0
Janá 1 12:00:20 cfgmgr(sar): DSL Carrier is up
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.35)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.32)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.40)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.36)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.38)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_default oamPing(0.96)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_search oamPing(0.35)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_search oamPing(8.35)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_search oamPing(0.43)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_search oamPing(0.51)result(2)
Janá 1 12:00:20 cfgmgr(sar): auto_vcc_search oamPing(0.59)result(2)
Janá 1 12:00:21 cfgmgr(sar): auto_vcc_search oamPing(8.43)result(2)
Janá 1 12:00:21 cfgmgr(sar): auto_vcc_search oamPing(8.51)result(2)
Janá 1 12:00:21 cfgmgr(sar): auto_vcc_search oamPing(8.59)result(2)
Janá 1 12:00:21 cfgmgr(pppoa-107): ---}}} Start of connection delayed for 44 sec
Janá 1 12:00:21 cfgmgr(pppoa-107): PPPoA launch delay.
Janá 1 12:01:05 cfgmgr(pppoa-107): PPPoA Launch after conn delay timeout ...
Janá 1 12:01:05 pppd[176]: pppd 2.4.4 started by root, uid 0
Janá 1 12:01:05 pppd[176]: Connect: ppp0 {--}á
Janá 1 12:01:06 pppd[176]: CHAP authentication succeeded
Janá 1 12:01:06 pppd[176]: localá IP address 151.65.56.61
Janá 1 12:01:06 pppd[176]: remote IP address 151.23.227.37
Janá 1 12:01:06 pppd[176]: primaryá áDNS address 193.70.152.15
Janá 1 12:01:06 pppd[176]: secondary DNS address 193.70.152.25
Janá 1 12:01:06 cfgmgr(pppoa-107): PPPoA Connect with IP Address 151.65.56.61á
Janá 1 12:01:07 cfgmgr(pppoa-107): PPPoA Connection Successfully Establishedá
Janá 1 12:01:07 cfgmgr(pppoa-107): PPPoA Connect with Gateway IP Address: 151.23.227.37á
Janá 1 12:01:08 syslog: dproxy force reload config.
Janá 1 12:01:16 cfgmgr(pppoa-107): PPPD Successfully Startedá
Janá 1 12:02:07 cfgmgr(logic): UDP connections reset...
Janá 1 12:02:17 cfgmgr(logic): UDP connections flush...

Quel "connection delayed for..." non l'ho mai visto... e lo fa sempre ogni volta che l'accendo e quando perde il segnale...
« Ultima modifica: 23 Settembre 2008, 19:50 da darkmater »