From IP list to IPTables blacklist

Fabio grossi

Hello,
I have an IP list
For example:

1.1.1.1
2.2.2.2
3.3.3.3

This list is very long (around 40000 IP)
I need that:

from
1.1.1.1
become
iptables -A INPUT -s 1.1.1.1 -j DROP

This for each line of the IP list

Ekopalypse

@Fabio-grossi

I guess this does it.
find dialog check regular expression

find what:\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}
replace with: iptables -A INPUT -s $0 -j DROP

PeterJones

Assuming your list is literally just a list, nothing else in the document:

find = (?-s)^.+$
replace = iptables -A INPUT -s $0 -j DROP
mode = regular expression

-----
FYI:

This forum is formatted using Markdown, with a help link buried on the little grey ? in the COMPOSE window/pane when writing your post. For more about how to use Markdown in this forum, please see @Scott-Sumner’s post in the “how to markdown code on this forum” topic, and my updates near the end. It is very important that you use these formatting tips – using single backtick marks around small snippets, and using code-quoting for pasting multiple lines from your example data files – because otherwise, the forum will change normal quotes ("") to curly “smart” quotes (“”), will change hyphens to dashes, will sometimes hide asterisks (or if your text is c:\folder\*.txt, it will show up as c:\folder*.txt, missing the backslash). If you want to clearly communicate your text data to us, you need to properly format it. That topic also explains how to embed images by uploading them to a public server like imgur.com, and embedding them using the syntax ![](http://i.imgur.com/QTHZysa.png)

If you have further search-and-replace (“matching”, “marking”, “bookmarking”, regular expression, “regex”) needs, study this FAQ and the documentation it points to. Before asking a new regex question, understand that for future requests, many of us will expect you to show what data you have (exactly), what data you want (exactly), what regex you already tried (to show that you’re showing effort), why you thought that regex would work (to prove it wasn’t just something randomly typed), and what data you’re getting with an explanation of why that result is wrong. When you show that effort, you’ll see us bend over backward to get things working for you. If you need help formatting, see the paragraph above.

Please note that for all regex and related queries, it is best if you are explicit about what needs to match, and what shouldn’t match, and have multiple examples of both in your example dataset. Often, what shouldn’t match helps define the regular expression as much or more than what should match.

Fabio grossi

Thanks!