Interface and Rules
-
@greatbush said in Interface and Rules:
My question is what happens if i change the interface from server to storage.
Most probably nothing.
The rule might not match any traffic on the storage interface, since it only filters for sources = SERVERS net. -
@viragomann So if the rule matched a traffic on the storage interface, will it let traffic through?
-
@greatbush Yes, exactly.
-
@greatbush said in Interface and Rules:
So if the rule matched a traffic on the storage interface, will it let traffic through?
Your screenshot shows a rule defined on the interface "SERVERS". Traffic on the "STORAGE" interface will never match any rules defined on the "SERVERS" interface.
-
If you edit the rule and change the interface that moves the rule to the new interface.
Thus the rule will no longer be present on SERVERS so traffic from there to CLIENTS will no longer be passed.
As mentioned that rule on STORAGE will not pass anything because traffic can never be from SERVERS net there.
-
@stephenw10 Thank you
I am still trying to wrap my ahead around something. Same three networks(storage, client, server).I want devices on the storage network to reach and get responses from devices on the server network. Do i create 2 rules or 1.
storage interface rule: source = [single host or alias of devices on the storage network]
destination = server networkserver interface rule: source = [single host or alias of devices on storage network]
destination = [server network, devices on server]I feel like i am overthinking this problem.
-
@greatbush I believe you take your rule above and duplicate it on each of the interfaces to direct it to the other (2) interfaces.
You would have to create two rules on each interface if you want that interface to talk to the other two interfaces.
-
@The-Party-of-Hell-No Sorry for being optuse but is this what you mean;
-
@greatbush said in Interface and Rules:
I want devices on the storage network to reach and get responses from devices on the server network. Do i create 2 rules or 1.
Rules apply as packets enter the firewall. Responses are always allowed. So, one rule for one direction.
https://docs.netgate.com/pfsense/en/latest/firewall/fundamentals.html#stateful-filtering
-
@SteveITS said in Interface and Rules:
https://docs.netgate.com/pfsense/en/latest/firewall/fundamentals.html#stateful-filtering
"Using this mechanism, traffic need only be permitted on the interface where it enters the firewall. When a connection matches a pass rule the firewall creates an entry in the state table. Reply traffic to connections is automatically allowed back through the firewall by matching it against the state table rather than having to check it against rules in both directions. This includes any related traffic using a different protocol, such as ICMP control messages that may be provided in response to a TCP, UDP, or other connection."
You are right. Thanks a lot!
