Re: D8500 Firmware Upgrade - no VDSL connection

kjrnz · ‎2018-04-22

I have been using the X8 for over a year with VDSL without any problems. I just upgraded the firmware to 1.0.3.39. Now i cant get the VDSL to hold its connection.

I can ping 8.8.8.8 for about 5 replies when i reboot the router, but then it drops the connection and nothing i can do can get it back (except a reboot to get 5 pings again)

Have reverted back to firmware 1.0.3.29, but still have the same issue, have factory reset the router but still the same issue.

Anything else i could try?

thanks

michaelkenward · ‎2018-04-23

Your subject says D8500 but the "footer" says R8500. Which are we talking about here?

@kjrnz wrote:

I can ping 8.8.8.8 for about 5 replies when i reboot the router,

That's an odd address. By default the modem router assigns itself 192.168.0.1.

It might help to tell people which Internet service provider you are on.

antinode · ‎2018-04-23

> Have reverted back to firmware 1.0.3.29, [...]

   Is that what it was before the update "to 1.0.3.39"?

> [...] have factory reset the router [...]

   Did you restore saved settings, or re-configure manually?

> Anything else i could try?

   Is there anything interesting in the router logs?

> I can ping 8.8.8.8 for about 5 replies [...]

> That's an odd address. By default the modem router assigns itself
> 192.168.0.1.

   Not really. "8.8.8.8" is an _even_ address. As a moment's research
would reveal, it's a Google address ("google-public-dns-a.google.com"),
and it's one memorable (outside-world) server address which can be
expected to respond to "ping". No one said that it had anything to do
with the router itself.

kjrnz · ‎2018-04-23

@antinode wrote:
> Have reverted back to firmware 1.0.3.29, [...]

   Is that what it was before the update "to 1.0.3.39"?

>>Correct, it was 1.0.3.29, upgraded to 1.0.3.39, thats when VDSL connection failed, rolled back to 1.0.3.29, still the same problem, upgraded to 1.0.3.36 same problem, and again to 1.0.3.39

> [...] have factory reset the router [...]

   Did you restore saved settings, or re-configure manually?

>>I tried both actually, no luck

> Anything else i could try?

   Is there anything interesting in the router logs?

>>Havent checked the logs, will do tonight, but from looking previously, they were pretty limited in what they logged

> I can ping 8.8.8.8 for about 5 replies [...]

> That's an odd address. By default the modem router assigns itself
> 192.168.0.1.

>> pinging 8.8.8.8 is a way of testing a connection to the internet, i was pinging 192.168.1.1 aswell which held pings the whole time, (goes without saying)

>>have borrowed a test VDSL router, so will find out if something has happened to the line or not

   Not really. "8.8.8.8" is an _even_ address. As a moment's research
would reveal, it's a Google address ("google-public-dns-a.google.com"),
and it's one memorable (outside-world) server address which can be
expected to respond to "ping". No one said that it had anything to do
with the router itself.

coolness787 · ‎2018-05-23

If you can try and get a refund i've gone through five of them last one only lasted 8 hours

none but the last one could hold a stable internet connection except the wifi died then started boot looping pure garbage

coolness787 · ‎2018-05-23

@kjrnz wrote:

@antinode wrote:

> Have reverted back to firmware 1.0.3.29, [...]

   Is that what it was before the update "to 1.0.3.39"?

>>Correct, it was 1.0.3.29, upgraded to 1.0.3.39, thats when VDSL connection failed, rolled back to 1.0.3.29, still the same problem, upgraded to 1.0.3.36 same problem, and again to 1.0.3.39

> [...] have factory reset the router [...]

   Did you restore saved settings, or re-configure manually?

>>I tried both actually, no luck

> Anything else i could try?

   Is there anything interesting in the router logs?

>>Havent checked the logs, will do tonight, but from looking previously, they were pretty limited in what they logged

> I can ping 8.8.8.8 for about 5 replies [...]

> That's an odd address. By default the modem router assigns itself
> 192.168.0.1.

>> pinging 8.8.8.8 is a way of testing a connection to the internet, i was pinging 192.168.1.1 aswell which held pings the whole time, (goes without saying)

>>have borrowed a test VDSL router, so will find out if something has happened to the line or not

   Not really. "8.8.8.8" is an _even_ address. As a moment's research
would reveal, it's a Google address ("google-public-dns-a.google.com"),
and it's one memorable (outside-world) server address which can be
expected to respond to "ping". No one said that it had anything to do
with the router itself.

If you can try and get a refund i've gone through five of them last one only lasted 8 hours

none but the last one could hold a stable internet connection except the wifi died then started boot looping pure garbage