Skip to content

Gargoyle blocks legit NFS mount #2

@btaub

Description

@btaub

gargoyle daemon was running on the client (192.168.1.161). Client mounted NFS (192.168.1.20). A little while after the mount, communication between the two was blocked. Comm resumed once gargoyle was stopped. Not sure how this can be remedied, aside from the end user excluding nfs ports.

./syslog:Jan  5 13:55:01 Bayshore01 gargoyle_pscand: action="block" violator="192.168.1.20" detection_type="7" timestamp="1515178501"

./auth.log:Jan  5 13:54:24 Bayshore01 sudo:    btaub : TTY=pts/20 ; PWD=/home/btaub/ ; USER=root ; COMMAND=/bin/mount 192.168.1.20:/media/btaub/70844b5d-2868-4e50-8994-fcf869ee8c1a /mnt/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions