"Your Miraclebox Premium Twin has no internet access" after upgrade to 5.0.029

[HardyDK]

Those IPs can change at any time. The IP of the DNS server cannot. Also this is a TCP handshake not UDP. So not sure why you are mentioning being a DNS. And if you have deliberately configured to block this IP I can't see how you feel this is an OpenViX error. It's like blocking the feeds IP and then moaning you can't reach the feeds.

I don't know how the internet test works but I seem to have the same problem, i.e. I get the "your box has no internet access" although the connection is fine. I have just tried the latest image but had to revert to my previous image (4.x).

I have a static route for 8.8.8.8 and 8.8.4.4 because I use smart DNS with a Chromecast, which is hardwired to google's DNS servers. I have not experienced any other problems with this static routing but it seems to prevent the new image from working properly.

[leithh]

I have the same problem on my Vu+ Duo2 since updating to version >5.0.27 about 2 month ago and want to voice my arguments here.

What I have understood is that you are now making some kind of network check.
And I can see that my firewall is blocking the access to ip 8.8.8.8 port 53.
This is in my overall network configuration correct and intended and I will not change that.

Because I have setup my own linux firewall server and on that server BIND9 is running as caching only nameserver for the local network.
So this server is the only machine allowed to connect to port 53 to specific dns servers in the internet.
All machines behind my firewall server inside the local network - that's also my 2 Vu+ Duo2s - are NOT allowed to connect to dns-port 53 to the internet.
I have this setup for 12 yrs now and had never problems with any software / hardware / system.
And from a security point of view I find it a reasonable setup.

So can't you implement your internet check in another way?

[abu baniaz]

So can't you implement your internet check in another way?

Please suggest an alternative.

[leithh]

Please suggest an alternative.

Maybe a connection to port 80 (http) or 443 (https)? Any ip will do. These ports are normally open for outgoing traffic on any firewall - even self-configured ones.

Why did you choose a nslookup thru google's nameservers? Why not just do a "normal" nslookup thru the nameserver that is configured in the box's network setup?