I have reported similar issues on my e1200 (broadcom):
jpp wrote:
I am using : DD-WRT v3.0-r34929 mega 02/12/18 on two e1200v2 and i am getting a few errors on the logs related to igmp:
user.warn igmpproxy[1585]: MRT_DEL_MFC; Errno(2): No such file or directory
user.warn igmpproxy[1585]: No interfaces found for source 0.0.0.0
igmpproxy[2306]: select() failure; Errno(4): Interrupted system call
Any thoughts?
My HP printer has some connectivity problems with the same router and i read that printer uses multicast / bonjour / mdns settings to work.
Posted: Mon Jun 25, 2018 3:44 Post subject: Chromecast Working now.
Firmware: DD-WRT v3.0-r36168 mini (06/20/1
I have tried several of the mini's and chromecast is working with them but not the mega's. Having a issue where I am disconnecting and reconnecting every now and them but chromecast is working again.
Posted: Tue Jun 26, 2018 2:39 Post subject: Got it working.
I have installed a bunch of different versions both old and new. I had some issues with some kind of interference with my wireless HDMI transmitter and the Mixed Mode and had to set it to Mixed-BG and chromecast and wifi is working for me with my e2000
Firmware: DD-WRT v3.0-r36168 mini (06/20/18
With the larger versions the chromecast wouldn't work but with the mini's they did. Thanks everyone for the help.
I updated my Netgear R6250 to DD-WRT 36070 and chromecast (still) doesn't work. I have previously tried the iptables changes to no effect. I might add that the web admin GUI is also very, very slow.
I went back to 32170 (from june 2017) and chromecast works.
Is there any known way of getting this to work on recent DD WRTs? I'll do a reset if I really have to (it's then some work to get it back to the way I want it, since I fix a load of IPs, MACs etc).
I also had a problem using a system that I believe uses similar multicasts to Chromecast (Samsung multi-room app for managing soundbars and speakers). That works on the older firmware but not the new one.
don't drop or reject dns queries, redirect or dnat them to your dns server
How can I do that?
iptables -t nat -A PREROUTING -i lan -p udp --dport 53 -j DNAT --to 192.168.1.1
iptables -t nat -A PREROUTING -i lan -p tcp --dport 53 -j DNAT --to 192.168.1.1
Add these to the firewall. Click apply settings. Profit?
You might need to enable local dns on the services tab.
Thanks very much. Before I try this, can you explain what it's doing? It looks like it is taking all DNS queries addressed to port 53 and sending them to the local gateway router DNS. Is that correct? If so, won't that stop all my normal DNS access?
don't drop or reject dns queries, redirect or dnat them to your dns server
How can I do that?
iptables -t nat -A PREROUTING -i lan -p udp --dport 53 -j DNAT --to 192.168.1.1
iptables -t nat -A PREROUTING -i lan -p tcp --dport 53 -j DNAT --to 192.168.1.1
Add these to the firewall. Click apply settings. Profit?
You might need to enable local dns on the services tab.
Thanks very much. Before I try this, can you explain what it's doing? It looks like it is taking all DNS queries addressed to port 53 and sending them to the local gateway router DNS. Is that correct? If so, won't that stop all my normal DNS access?
Well I'm still learning all of this... Yes you are correct. From what I understand as long as you are using dnsmasq to specify a dns address (dhcp-option=6,1.1.1.1) everything should work correctly.
don't drop or reject dns queries, redirect or dnat them to your dns server
How can I do that?
iptables -t nat -A PREROUTING -i lan -p udp --dport 53 -j DNAT --to 192.168.1.1
iptables -t nat -A PREROUTING -i lan -p tcp --dport 53 -j DNAT --to 192.168.1.1
Add these to the firewall. Click apply settings. Profit?
You might need to enable local dns on the services tab.
Thanks very much. Before I try this, can you explain what it's doing? It looks like it is taking all DNS queries addressed to port 53 and sending them to the local gateway router DNS. Is that correct? If so, won't that stop all my normal DNS access?
Well I'm still learning all of this... Yes you are correct. From what I understand as long as you are using dnsmasq to specify a dns address (dhcp-option=6,1.1.1.1) everything should work correctly.
Don't use the latest build or any build on 2018 if you use Chromecast. I tried 3 different builds on 2018 and all of them works intermittently. I roll back to R30949 works. The reason of trying a new firmware was because the R30949 Access Restrictions doesn't work, but I tried all versions and none of them works (well that is another issue).
The method I tried are adding the command on firewall, changing the DNS to the comcast dns and other dns.
Linksys WRT1900ACS Ver2
Comcast
Chromecast Ver 1 and 2.
Nvidia Shield TV
I’m not sure if this is exacty the same thing, but on my Android TV going through a Linksys E900 with ddwrt r36079 mega as a client bridge. When the tv was running through that, I wasn’t able to see it as a castable device on any of my devices connected to my wi-fi. The only way I was able to see it was it was to wire my laptop to the client bridge as well, then I could see it on my laptop only.
To resolve this, I was able to put the r36079 mini k2.6 build on there with the same client bridge configuration, then I was able to cast to it from all my devices.
