Jump to content
FQs19

Can't view Plex content Locally...NAT issues?

Recommended Posts

My setup:

Internet>Verizon G1100 gateway>R1 (DMZ'd in the G1100)>Plex server (on a pc)

I'm running a Plex server on a pc that is wired to the R1 which is DMZ'd in my Verizon G1100 router.

I can not connect to my Plex server from anything on my local network, but I can connect to my Plex from outside my network. 

There seems to be a problem with NAT and I can't figure out how to fix it. I've tried manually port forwarding everything I could think of, but nothing has worked. 

To be more specific, I'm trying to connect to my Plex server from devices that are under my Verizon G1100 which are on 192.168.1.x subnet. The R1 is running a dhcp server on 192.168.88.x subnet. 

When I had the XR700 in this same configuration, I had zero issues with Plex. It worked perfectly. I could connect to my Plex from both locally and remotely. 

Could a dev take a look at what is different between the XR700 and the R1 running DumaOS to see why NAT traffic isn't working within the local network. 

Thanks

My Plex Server status

Capture.thumb.JPG.75a4335978b404037af27638ad6b92d9.JPG

My R1 port forwarding the correct ports

Capture.thumb.JPG.2f2f58ee5363376a0f77b2eb2e60f74f.JPG

My Macbook Pro on the G1100 subnet not being able to connect to the Plex Server on the R1 subnet

1343508300_Image11-23-18at10_12AM.thumb.jpg.d4bd08b102cce6f5043dd2735db0c27e.jpg

The most recent logs

Fri Nov 23 15:16:50 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory.
Fri Nov 23 15:15:54 2018 kern.info kernel: [47920.212000] recv: nf_ct_get failed
Fri Nov 23 15:14:54 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 15:14:54 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 15:12:56 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 15:09:34 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 15:07:41 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory.
Fri Nov 23 15:07:34 2018 kern.info kernel: [47420.188000] recv: nf_ct_get failed
Fri Nov 23 15:05:27 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:59:17 2018 kern.info kernel: [46923.100000] recv: nf_ct_get failed
Fri Nov 23 14:57:23 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:57:09 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:56:20 2018 daemon.warn dnsmasq[1120]: possible DNS-rebind attack detected: 192-168-88-15.8cbab343d9204bc98b1d780de2885481.plex.direct
Fri Nov 23 14:56:20 2018 daemon.warn dnsmasq[1120]: possible DNS-rebind attack detected: 192-168-1-243.a587e45deb5b4b239d14bfa023a5f0a9.plex.direct
Fri Nov 23 14:49:33 2018 kern.info kernel: [46338.688000] recv: nf_ct_get failed
Fri Nov 23 14:48:59 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:44:09 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory.
Fri Nov 23 14:40:21 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:40:09 2018 kern.info kernel: [45775.308000] recv: nf_ct_get failed
Fri Nov 23 14:33:18 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:30:58 2018 kern.info kernel: [45223.988000] recv: nf_ct_get failed
Fri Nov 23 14:23:29 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:21:26 2018 kern.info kernel: [44651.848000] recv: nf_ct_get failed
Fri Nov 23 14:18:26 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:12:25 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Fri Nov 23 14:12:24 2018 kern.info kernel: [44109.788000] recv: nf_ct_get failed
Fri Nov 23 14:06:51 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:04:51 2018 kern.info dpiclass-daemon: Kill flow due to timeout
Fri Nov 23 14:02:49 2018 kern.info kernel: [43534.608000] recv: nf_ct_get failed

Share this post


Link to post
Share on other sites

how are you trying to access the server page, via a web browser or app? If browser then clear cache and re-enter the ip address of your local server which is 192.168.88.15:32400

My local plex server is 192.168.1.7:32400

Share this post


Link to post
Share on other sites

Okay I think I understand the issue. I don't believe it's possible to access downstream devices the way you want to. You're accessing from WAN essentially so remote will work, otherwise you'd need to be connected to the R1 directly.

Share this post


Link to post
Share on other sites
2 hours ago, BIG__DOG said:

how are you trying to access the server page, via a web browser or app? If browser then clear cache and re-enter the ip address of your local server which is 192.168.88.15:32400

My local plex server is 192.168.1.7:32400

I access the server through the PC which is the server. My clients are unable to connect to the server so I can view the content. 

59 minutes ago, Netduma Fraser said:

Okay I think I understand the issue. I don't believe it's possible to access downstream devices the way you want to. You're accessing from WAN essentially so remote will work, otherwise you'd need to be connected to the R1 directly.

I am connecting through WAN essentially since the client I'm trying to view my Plex content on is on the WAN side of the R1, but the server is fully accessible outside my network.

It worked with the XR700 in the same configuration. So I'm not understanding why it won't work with the R1 with DumaOS. 

Share this post


Link to post
Share on other sites

If I place the Plex server PC on the G1100 network, then I'm not able to take advantage of the R1's QoS. My friends have access to my Plex content, so I could be playing online games while my friends are watching my Plex content, which could cause me lag issues. 

Share this post


Link to post
Share on other sites

I don't think anything like that is possible at the moment on the R1 until allowing access from WAN is implemented and then that might do it. Is it a big hassle accessing from the WAN address?

Just thinking, might work if you use the IP that the G1100 has given the R1.

Share this post


Link to post
Share on other sites
2 hours ago, Netduma Fraser said:

I don't think anything like that is possible at the moment on the R1 until allowing access from WAN is implemented and then that might do it. Is it a big hassle accessing from the WAN address?

Just thinking, might work if you use the IP that the G1100 has given the R1.

There's no way to enter the IP address on my devices like my LG OLED TV Plex app or my Nvidia Shield TV Plex app.

They simply ask you to sign into your account and connect automatically. 

This is the error I get when Diagnosing my Network connection on the PC which is connected to the R1:

Capture.thumb.JPG.cf85cfa2e1418a8e725372c83e47a32b.JPG

Share this post


Link to post
Share on other sites

I have. I let it use the G1100 automatic DNS from Verizon and tried 1.1.1.1 too. 

Neither worked. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...