upon further investigation is would appear that what seems to have resolved my issue with PlexConnect and WHS2011 is what I did in IIs and not the router. I removed the firewall entries and it still worked :huh:
Again sorry, I'm at my witts end with this. I have it working when I stop the default sites on IIs which breaks some of the WHS2011 functionality. If I were able to successfully do the DNSMasq I think it would resolve that issue but this is one step closer than I was yesterday, as I have gotten a positive response from PlexConnect. Wish I could be more help.
Just a quick hint. It is possible to only let the ATV use the custom DNS for
the trailers website, but all other clients (MAC, PC, smartphones, etc.)
will still get the "real" website.
Following everything like the original posts on page 1 here explain.
Add the following two lines to the Dnsmasq custom configuration:
Replace ** with the MAC address of your AppleTV (you can easily see it in
the Tomato WebUI, go to Overview, Device List). And replace the IP with
the IP of your PlexConnect DNS! Make sure you enable that DNS too!
What this does is to give out a different DNS server over DHCP to the AppleTV,
but all other DHCP clients still get the normal answer (your router).
Make sure to renew the DHCP release on the ATV, or to be safe, just reboot it.
This way you can use PlexConnect DNS on your ATV, but all other clients can
still use the trailers website without problems. Unfortunately, if you
turn off your PlexConnect computer, the ATV will still try to connect to it
and it will timeout. But i guess most people will run PlexConnect on their PMS
anyway and it is up 24/7.
10.10.10.121 is my appletv, 10.10.10.1 is my router and 10.10.10.116 is my synology/plex/plexconnect. I changed the Settings.cfg to run ssl on 82 and www on 81 so I can continue to run my other webservices on 443 and 80 with no disruption.
I do have dnsmasq to set the router as the address for trailers.apple.com and atv.plexconnect to 10.10.10.1.
Works great so far.
Thank you! This is the only solution that worked for me on this thread.
My router is running Tomato firmware so after some tweaking the following in Administration -> Scripts-> Firewall works:
• Run a dedicated instance of dnsmasq, that will forward everything to the “real” dns (except the hijacked host), and redirect all the dns traffic from the appletv to the dedicated dns so that no specific configuration is required on the appletv.
• Redirect the HTTP and HTTP traffic from the appletv to arbitrary ports in the PlexConnect server (the SNAT destinations allow the redirection to work even if the appletv and the PlexConnect server do live on the same network).
Note: In some kernel versions there’s a weird interaction between iptables and bridged interfaces (see http://www.spinics.net/lists/netdev/msg268016.html). if the script does not seem to work, and you’re using a bridge (say between ethernet and wifi), you may want to try to uncomment (and adapt) the ifconfig line at the end.
Is there a minimum version of tomato required to run this? I have tried setting this script in the firewall section, but the log file shows dnsmasq FAILED to start each reboot. Is there another way to debug this script?
I am running tomato on a WRT54GS v1.1 Yes, old but works great!
Hi, I've been testing some of the messages in here, and they all ended up in either no clear results, or the apple TV directly getting disconnected from internet (had to reset the router). Could someone please confirm me which of the many methods listed here are more likely to work on a router (Linksys E2500 v1) with Tomato Firmware 1.28? It would really help me, thanks for reading.