nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Limiting CIFS connections by address?

cbhank

Hello,

I would like to restrict the CIFS subsystem to listen not only on one of the box's two network interfaces (done, works great) - but also respond only to connection requests sourced from specific networks on the wire.

How can this be achieved?

Version: Community - v3.2.0 (2056)

Best regards,
Mark

Find more posts tagged with

Comments

mikeh

That sounds more like a job for a firewall (software or hardware) - if you're on a Linux system, check "iptables".

Thanks,
Mike

cbhank

Yes, however these sorts of things can be done simply and internally with most other services like apache and samba … I am hoping it can be configured internally, otherwise your idea is definitely worth pursuing.

Thanks for the input!

tommy

Hi chbank,

Interested knowing how you proceed to restrict CIFS subsystem to listen to only one of your box's two network interfaces.
Thanks

cbhank

In file-servers.properties I did this:

cifs.bindto=192.168.10.40
cifs.broadcast=192.168.10.255

This is the IP held by that interface. That pretty much took care of it. However, I never went further regarding limiting the source connections. Our firewall takes care of that from the outside.