Can access plex via my IOT vlan but not my inhouse vlan.
-
@Nath2125 possible mask problem.. I didn't look to what the other networks are.. But one thing that comes to mind where answers to some source IPs work and others don't - other than a firewall blocking access from source, or only allowing specific source would be a mask problem.
Where source IP X comes in and the plex thinks oh that is on my local network, do you have a mask other than /24 ? If the plex box thinks the source IP trying to talk to it is local to its own network it would never send answer back to its gateway (pfsense).
If you sniff on your plex box and see it come in, look to see if it arps for that IP right after, if its arping for it - it thinks its on the same local network. Or just look at the mask on the interface on your plex box.
Are you running plex as a docker, or just native.. Docker likes to do stuff behind a nat, etc.
-
@johnpoz every IP range for every VLAN is /24. Plex is run on docker, which is an integration with the unraid os. So pretty much docker. Trying to figure out the best how to sniff my unraid box atm.
-
@Nath2125 can't you just ssh to your unraid or console in and install tcpdump?
edit: horrible work around, but as a quick fix until you figure out what is going on.. you could always source nat on pfsense so traffic from that network looks like its coming from that 192.168.10.x interface on pfsense - so now when you talk to plex from that network, plex would think its just some client on its own network.
Could it be something as stupid as routing.. what does your routing table look like on the unraid box, I would think just a default route to pfsense IP? Is that unraid box multihomed?
-
@johnpoz what do you mean by multihomed sorry and yes its using the top default in the image which goes to the 192.168.10.1 which is pfsense.
Getting tcp dump on my unraid box atm.
-
@Nath2125 well this looks like a problem to me..
That 192.168.16.0/20 would include your 192.168.31 your trying to talk from..
192.168.16.0 - 192.168.31.255
Would be that network range - so yeah you have a mask/routing issue.. Where that box thinks to get to that 192.168.31.x address he should just use that br-2b99 whatever interface that is vs sending it to your default gateway 10.1
-
@johnpoz said in Can access plex via my IOT vlan but not my inhouse vlan.:
Would be that network range - so yeah you have a mask/routing issue.. Where that box thinks to get to that 192.168.31.x address he should just use that br-2b99 whatever interface that is vs sending it to your default gateway 10.1
Ok so i changed the vlan to a 192.168.32.x subnet and it seems to now be picking it up. So you are correct. I did try and delete it and or find out how it was created in the route table on my unraid server but it for some reason wont delete and I dont know where it has come from so thats for further investigation. But for now its picking up fine when i moved it out of the 192.168.16.0/20 range.
-
@Nath2125 I believe that 192.168.*.0/20 is a by design network - I think it tries to use networks that are not in use and then creates a network.. So I would guess for whatever reason, it didn't detect this network and picked 192.168.20/20 which causes your problem.
Simple fix is what you did and just use a different network outside that /20
Or you could dig into docker and have it use a different range that won't conflict with the other networks you want to use.
