Apple TV and Plex attached to different routers

Dev Community Apps & Creations
1

Well hello there, dear Plex Community!

I've been using Plex for quite a while now on my Apple TV as well as on other client devices. Recently I was forced to rework our wired home network setup which made it impossible to for me to connect my aTV 3 to my PMS.

 

Our ISP recently made the switch from good ol' copper to fancy new fibre. Awesome! But chaos unleashed when I found out that the new proprietary router gave mandatory super user access to my ISP and therefore my existing private lan environment. No go! So I purchased myself a new router and tried to put the ISP router to bridge mode. Of course this was not supported because the also propriatry TV boxes need to be attached to the ISP router. So I setup IP-forwarding to my new router with the resulting problem of a second subnet.

 

Due to the tiny wire channels in our house I am not able to wire a second ethernet connection from our TV room to the new router so the aTV has to be attached to the ISP router, my server where PMS and PlexConnect is installed obviously hides behind my new private router. To clarify the setup I attached a rudimentary network plan to this post.

 

The ISP router is routing the 192.168.0.0/24 with the router on 192.168.0.1 forwarding all incoming web traffic to my second router on 192.168.0.2. This one manages the 192.168.1.0/24 network with my PMS on 192.168.1.31. The outside world is able to ping my PMS via the external 27307 port which is forwarded to 32400 by my second router. However since the traffic from aTV is originating inside my first network it does not get forwarded to PMS by the ISP router.

 

PlexConnect is setup like this:

[PlexConnect]
enable_plexgdm = False
ip_pms = 192.168.1.31
port_pms = 32400
enable_dnsserver = True
port_dnsserver = 53
ip_dnsmaster = 8.8.8.8
prevent_atv_update = True
enable_plexconnect_autodetect = True
ip_plexconnect = 0.0.0.0
hosttointercept = trailers.apple.com
port_webserver = 80
enable_webserver_ssl = True
port_ssl = 443
certfile = ./assets/certificates/trailers.pem
loglevel = Normal
logpath = .

My aTV ethernet connection like this:

DHCP IP: 192.168.0.41 (reserved IP via ISP router)
SM: 255.255.255.0
Router: 192.168.0.1
DNS: 192.168.1.31

Any thoughts how I can resolve this issue?

2

Errrmm... Use WiFi? To connect the ATV directly to the non-ISP router?

3

Well thank you for this imput. However the Wifi Connection between the router and aTV is quite poor due to a concrete wall inbetween them.

4

Figured there was probably a good reason you weren't doing that, but worth a shot at the easy solution. :)

It'll take someone with more networking experience than me to help with the wired options, alas.

5

Until a networking expert can give a better advice, here are some options that I would try (I don't know if any of these will work):

  1. Point the DNS of the ATV to 192.168.0.2 (the IP of your new router), and in this new router assign ports 80, 81 and 443 to your PMS machine
  2. Interchange your new router with the switch (top rightmost one). This will put PMS in the same LAN as the ATV
  3. Modify netmask
6

Thank you for your thoughts, moody_blue!

ad 1) Tried that. Did not work.

ad 2) This is not possible. The ethernet wire between the ISP router and the first GS105E switch is the achilles heel of my setup. No possibility to switch those two.

ad 3) Not possible. The R7000 does not allow me to set a subnetmask on the LAN port that would include its own WAN address.

One interesting thing is that the computer running PMS is able to ping the aTV but if I attach a client to aTV port of the switch I am not able to ping the PMS machine.

7

Static routes?

8

Until the experts get here, try this?

Port forwarding wrt PMS is frowned upon though I think, like you mentioned it's your only option, leaving PMS open to the www is like leaving your a** open ;) just saying! I'm sure a networking expert will help with that!

Updated your map(amateurly) to share my thoughts!

![post-220329-0-86945100-1401425674.png|690x376](upload://gxpjFKct4zdnSKdxvlCHgOxqAEg.png)

Update! You've got me all hooked ;)

Secutity option 1 is to let your R7000 behave like its a computer, don't port forward, let there be that internet lag, DD-WRT the R7000 if required/possible. The internet required is just minimal for PlexConnect/PMS/Clients the lag is ok. You will be secure, me thinks, with this setup.

Option 2, try bridge mode again on the proprietary modem, use PPPoE login details on the R7000 (I guess youv'e tried this) just give it a shot! the ke is in the settings for your proprietary modem, VCI 0 - 35 or something like that depending on your ISP, you have to delete all other modes and just leave the bridge mode settings. Run through all the existing settings and take screenshots/backup before you delete

Option 3, pay the ISP guy $50 to set it up, they know that the f**k their doing, most of the time ;)

If all fails, try the below, sorry but I can't be of more help without understanding the ISP:

![post-220329-0-18606600-1401430454.png|690x376](upload://9Hxw5sgQxxDNqGeu9DVAplmwtBI.png)

OR

![post-220329-0-99841900-1401430869.png|690x433](upload://2i3barjLEUPrtKbhD2DCOejgDG6.png)

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.