Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GreenBay42]

Try setting a static route. Let us know if this works.

Go in to your router Features > Static Route. Click Add Route.

Name: chromecast1 (or whatever)
Destination Network:  8.8.8.8
Mask:  255.255.255.255   or   255.255.255.252
Gateway: IP address of the router (192.168.0.1)
Metric: 1
Interface:  WAN

Save settings.

Repeat with 8.8.4.4, 208.67.222.222 and 209.244.0.3.

Flush the DNS on your computer --> https://techwiser.com/flush-dns-cache/

Try pinging 8.8.8.8. It should not return replies...hopefully

[cacatnow]

Actually I already tried using static route method before it came to asking for help here. There is a site stating that the if the interface is locked to WAN it will not work. Unfortunately this router can't set the interface to LAN.

[GreenBay42]

I tested this, seemed to work

Features > Firewall > IPv4

Select Turn IPv4 Filtering ON and DENY rules listed

Add Rule:

Name: CC1
Source IP Address Range:  LAN  (the IP address of your chromecast) or put the IP range of your LAN (e.g. 192.168.0.1-192.168.0.254). Putting in the router IP or 192.168.0.255 will not work
Destination IP Address Range:  WAN   8.8.8.8
Protocol & Port Range: ANY
Schedule: Always Enable

Click APPLY and then click Save.

Create 3 more rules with 8.8.4.4, 208.67.222.222 and 209.244.0.3.

[cacatnow]

Did you reboot the router? I did a quick test (a bit busy atm) without rebooting it (no prompt to reboot after saving either) did not work. What am I supposed to put into the port range? It does not let me leave it empty. I did put 53 as thats the usual port for DNS query but it did not work. CC is still using Google DNS

[GreenBay42]

Put nothing in the port box. Click the drop-down where it says TCP and select ANY.  If you not have that option, enter 1-65535

You may not get prompted to reboot. Mine didn't and it worked. After you click Save, the button should be grayed-out unless you make a change. I am using a different model router though but has same GUI.

I will see if a tech has an 850L rev B to test.

Also, you are blocking the IP address, not the port.

[GreenBay42]

The 850L GUI is the same as what I am using.

Here is what I entered:

[cacatnow]

I entered the values exactly like you did except IP address and Port Range. I put my CC's IP address (reserved it too) and 1-65535 as port range because I can't leave it empty. My CC is still using Google DNS.

[GreenBay42]

So you do not have a drop-down next to protocol & port range that gives you TCP, UDP, or ANY?

Also, create a second rule blocking 8.8.4.4.

[cacatnow]

Posted screenshot

https://imgur.com/a/1RnRJ

[GreenBay42]

hmm strange. That should work. 

Just to test, edit the 8.8.8.8 rule and put in 192.168.0.1-192.168.0.254 as the source range. Apply. Make sure Turn IPv4 filtering is ON and DENY.... is selected. Click save. Should take like 5 seconds and then ping 8.8.8.8 from your computer and see if you get replies.

What firmware are you using and what brower? I used IE 11.

[cacatnow]

I still get replies from 8.8.8.8 FW 2.09 browser Google Chrome

[GreenBay42]

I just saw 2.09 from your first post 

You may want to update the firmware. The latest global release is 2.21. Maybe try that and see if it fixes it.

I see 2.09 is the latest in your region - http://www.dlink.com.my/dir-850l-msia/#firmware

I do not know if the world wide (WW) firmware will work with your router. 2.21 is on the US site as well as tsd.dlink.com.tw (global releases). You may want to contact tech support and report the issue and see if using the 2.21 firmware will work. Your rules are set up properly but looks like the router is not blocking the traffic.

Link to WW firmware - ftp://FTP2.DLINK.COM/PRODUCTS/DIR-850L/REVB/DIR-850L_REVB_FIRMWARE_v2.21B01.zip

[cacatnow]

Lol I'm afraid to update to this WW firmware. It might broke the router altogether. Anyway thanks for the support.

[GreenBay42]

Sorry that didn't work for you. Definitely contact tech support because your settings are correct.

This firmware is a 2 step process. The first firmware encrypts the firmware so you will not be able to downgrade if it doesn't work. (you will have to do an emergency firmware recovery to go back to 2.09) so I do understand your hesitation.