Looks like you’re on AWS – you could do it through the security policies on AWS 
instead as well.


------
Joe


From: pound <pound-boun...@apsis.ch> on behalf of John Hayward 
<john.hayw...@wheaton.edu>
Reply-To: Pound mailing list <pound@apsis.ch>
Date: Wednesday, March 25, 2020 at 3:03 AM
To: "pound@apsis.ch" <pound@apsis.ch>
Subject: [pound] configuring ufw with pound

Hi Pound people,

First thanks for this useful facility.

I'm trying to set up ufw to block a few bad actors from accessing the service 
provided by pound.

When I run ufw adding rules to deny access to these bad actors and enable ufw 
it appears that it blocks all traffic - I thought the issue might be routed 
being disabled so I enabled that and still no dice.

Here is what the verbose status of ufw is:
====
root@ip-172-31-45-181:~# ufw status verbose
Status: active
Logging: on (low)
Default: allow (incoming), allow (outgoing), allow (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
Anywhere                   DENY IN     5.62.43.182               
Anywhere                   DENY IN     77.234.43.131             
Anywhere                   DENY IN     5.62.43.158               
Anywhere                   DENY IN     5.62.43.146               
Anywhere                   DENY IN     5.62.43.170               
Anywhere                   DENY IN     5.62.43.134               
Anywhere                   DENY IN     94.25.171.231             
Anywhere                   DENY IN     24.60.253.150             
====

Anybody have hints as to what issues there might be with using pound and ufw 
together?

johnh...

-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Reply via email to