Beantwoord

IPv4 connection issues that assigns bad gateway automatically

  • 11 april 2020
  • 8 reacties
  • 128 keer bekeken

Hello all,

Sorry for English post since my Dutch is not good to communicate at this level.

Ever since I got my Ziggo as my ISP, I have this problem that most of the time when my devices connect to internet, either via Wi-Fi or ethernet, they were able to connect only to IPv6 sites (Google, YouTube, Facebook, Instagram, etc.) where as they were not able to connect IPv4 sites (basically every other site).

Since this happened not all the time (around 80% of the times), I checked what caused this and found out that when I can connect properly, my devices get IPv4 Default Gateway of 192.168.178.1 and a corresponding IPv4 address of 192.168.178.xx. This seems reasonable since ıp address of my modem is 192.168.178.1.

When my devices cannot connect to IPv4, my devices are assigned IPv4 Default Gateway of 192.168.192.1 and a corresponding IPv4 address of 192.168.192.xx. I do not know why my devices are assigned this IP and this happens very often.

A solution that I found which worked for me till now is bypassing this by assigning every device that I have with manual IPv4 addresses of  192.168.178.xx. This did not solved the problem but at least I was able to bypass the issue.

Now with Covid19 measures, I need to work from home and I cannot have the admin rights to manually assign IPv4 address to my company laptop. This results in plugging in and out of ethernet cable in the hopes that next time I will be assigned a correct IP. This can take up to an hour and really exhausting and frustrating.

Today I tried to ask help from Ziggo Chat, which resulted in the finding of no problem on connection and resetting the modem to factory settings. This did not solve my issues (I already tried this before).

After the factory reset, I get some screenshots to show the problem.

I thank you for all the help.

Best regards,

Mert
 

icon

Best beantwoord door efok 11 april 2020, 14:39

The IP range 192.168.192.x belongs to the horizon mediabox XL. Just disconnect it from your network.

Bekijk origineel

Dit topic is gesloten. Staat je antwoord hier niet bij, stel dan je vraag in een nieuw topic.

8 Reacties

Reputatie 7
Badge +9

Hello,
 

This is a public Ziggo forum, where Ziggo customers try to help each other. Also, Ziggo moderators ( they have “_Ziggo” behind their name ) visit every topic every so often. Compared to the helpdesk, they have more knowledge, options, rights and can look 'deeper' into the Ziggo system.

Put your zip code and house number in your Ziggo profiel ( these are only visible to Ziggo moderators ), so that they can view your settings and data.


Because you have 2 IP ranges, it looks like there are 2 DHCP servers. If these are not configured correctly, you will have problems like these.
The first modem/router wil be the Ziggo one.  This one sends the right IP-range/Gateway/… settings and then a device can connect to the internet.
The other DHCP will sends its one IP-range settings and devices ‘connected’ to this DHCP will not be able to connect to the internet, because the IP-range/Gateway/… settings are false.

 Please describe your netwerk.

The IP range 192.168.192.x belongs to the horizon mediabox XL. Just disconnect it from your network.

The IP range 192.168.192.x belongs to the horizon mediabox XL. Just disconnect it from your network.

Just unplugged the ethernet cable from mediabox XL. 

I think this may have fixed the problem, so far the devices that i tried got ip’s in 192.168.178.xx range.

I will now try with all my devices.

 Should I not connect Mediabox anyway to my network? This seems like a little bit of oversight.

The Mediabox XL has its own DHCP server active in his own modem in a different IP range and it has no connection to the internet.
In addition, the connection with the modem causes connection problems to in the Mediabox XL with replay, on-demand, apps and the guide due to a bug in the software that mixes up all connections.
The Mediabox XL has its own IP connection through his own modem for these functions of the Mediabox XL through the coax cabel.

Reputatie 7
Badge +9

...Should I not connect Mediabox anyway to my network? This seems like a little bit of oversight.

No, leave it disconnected from your network.

The IP range 192.168.192.x belongs to the horizon mediabox XL. Just disconnect it from your network.

Just unplugged the ethernet cable from mediabox XL. 

I think this may have fixed the problem, so far the devices that i tried got ip’s in 192.168.178.xx range.

I will now try with all my devices.

 Should I not connect Mediabox anyway to my network? This seems like a little bit of oversight.

You can connect it if you want, but it it behaves really weird in your network. You must turn the built in DHCP off. In my case it works, however I think it’s booting slower then when it’s not connected. If you don’t need the webinterface of the mediabox just leave it disconnected.

And yes, you’re right, this is weird default behaviour. Ziggo promised to make a firmware remake of the device, but if this wil fix these things....We don’t know.

Thank you all for your answers and help :) wierdly enough this also improved my WiFi connection where i was able to get 40% of speed of ethernet, now it is 90%.

“And yes, you’re right, this is weird default behaviour. Ziggo promised to make a firmware remake of the device, but if this wil fix these things....We don’t know.”

This will never be repaired, because the Mediabox XL will later have the same look and feel and functions as the Next, except 4K.

https://www.ziggo.nl/televisie/mediaboxen/mediabox-next/#mediabox-next