Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Struggling to get Plex connected

I'm trying to get internet traffic to arrive to my Plex media server which is attached to my XGF. I've Had it working without issue when connected to my outer firewall; but I'm struggling with getting it working via XGF.

My network is as below:

 

I've already covered why I'm using the SkyQ firewall in my first bullet point of this post

My forwarding rule on the Q Firewall is like this:

Any->MediaServerIP:32400 Allow.

This has been changed to: Any->10.0.0.3:32400 Allow, as a result of me moving it internally.

I have then configured port forwarding on Sophos to this:

WAN Zone (10.0.0.0/28) -> MediaServer:32400 Allow.

I have also set up a forwarding rule in the other type of firewall rule.

I can provide screen shots if required.



This thread was automatically locked due to age.
Parents
  • Hi All,

    I deleted my firewall rules specific to this issue and rebuilt them using this post as a guide.

    The rules were similar to mine, but I'd put a "standard" firewall entry in as well as a "business" (non-http) entry that included the port forwarding etc. (Can't remember the official names). I think they were, perhaps, interfering with each other for some reason. Either way, it's working now.

    Also, one thing that is really confusing is the whole "Destination & Service" part. After reading I came to the understanding was that "destination" relates to the packet before it hits the firewall. Basically ask yourself this question before completing this section "What would be the destination of the packet if I viewed it leaving the last hop". That'll give you your answer!

Reply
  • Hi All,

    I deleted my firewall rules specific to this issue and rebuilt them using this post as a guide.

    The rules were similar to mine, but I'd put a "standard" firewall entry in as well as a "business" (non-http) entry that included the port forwarding etc. (Can't remember the official names). I think they were, perhaps, interfering with each other for some reason. Either way, it's working now.

    Also, one thing that is really confusing is the whole "Destination & Service" part. After reading I came to the understanding was that "destination" relates to the packet before it hits the firewall. Basically ask yourself this question before completing this section "What would be the destination of the packet if I viewed it leaving the last hop". That'll give you your answer!

Children
No Data