Blacklist: Difference between revisions

From DISI
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:


Thank you
Thank you
John Irwin
=== Blacklist IP Address ===
Once in a while, we would have bot submitting huge amount of requests to ZINC and overload our database
1. Figure the problematic IP Address by going to this address below and figuring out the ones with the most requests
http://epyc/server-status
2. Add IP address to blackhole list
ssh epyc
sudo ip route add blackhole <ip_address>
3. Remove the ip address from blacklist (if neccessary)
sudo ip route show // to list the black listed ips
sudo ip route del <ip_address>


John Irwin


[[Category:ZINC]]
[[Category:ZINC]]
[[Category:Jargon]]
[[Category:Jargon]]

Revision as of 18:55, 13 June 2024

HA! We do not have a blacklist for ZINC, a list of compound vendors who have been difficult or unresponsive in the past. Instead, we simply remove these vendors from ZINC completely.

If you have trouble with a vendor, whether it is failure to deliver, failure to communicate in a timely fashion, or some other reason that makes you not want to do business with them, please write to us so that we incorporate your feedback to make ZINC more useful to everyone.

Thank you John Irwin


Blacklist IP Address

Once in a while, we would have bot submitting huge amount of requests to ZINC and overload our database 1. Figure the problematic IP Address by going to this address below and figuring out the ones with the most requests

http://epyc/server-status

2. Add IP address to blackhole list

ssh epyc
sudo ip route add blackhole <ip_address>

3. Remove the ip address from blacklist (if neccessary)

sudo ip route show // to list the black listed ips
sudo ip route del <ip_address>