Vlastni router - vypadava pripojeni na VDSL

[Návštěvník Veverak]

Zdravim,

 

v Pa. mi technik zapojil pripojeni na VDSL (Cetin technik at jsem korektni), a muj vlastni router TP-Link Archer VR2100 se uspesne pripojil na DSL a pry ted budu jen 24h cekat nez se to aktivuje a melo by to byt dobry. (Note: ten router podporuje 250Mbit a standard ktery vyzaduje Vodafone)

 

Od Soboty je to ve stavu ze po restartovani router uspesne na vaze DSL spojeni, ziska WAN IP adresu a veskere nastaveni (tj Gateway, DNS servery, etc etc etc) internet krasne funguje ale po kratke chvilce proste dojde k odpojeni a pripojeni do WAN prestane fungovat. (Celou dobu wifi na router samotny funguje krasne, bavim se ciste o WAN)

 

Nejakou dobu po tom co prestane fungovat router eventualne zahodi nastaveni ip adres/gateway pro WAN a jen hlasi ze se nemuze pripojit, jedine reseni ktere jsem zatim nasel je restartovani routeru, pak se kolecko opakuje -> ziska vse co ma, chvilku funguje a pak to vypadne.

 

Podarilo se mi z neho vytahnout cas logu ktera ukauzje co se deje, tj. od momentu kdy se mu podari pripojit po moment kdy jde videt ze z nejakeho duvodu je timeout. Casove znacky jsou bohuzel divny protoze router zsika spravny cas az po pripojeni 🙂

 

Otazka je: ma smysl volat a ikdyz mam vlastni router dokazou mi technici pomoct?

 

2016-01-01 01:01:29 [5] System: DSL Link Up us/ds 0/107872 kbps Type 64/65B PTM Annex B
2016-01-01 01:01:35 [6] PPP: sent [PADT session is 1]
2016-01-01 01:01:35 [6] PPP: sent [PADI Host-Uniq(0x0000053b)]
2016-01-01 01:01:35 [6] PPP: rcvd  [PADO PeerMac(20-e0-9c-32-5c-01)]
2016-01-01 01:01:35 [6] PPP: sent [PADR Host-Uniq(0x0000053b)]
2016-01-01 01:01:35 [6] PPP: rcvd  [PADS SessionID(0x0001)]
2016-01-01 01:01:35 [5] PPP: Connected to 20:e0:9c:32:5c:01 via interface nas8.848
2016-01-01 01:01:35 [6] PPP: Using interface ppp1
2016-01-01 01:01:35 [5] PPP: Connect: ppp1 <--> nas8.848
2016-01-01 01:01:35 [6] PPP: Terminating on signal 15
2016-01-01 01:01:35 [5] PPP: Connection terminated.
2016-01-01 01:01:35 [5] PPP: Release PPP unit success
2016-01-01 01:01:39 [6] PPP: sent [PADT session is 1]
2016-01-01 01:01:39 [6] PPP: sent [PADI Host-Uniq(0x00000584)]
2016-01-01 01:01:39 [6] PPP: rcvd  [PADO PeerMac(20-e0-9c-32-5c-01)]
2016-01-01 01:01:39 [6] PPP: sent [PADR Host-Uniq(0x00000584)]
2016-01-01 01:01:39 [6] PPP: rcvd  [PADS SessionID(0x0001)]
2016-01-01 01:01:39 [5] PPP: Connected to 20:e0:9c:32:5c:01 via interface nas8.848
2016-01-01 01:01:39 [6] PPP: Using interface ppp1
2016-01-01 01:01:39 [5] PPP: Connect: ppp1 <--> nas8.848
2016-01-01 01:01:43 [6] PPP: Remote message: Login ok
2016-01-01 01:01:43 [5] PPP: PAP authentication succeeded
2016-01-01 01:01:43 [5] PPP: peer from calling number 20:E0:9C:32:5C:01 authorized
2016-01-01 01:01:43 [5] PPP: local  IP address <<<REDACTED>>>
2016-01-01 01:01:43 [5] PPP: remote IP address 10.26.202.187
2016-01-01 01:01:43 [5] PPP: primary   DNS address 217.77.165.81
2016-01-01 01:01:43 [5] PPP: secondary DNS address 217.77.165.211
2021-09-19 08:42:44 [6] Httpd: DNS 217.77.165.211 resolve timeout for dns.msftncsi.com
2021-09-19 08:42:46 [6] Httpd: DNS 8.8.8.8 resolve timeout for dns.msftncsi.com
2021-09-19 08:46:26 [6] PPP: Terminating on signal 15
2021-09-19 08:46:26 [6] PPP: Connect time 7.8 minutes.
2021-09-19 08:46:26 [6] PPP: Sent 32059 bytes, received 19581 bytes.
2021-09-19 08:46:32 [5] PPP: Connection terminated.
2021-09-19 08:46:32 [5] PPP: Release PPP unit success
2021-09-19 08:46:32 [6] PPP: Terminating on signal 15
2021-09-19 08:46:32 [5] PPP: Modem hangup
2021-09-19 08:46:55 [6] PPP: sent [PADT session is 1]
2021-09-19 08:46:55 [6] PPP: sent [PADI Host-Uniq(0x0000090d)]
2021-09-19 08:47:00 [6] PPP: sent [PADI Host-Uniq(0x0000090d)]
2021-09-19 08:47:10 [6] PPP: sent [PADI Host-Uniq(0x0000090d)]
2021-09-19 08:47:30 [4] PPP: Timeout waiting for PADO packets
2021-09-19 08:47:30 [3] PPP: Unable to complete PPPoE Discovery

 

 

[Adolf.Shitler]

Obdobné problémy se popisují i zde, vč. toho, jak je vyřešit: https://telekomunikace.cz/d/34124-vdsl-modem/25

[Návštěvník Veverak]

Tak zmena:

 

aktualizoval jsem FW routeru na posledni build a .... zatim to funguje 🙂 kdyztak zkusim ohlasit kdyby nastal problem.