Thema "Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U" in Störungen im DSL-Netz

PPP / PADO problemen mit DSL + Asus DSL-AX82U

Erja — Wed, 15 Nov 2023 11:27:36 GMT

Hallo,

ich habe problem mit meiner DSL-Verbindung.

Habe Router Asus DSL-AX82U (mit Modem funktion) und es gibt kein Internetverbindung mit meinem Benutzername und Kennwort, aber ob ich nicht korrekt Kennwort benutze, ich habe diese ''frei 60 Minuten'' und Internet werkt (so Problem ist nicht mit Router oder Kabel).

Hier sind logs von meinem Router:

May 5 07:53:49 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:53:49 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:53:49 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:53:49 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:53:49 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:53:49 pppd[4169]: CHAP authentication succeeded
May 5 07:53:49 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:53:52 pppd[4169]: Connection terminated.
May 5 07:53:53 acsd: eth5: selected_chspec is 1003 (3)
May 5 07:53:53 acsd: eth5: Adjusted channel spec: 0x1003 (3)
May 5 07:53:53 acsd: eth5: selected channel spec: 0x1003 (3)
May 5 07:53:53 acsd: eth5: txop channel select: Performing CSA on chspec 0x1003
May 5 07:53:59 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:09 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:09 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:09 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:09 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:54:09 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:54:09 pppd[4169]: CHAP authentication succeeded
May 5 07:54:09 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:54:12 pppd[4169]: Connection terminated.
May 5 07:54:19 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:29 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:29 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:29 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:29 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:54:29 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:54:29 pppd[4169]: CHAP authentication succeeded
May 5 07:54:29 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:54:32 pppd[4169]: Connection terminated.
May 5 07:54:39 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:49 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:54:49 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:49 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:54:49 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:54:49 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:54:49 pppd[4169]: CHAP authentication succeeded
May 5 07:54:49 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:54:52 pppd[4169]: Connection terminated.
May 5 07:54:59 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:09 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:09 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:09 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:09 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:55:09 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:55:09 pppd[4169]: CHAP authentication succeeded
May 5 07:55:09 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:55:12 pppd[4169]: Connection terminated.
May 5 07:55:19 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:29 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:29 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:29 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:29 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:55:29 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:55:29 pppd[4169]: CHAP authentication succeeded
May 5 07:55:29 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:55:32 pppd[4169]: Connection terminated.
May 5 07:55:39 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:49 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:55:49 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:49 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:55:49 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:55:49 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:55:49 pppd[4169]: CHAP authentication succeeded
May 5 07:55:49 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:55:52 pppd[4169]: Connection terminated.
May 5 07:55:59 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:09 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:09 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:09 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:09 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:56:09 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:56:09 pppd[4169]: CHAP authentication succeeded
May 5 07:56:09 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:56:12 pppd[4169]: Connection terminated.
May 5 07:56:19 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:29 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:29 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:29 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:29 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:56:29 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:56:29 pppd[4169]: CHAP authentication succeeded
May 5 07:56:29 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:56:32 pppd[4169]: Connection terminated.
May 5 07:56:39 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:49 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:56:49 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:49 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:56:49 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:56:49 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:56:49 pppd[4169]: CHAP authentication succeeded
May 5 07:56:49 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:56:52 pppd[4169]: Connection terminated.
May 5 07:56:59 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:57:09 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:57:09 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:57:09 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:57:09 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:57:09 pppd[4169]: Connect: ppp0 <--> wan0
May 5 07:57:09 pppd[4169]: CHAP authentication succeeded
May 5 07:57:09 pppd[4169]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
May 5 07:57:12 pppd[4169]: Connection terminated.
May 5 07:57:19 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:57:29 WAN Connection: trigger the PPP connection via 10.112.112.112
May 5 07:57:29 pppoe-relay[4165]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:57:29 pppoe-relay[4165]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
May 5 07:57:29 pppd[4169]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
May 5 07:57:29 pppd[4169]: Connect: ppp0 <--> wan0

Vielen Dank für Hilfe!

Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

RobertP — Wed, 15 Nov 2023 13:21:37 GMT

ich vermute dein Anschluss läuft auf DS Lite und das kann der Asus nicht

versuch mal dich über den Support auf Dual Stack umstellen zu lassen

https://forum.vodafone.de/t5/Vodafone-News/Dein-Kontakt-zu-Vodafone/m-p/1912292#M10954

bevorzugt FB oder X /Twitter)

Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Erja — Wed, 22 Nov 2023 21:50:32 GMT

Danke! Ich versuche es.

