Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 844 views
  • Users 0 members are here
Options
Suggested
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

Cannot communicate between two subnets

Kolt Litrenta

My main subnet (192.168.1.0/24) is unable to reach a newly created subnet (192.168.2.0/24).  For example, a laptop connected to the new subnet with an IP address of 192.168.2.2 cannot access a locally hosted website with the IP address of 192.168.1.17 as shown in firewall logs.

 

 

I don't know much about firewall rules but I have attempted to make one to see if communication between these two subnets would work:

 

What I configured for the source network:

 

What I configured for the destination network:

 

With this rule enabled, traffic to my second subnet from my main subnet is still disabled so my firewall rule is ineffective.  Anything I need to change or do to get this working?

 

Thank you



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    where does your firewall rule sit in your firewall list? Also please enable logging on your firewall rule so you can see what is happening.

    Also those go messages indicate that either their no path of the connection has been completed.

    Ian

Reply
  • 0

    Hi,

    where does your firewall rule sit in your firewall list? Also please enable logging on your firewall rule so you can see what is happening.

    Also those go messages indicate that either their no path of the connection has been completed.

    Ian

Children
  • 0 in reply to rfcat_vk

     

    This is where the rule is placed.

     

    Also if I attempt to access the router using its 192.168.2.0/24 gateway address (192.168.2.1) from my desktop (192.168.1.45), I am unable to access the GUI and I see the following in logs,

     

    With the message saying 'Invalid TCP state' as shown in the screenshot.  However I can ping it:

     

     

     

     

    If I go to an IP address on the 192.168.2.0 subnet that is not assigned to anything, this shows up in logs: