Well the header tells it all. I have installed portsentry and I have shorewall up and running. But I would like to receive notifications/alerts when my computer is scanned. How would I go about achieving this?

You could use it's counter part Logcheck/Log Sentry in conjunction with Port Sentry, then the scans should show up in the emails that Log Check sends you.

Other than that don't think Port Sentry by itself can do it from my readng anyway


.....going to install Log Check myself and see how it goes.

Which portsentry are you using?
In the version im running this appears in the portsentry.conf file:

# External Command#
###################
# This is a command that is run when a host connects, it can be whatever
# you want it to be (pager, etc.). This command is executed before the
# route is dropped or after depending on the KILL_RUN_CMD_FIRST option below
#
#
# I NEVER RECOMMEND YOU PUT IN RETALIATORY ACTIONS AGAINST THE HOST SCANNING
# YOU!
#
# TCP/IP is an *unauthenticated protocol* and people can make scans appear out
# of thin air. The only time it is reasonably safe (and I *never* think it is
# reasonable) to run reverse probe scripts is when using the "classic" -tcp mode
.
# This mode requires a full connect and is very hard to spoof.
#
# The KILL_RUN_CMD_FIRST value should be set to "1" to force the command
# to run *before* the blocking occurs and should be set to "0" to make the
# command run *after* the blocking has occurred.
#
#KILL_RUN_CMD_FIRST = "0"
#
#
#KILL_RUN_CMD="/some/path/here/script $TARGET$ $PORT$"
#KILL_RUN_CMD="/bin/mail -s 'Portscan from $TARGET$ on port $PORT$' user@host <
/dev/null"

So just use the second KILL_RUN_CMD setting user@host to where you want the email to go and uncomment the KILL_RUN_CMD_FIRST = "0" line

I stand corrected, silly me.

Thank you very much for the help, everything seems to be working now, i.e. Im aware of portscans