Hi all,
Sorry for writing in English, I can read and understand Flemish without any issues but proper writing is bit difficult, especially when I plan to write long story like this
Few weeks ago i got the letter from Belgacom that equipment in my street has been upgraded and that I can come to take free BBox3 in order to enjoy faster speed. At that moment I had 50/6 profile on my BBox2 and I used old FritzBox 7170 for my VoIP lines. FritzBox was set in network client mode, so bbox2 was handling both VDSL and PPPoE, and that worked without any issues for several years. So I took free bb3 and from the moment I connected it, issues started...
I immediately noticed that speed was increased to ~70mbit/sec, but
1) my VoiP phones stopped working and
2) Belgacom TV stopped working and
3) DSL connection was quite unstable, couple of times per hour lights on bb3 were blinking and DSL connection was getting up and down.
I connected bbox2 again and everything started working normally, but from that moment bbox2 was syncing at repair profile speed (4/0.5) which was kind of expected. I called Belgacom several time and after 3-4 days of line checking and explanations to different operators what is going on, they decided to send someone onsite to check. Some friendly guy arrived to my place next time, and in front of him modem started blinking and he immediately said i got bad modem and he replaced it with another copy. In 10 minutes my TV was working again, internet was up and I did not check VoIP, thinking that new modem would fix that as well. He left, and I changed ethernet IP address on Bbox 3 to the range 192.168.178.x to match the rest of my network, and as soon as I did it, Belgacom TV stopped working and I again got message "no signal" or streaming stopped after 3 sec on each channel!
Conclusion 1 - BBox 3 has problems is Ethernet IP is changed from the default value and Belgacom TV does not work in that case.
I changed IP of bbox3 to default value, reconfigured the rest of my devices to that range and TV started to work again... I thought, ok, no big issue. Then I checked my VoIP phones, and surprise - FritzBox could not log in to the Sip servers when it was behind BBox 3. I found then couple of articles on this forum that bbox3 is breaking SIP protocol, and I confirm that here
Conclusion 2 - SIP clients behind BBox 3 are not work due to the packed mangling done by Bbox3, resulting in resetting SIP connection
Next what I tried is to set FritzBox to act as PPPoE client behind BBox3, but it also miserably failed as i got PPPoE timeouts, and after 1-2 hours of retries FritzBox was able to establish PPPoE session. During the night, after midnight for example, Fritz was able to establish PPPoE session instantly, and later I found few posts on this forum explaining exactly the same problem, with the conclusion that something is wrong on Belgacom PPPoE servers side, probably some sort of saturation was creating PPPoE timeouts.
Tired of everything, i ordered FritzBox 7490 hoping that it would solve the issue and I cashed out 275 EUR for international version. But, unfortunately, PPPoE was still giving timeouts even FB was acting as VDSL2 modem and PPPoE client, and also I had some nasty hostid mismatch errors. I found later on the forum that Belgacom and AVM are accusing each other for this errors, and basically there is no solution.
At that point I was so pissed off and furious, I called Belgacom and fighted with those poor L1 support ladies, and they told me there are still issues on my line and they sent someone onsite for the second time. This guy listened to issues I had, he confirmed BBox3 will not support VoIP client and on the phone with someone in central they changed my VDSL profile back to be able to work with BBox2. I got 30 Mbit speed (although I had 50 before), but my new expensive FritzBox could establish now SIP sessions. In PPPoE mode (with bbox2 as modem), I still had PPPoE timeouts all day long. Technician told me that I have to live with 30mbit speed for 96 days and that automatic line manager will then automatically increased speed back to 50 mbit, and that I should not connect bbox3 or FB to DSL line directly as that would turn vectoring on again and I will have same issues.
Just out of curiosity, two days ago I tried to configure FB to establish PPPoE session behind BBox2, and on my surprise, now it works each time! No timeout messages since then. I also tried PPPoE from my PC, and that one also worked instantly and it still works (and before my PC also could not establish PPPoE link, it took many many retries before I could connect). I have feeling that they changed or fixed something on Belgacom PPPoE side so the timeouts are gone. Now I am tempted to connect BBox 3/FB back to DSL line, turn on vectoring and get back 70 mbit/sec speed back...
After this long introduction, here is my question - is anyone aware that PPPoE timeout problem has been fixed by Belgacom? Would it be smart (or stupid) to try to turn on vectoring back by connecting bbox3, because if PPPoE timeouts start to appear again, I would be back to repair profile with BBox 2 and then I would again need to fight with belgacom front line...?
Thanks all for your opinions
Vectoring + FritzBox 7490 + PPPoE problem
- Splitter
- Elite Poster
- Berichten: 4578
- Lid geworden op: 10 maa 2010, 12:30
- Uitgedeelde bedankjes: 58 keer
- Bedankt: 446 keer
over here, no vectoring, fritzbox 7390, i also have the pppoe timeouts and hostunique errors.
been happening a few months now, and it slows down the reconnect (before, it reconnected within a minute, now it's about 5 minutes of timeouts before it reconnects)
the ROP is not yet vectoring capable (ikanos chipset) so i doubt it has anything to do with the rop's or vectoring itself.
and, afaik, the problem has not been "solved" because just today my FB reconnected with the same delay and errors.
interestingly, today after reconnecting, it also gave me a few dns lookup errors (using belgacom dns servers) after having reconnected.
so, something is up, but i have no clue what exactly, and if your setup is currently working flawlessly, i'd leave it as-is.
been happening a few months now, and it slows down the reconnect (before, it reconnected within a minute, now it's about 5 minutes of timeouts before it reconnects)
the ROP is not yet vectoring capable (ikanos chipset) so i doubt it has anything to do with the rop's or vectoring itself.
and, afaik, the problem has not been "solved" because just today my FB reconnected with the same delay and errors.
interestingly, today after reconnecting, it also gave me a few dns lookup errors (using belgacom dns servers) after having reconnected.
so, something is up, but i have no clue what exactly, and if your setup is currently working flawlessly, i'd leave it as-is.
-
- Elite Poster
- Berichten: 1104
- Lid geworden op: 23 nov 2005, 17:11
- Uitgedeelde bedankjes: 54 keer
- Bedankt: 99 keer
Hi,
I still have the infamous PPPoE issues today, unfortunately...
01.10.14 00:57:01 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:48 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:34 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:20 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:06 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:52 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:38 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:24 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:10 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:54:56 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:54:43 PPPoE-Fehler: Zeitüberschreitung.
...
so be careful
I still have the infamous PPPoE issues today, unfortunately...
01.10.14 00:57:01 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:48 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:34 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:20 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:56:06 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:52 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:38 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:24 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:55:10 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:54:56 PPPoE-Fehler: Zeitüberschreitung.
01.10.14 00:54:43 PPPoE-Fehler: Zeitüberschreitung.
...
so be careful
-
- Moderator
- Berichten: 16487
- Lid geworden op: 28 apr 2008, 11:22
- Locatie: Waregem
- Uitgedeelde bedankjes: 820 keer
- Bedankt: 2998 keer
Maybe just a coincidence, but the PPPoE time-out issue seems to be resolved by using @PROXIMUS in your DSL logon name.
http://userbase.be/forum/viewtopic.php? ... 60#p569998
http://userbase.be/forum/viewtopic.php? ... 60#p569998
VoIP: WeePee (vaste nummers geporteerd), Sipgate.de, Sipgate.co.uk, MegaVoip (uitgaand België).
Provider: Proximus Start (60/4 mbps down/up).
Modem/Router: Fritz!Box 7590 int, OS 07.39-97058 BETA, profiel 100/35.
Telefoon centrale: Euracom 181 achter FritzBox So.
TV: Telenet CI+, Fritz!DVB-C.
Provider: Proximus Start (60/4 mbps down/up).
Modem/Router: Fritz!Box 7590 int, OS 07.39-97058 BETA, profiel 100/35.
Telefoon centrale: Euracom 181 achter FritzBox So.
TV: Telenet CI+, Fritz!DVB-C.
- Splitter
- Elite Poster
- Berichten: 4578
- Lid geworden op: 10 maa 2010, 12:30
- Uitgedeelde bedankjes: 58 keer
- Bedankt: 446 keer
doesn't seem a coincidence, here as well perfect and fast binding after changing to proximus realm:
just this night:
guess they made an error somewhere when implementing the proximus real a while back, giving errors on the skynet realm?
Code: Selecteer alles
01.10.14 21:55:26 Internet connection established successfully. IP address: 109.<snip>, DNS server: 195.238.2.22 and 195.238.2.21, Gateway: 109.128.48.1, Broadband PoP: MSR03BKC7-H104L4512L00KK
01.10.14 21:55:19 Internet connection cleared.
Code: Selecteer alles
01.10.14 03:37:26 Dynamic DNS error: Error during DNS resolution of the domain name
01.10.14 03:36:10 Dynamic DNS error: Error during DNS resolution of the domain name
01.10.14 03:34:55 Internet connection established successfully. IP address: 109.<snip>, DNS server: 195.238.2.22 and 195.238.2.21, Gateway: 109.128.0.1, Broadband PoP: MSR03BKC7-H104L4512L00KK
01.10.14 03:34:39 PPPoE error: Timeout.
01.10.14 03:34:26 PPPoE error: Timeout.
01.10.14 03:34:12 PPPoE error: Timeout.
01.10.14 03:33:59 PPPoE error: Timeout.
01.10.14 03:33:45 PPPoE error: Timeout.
01.10.14 03:33:31 PPPoE error: Timeout.
01.10.14 03:33:17 PPPoE error: Timeout.
01.10.14 03:33:03 PPPoE error: Timeout.
01.10.14 03:32:50 PPPoE error: Timeout.
01.10.14 03:32:36 PPPoE error: Timeout.
01.10.14 03:32:22 PPPoE error: Timeout.
01.10.14 03:32:09 PPPoE error: Timeout.
01.10.14 03:31:55 Timeout during PPP negotiation.
01.10.14 03:31:55 Internet connection cleared.
i could not resist temptation. bb3 connected, i got repair profile 7/0.5... called belgacom, uhm, proximus, and guy on the phone did reset my line. After 10 min, bb3 synced at 70/6. I connected FB and got this:
[img]vdsl.jpg[/img]
Bit risky, but finally bboxes are going in the closet on the bottom shelf . Interesting is that my Fritz!Box 7490 has FW 6.04 (so not the one that is Belg..Proximus approved, 6.06)
[img]vdsl.jpg[/img]
Bit risky, but finally bboxes are going in the closet on the bottom shelf . Interesting is that my Fritz!Box 7490 has FW 6.04 (so not the one that is Belg..Proximus approved, 6.06)
I was celebrating too early.... After couple of hours, DSL live went down, Fritz Box could not sync. I put back Bbox 3 and I am back to repair profile...
Honestly, I am fed up with this. I will move to cable most likely
Honestly, I am fed up with this. I will move to cable most likely