Ich habe auch gedacht, dass Problem ist mit Anschluss, aber es werk wenn ich schlechtes Login benutze. Aber wer weiß...

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

R4mona — Thu, 23 Nov 2023 10:29:25 GMT

Guten Morgen @Erja,

hat denn die Umstellung funktioniert? 🙂

Liebe Grüße
R4mona

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Erja — Thu, 23 Nov 2023 10:59:51 GMT

Hallo,

sie haben schon die Umstellung auf Dual-Stack gemacht? 🙂

Kann es nicht jetzt probieren (am spätens am Sonntag).

Freundliche Grüße

Erja

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

R4mona — Thu, 23 Nov 2023 11:01:48 GMT

Hi @Erja,

wir können die Umstellung hier leider nicht überprüfen, da wir keinen Zugriff auf Dein Kundenkonto haben. Meine Frage war auch eher, ob Du die Umstellung über einen der folgenden Kontaktkanäle beauftragt hast?

Liebe Grüße
R4mona

Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Erja — Fri, 01 Dec 2023 16:12:58 GMT

So, die Veränderung half mir, aber Verbindung gibt 1-2x pro Tage andere Fehler - und danach ich muss Router restarten.

Dec 1 17:02:24 DSL: Link down -> up
Dec 1 17:02:25 WAN Connection: WAN(0) link up.
Dec 1 17:02:25 rc_service: wanduck 1499:notify_rc restart_wan_if 0
Dec 1 17:02:29 pppd[13818]: pppd 2.4.7 started by jelena, uid 0
Dec 1 17:02:29 pppd[13818]: local IP address 10.64.64.64
Dec 1 17:02:29 pppd[13818]: remote IP address 10.112.112.112
Dec 1 17:02:30 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:02:30 pppoe-relay[13814]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
Dec 1 17:02:30 pppoe-relay[13814]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
Dec 1 17:02:30 pppd[13818]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
Dec 1 17:02:30 pppd[13818]: Connect: ppp0 <--> wan0
Dec 1 17:02:30 pppd[13818]: CHAP authentication succeeded
Dec 1 17:02:30 pppd[13818]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
Dec 1 17:02:30 pppd[13818]: Local IP address changed to 88.74.145.207
Dec 1 17:02:30 pppd[13818]: Remote IP address changed to 84.59.211.1
Dec 1 17:02:31 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:02:31 WAN Connection: Fail to connect with some issues.
Dec 1 17:02:31 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:02:32 wan: finish adding multi routes
Dec 1 17:02:32 miniupnpd[29234]: shutting down MiniUPnPd
Dec 1 17:02:32 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Dec 1 17:02:32 miniupnpd[13878]: HTTP listening on port 56998
Dec 1 17:02:32 miniupnpd[13878]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 1 17:02:32 kernel: [71352.003879] Archer TCP Pure ACK Enabled
Dec 1 17:02:32 rc_service: ip-up 13831:notify_rc stop_samba
Dec 1 17:02:32 rc_service: ip-up 13831:notify_rc start_samba
Dec 1 17:02:32 rc_service: waitting "stop_samba" via ip-up ...
Dec 1 17:02:32 Samba Server: smb daemon is stopped
Dec 1 17:02:36 WAN Connection: WAN was restored.
Dec 1 17:02:41 zcip client: configured 169.254.210.239
Dec 1 17:07:40 kernel: [71660.216539] Line 0: xDSL link down
Dec 1 17:07:40 kernel: [71660.220082] bcmxtmcfg:ulPhysPort[0] m_ulTrafficMonitorPort[0]
Dec 1 17:07:40 kernel: [71660.226081] bcmxtmcfg: XTM LinkInfo. P-0, S-DOWN(2), Service =PTM(2)
Dec 1 17:07:40 kernel: [71660.233326] bcmxtmrt: netif_carrier_off
Dec 1 17:07:40 kernel: [71660.239369] iudma txq 0 disable
Dec 1 17:07:40 kernel: [71660.242544] tx_disable context 0x1 from (0x1)
Dec 1 17:07:40 kernel: [71660.242681] XTM W1B 639811377
Dec 1 17:07:40 kernel: [71660.249727] XTM W1E 639811384
Dec 1 17:07:40 kernel: [71660.249942] bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Dec 1 17:07:40 kernel: [71660.249951] bcmxtmcfg: ChkSILI Port = 0, BondingPort = 4
Dec 1 17:07:40 kernel: [71660.249954] bcmxtmcfg: DSL link mode is 4
Dec 1 17:07:40 kernel: [71660.249955] DSL LinkMode 4
Dec 1 17:07:40 kernel: [71660.249964] bcmxtmcfg: ReconfSAR P-0, T-0
Dec 1 17:07:40 kernel: [71660.249997] bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Dec 1 17:07:40 kernel: [71660.249999] bcmxtmcfg: Bonding State is DATA_IDLE
Dec 1 17:07:40 kernel: [71660.250002] bcmxtmcfg: SID MODE SET to 12 BIT MODE
Dec 1 17:07:40 kernel: [71660.250007] bcmxtmcfg: ATM Bonding Mgmt Log Area = d273b5bc
Dec 1 17:07:40 kernel: [71660.250013] BcmXdslDiscardWanDev: lineId=0,bDevDown=0
Dec 1 17:07:40 kernel: [71660.258600] XTM RXQ[0]: Depth 512, Level 0, Writes 209627, Reads 209627, Discards 0, Writes+Discards 209627
Dec 1 17:07:40 kernel: [71660.270720] XTM RXQ[1]: Depth 512, Level 0, Writes 10, Reads 10, Discards 0, Writes+Discards 10
Dec 1 17:07:40 kernel: [71660.282306] XTM TXQ[0]: Depth 512, Level 0, Writes 441838, Reads 441838, Discards 0, Writes+Discards 441838
Dec 1 17:07:40 kernel: [71660.297630] XTM RCQ[0]: Depth 512, Level 0, Writes 4306865, Reads 4306865, Discards 0, Writes+Discards 4306865
Dec 1 17:07:40 kernel: [71660.312427] Archer XTM rx notify 0x1 (pending 0)
Dec 1 17:07:40 kernel: [71660.330876] xtm queue 0 forcely claim the untransmitted (0) buffers tx = 431
Dec 1 17:07:44 kernel: [71664.016115] Line 0: xDSL G.994 training
Dec 1 17:07:44 DSL: Link up -> down
Dec 1 17:07:46 WAN Connection: Fail to connect with some issues.
Dec 1 17:07:48 kernel: [71668.027122] Line 0: xDSL link down
Dec 1 17:07:51 WAN Connection: WAN(0) link down.
Dec 1 17:07:52 kernel: [71672.030115] Line 0: xDSL G.994 training
Dec 1 17:07:58 kernel: [71678.034112] Line 0: VDSL G.993 started
Dec 1 17:08:55 kernel: [71735.038120] Line 0: VDSL G.993 channel analysis
Dec 1 17:08:57 kernel: [71736.813121] Line 0: VDSL2 link up, Bearer 0, us=42440, ds=116798
Dec 1 17:08:57 kernel: [71736.819150] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Dec 1 17:08:57 kernel: [71736.824674] bcmxtmcfg: ULS Port 0
Dec 1 17:08:57 kernel: [71736.828099] bcmxtmcfg: XTM Link Mode is VDSL G.inpRtx
Dec 1 17:08:57 kernel: [71736.834433] bcmxtmcfg:ulPhysPort[0] m_ulTrafficMonitorPort[4]
Dec 1 17:08:57 kernel: [71736.840264] bcmxtmcfg: XTM LinkInfo. P-0, S-UP(1), Service =PTM(2)
Dec 1 17:08:57 kernel: [71736.846755] bcmxtmcfg: ReconfSAR P-0, T-2
Dec 1 17:08:57 kernel: [71736.850901] bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
Dec 1 17:08:57 kernel: [71736.856057] ===>ConfigurePtmQueueShaper: ShaperIdx=0 MinRate=0 ShapeRate=0 Mbs=0 MinRateMbs=0, SitUt=600 SitLoUT=19200pulGts[00000000] NON-CO4 DSLAM based operations for PTM CRC & ENET FCS.
Dec 1 17:08:57 kernel: [71736.873121] SetTxQueue for InfoSize 0 QueueIndex 0
Dec 1 17:08:57 kernel: [71736.877989] TXDMA drop alg 0 Lo minThresh 0 maxThresh 0 hi minThresh 0 maxThresh 0
Dec 1 17:08:57 kernel: [71736.885575] iudma txq 0 enable devId[0] txVcid[0] base_buff_status[000000f3]
Dec 1 17:08:57 kernel: [71736.892630] bcmxtmrt: netif_carrier_on
Dec 1 17:08:57 kernel: [71736.896514] bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=42440000, DS=116798000
Dec 1 17:08:57 kernel: [71736.904649] bcmxtmcfg: ChkSILI Port = 0, BondingPort = 4
Dec 1 17:08:57 kernel: [71736.910080] bcmxtmcfg: DSL link mode is 4
Dec 1 17:08:57 kernel: [71736.914103] DSL LinkMode 4
Dec 1 17:08:59 DSL: Link down -> up
Dec 1 17:09:01 WAN Connection: WAN(0) link up.
Dec 1 17:09:01 rc_service: wanduck 1499:notify_rc restart_wan_if 0
Dec 1 17:09:06 pppd[14790]: pppd 2.4.7 started by jelena, uid 0
Dec 1 17:09:06 pppd[14790]: local IP address 10.64.64.64
Dec 1 17:09:06 pppd[14790]: remote IP address 10.112.112.112
Dec 1 17:09:07 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:09:07 pppoe-relay[14786]: PADO packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
Dec 1 17:09:07 pppd[14790]: Connected to 40:7c:7d:db:2c:a9 via interface wan0
Dec 1 17:09:07 pppd[14790]: Connect: ppp0 <--> wan0
Dec 1 17:09:07 pppoe-relay[14786]: PADS packet from 40:7c:7d:db:2c:a9 on interface wan0 does not have Relay-Session-Id tag
Dec 1 17:09:07 pppd[14790]: CHAP authentication succeeded
Dec 1 17:09:07 pppd[14790]: peer from calling number 40:7C:7D:DB:2C:A9 authorized
Dec 1 17:09:07 pppd[14790]: Local IP address changed to 90.186.90.191
Dec 1 17:09:07 pppd[14790]: Remote IP address changed to 84.59.211.1
Dec 1 17:09:07 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:09:07 WAN Connection: Fail to connect with some issues.
Dec 1 17:09:07 WAN Connection: trigger the PPP connection via 10.112.112.112
Dec 1 17:09:08 wan: finish adding multi routes
Dec 1 17:09:08 miniupnpd[13878]: shutting down MiniUPnPd
Dec 1 17:09:08 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Dec 1 17:09:08 miniupnpd[14854]: HTTP listening on port 59605
Dec 1 17:09:09 miniupnpd[14854]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 1 17:09:09 kernel: [71748.650882] Archer TCP Pure ACK Enabled
Dec 1 17:09:09 rc_service: ip-up 14803:notify_rc stop_samba
Dec 1 17:09:09 rc_service: ip-up 14803:notify_rc start_samba
Dec 1 17:09:09 rc_service: waitting "stop_samba" via ip-up ...
Dec 1 17:09:09 Samba Server: smb daemon is stopped
Dec 1 17:09:12 WAN Connection: WAN was restored.
Dec 1 17:09:18 zcip client: configured 169.254.210.239

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Chr1ssy — Sat, 02 Dec 2023 20:49:02 GMT

