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 <firstname.lastname@example.org> Date: Wednesday, March 25, 2020 at 3:03 AM To: "email@example.com" <firstname.lastname@example.org> 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 18.104.22.168 Anywhere DENY IN 22.214.171.124 Anywhere DENY IN 126.96.36.199 Anywhere DENY IN 188.8.131.52 Anywhere DENY IN 184.108.40.206 Anywhere DENY IN 220.127.116.11 Anywhere DENY IN 18.104.22.168 Anywhere DENY IN 22.214.171.124 ==== Anybody have hints as to what issues there might be with using pound and ufw together? johnh... -- pound mailing list email@example.com https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch