topic Re: Simple internal rule not been caught in Spark Firewall (SMB)

Simple internal rule not been caught

mischelw — Tue, 21 Sep 2021 10:12:08 GMT

Hello,

I'm trying to block access to a specific network object, but whatever I do, access is not blocked.

Any ideas why ?

Screenshot of rule base attached, any hint will be appreciated.

BTW, outgoing to the internet (wan) blocking rules work fine, only internal. isn't these smbs gateways able to block internal objects ? will be a bummer if so...

Thanks !

Re: Simple internal rule not been caught

G_W_Albrecht — Tue, 21 Sep 2021 10:34:30 GMT

Quantum Spark 1500, 1600 and 1800 Appliance Series R80.20.30 Locally Managed Administration Guide p.77:

Traffic is not monitored or inspected between the LAN ports of a switch.

Re: Simple internal rule not been caught

mischelw — Tue, 21 Sep 2021 11:12:52 GMT

Does that mean I have a firewall that cannot monitor internal packets or block unwanted connection between different objects in the network ? sounds a basic request for such expensive SMB, no ?

Re: Simple internal rule not been caught

G_W_Albrecht — Wed, 22 Sep 2021 08:27:48 GMT

Of course that is possible if the SMB is configured appropriately ! Did you read Quantum Spark 1500, 1600 and 1800 Appliance Series R80.20.30 Locally Managed Administration Guide p.77 as i suggested ? Next sentence after the one cited is:

Configure multiple bridges between interfaces. Traffic in a bridge is always monitored and inspected by the appliance.

Re: Simple internal rule not been caught

_Val_ — Tue, 21 Sep 2021 12:12:37 GMT

Only if the traffic is routed, not switched. By default, internal interfaces are configured as a switch. If you segment your internal network, and each internal interface will be connected to a different segment, while the appliance is routing from one segment to another, then yes, you can use filtering rules for internal networks.

Re: Simple internal rule not been caught

Chris_Atkinson — Tue, 21 Sep 2021 12:41:31 GMT

Depending on the specific use case you also have the following Advanced option where relevant.

Re: Simple internal rule not been caught

mischelw — Tue, 21 Sep 2021 17:20:37 GMT

That looks interesting indeed. will try that (have to admit I was missing that :))

Thanks!

Re: Simple internal rule not been caught

mischelw — Wed, 22 Sep 2021 08:04:57 GMT

Tried to change it to true, but rule was not caught. Need to restart anything ?

Thanks

Re: Simple internal rule not been caught

_Val_ — Wed, 22 Sep 2021 08:17:34 GMT

Once again, these options only work on a routed, not switched traffic. Also, deep inspection means IPS and other advanced blades are applied on routed LAN traffic on top of the regular network security rule base, which is not enabled by default, to save on performance.

Re: Simple internal rule not been caught

mischelw — Wed, 22 Sep 2021 08:20:08 GMT

Understood, i was more looking for a rule based actions. So i will need to create vlans or separate the network so it goes to a different port in the firewall , right ?

Re: Simple internal rule not been caught

Chris_Atkinson — Wed, 22 Sep 2021 08:42:18 GMT

In it's simplest form the source & destination would normally be different subnets.