Hi @Erja,

vielen Dank dafür,

Hast Du Dich denn nun nochmal bei uns über die anderen Kanäle gemeldet?

VG Chr1ssy

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Erja — Thu, 18 Jan 2024 12:28:47 GMT

Hallo, nein.

Und diese Problemen dauern immer weiter - 1-6x pro Tag.

In der andere Lokation router werkt gut, so Problem muss irgendwo beim Vodafone sein.

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

Jakobson — Wed, 31 Jul 2024 22:43:37 GMT

Hab selbes Problem. Oder zumindest hat es den Anschein. Habe Problem über Störung gemeldet aber das Ticket ist dazu nicht auffindbar trotz Nachfrage.
Nun fange ich wieder bei 0 an. Literally.

Bin erst seit einem Tag Kunde. Der setup hat so wunderbar mit der Telekom zuvor funktioniert (gleiche Bandbreite. Ebenfalls 35b, 250down/50up).

Mein Fehlerbild ist noch merkwürdiger. Selbst wenn WAN Up ist habe ich keine Verbindung ins WAN.

Zugangsdaten stimmen, das bestätigte der Support. Dennoch wird mir ein Fehler 651 angezeigt beim Verbindungsaufbau: User / Passwort falsch. Ergibt alles keinen Sinn.

Ich betreibe ebenfalls den ASUS ax82u.

Re: Betreff: PPP / PADO problemen mit DSL + Asus DSL-AX82U

RobertP — Thu, 01 Aug 2024 07:32:35 GMT

@Jakobson schrieb:
Zugangsdaten stimmen, das bestätigte der Support. Dennoch wird mir ein Fehler 651 angezeigt beim Verbindungsaufbau: User / Passwort falsch.

dein Anschluss läuft auf DS Lite und das kann der Asus nicht

lass dich über den Support auf Dual Stack umstellen
https://forum.vodafone.de/t5/Vodafone-News/Dein-Kontakt-zu-Vodafone/m-p/1912292#M10954
(bevorzugt über FB oder SMS Kontakt aufnehmen)