Sponsored Content
Full Discussion: Cloudflare and iptables
Top Forums UNIX for Beginners Questions & Answers Cloudflare and iptables Post 303045762 by Abu Rayane on Sunday 12th of April 2020 11:10:26 AM
Old 04-12-2020
@Neo: Basically if an IP (range of IP) is whitelisted, it should not be blocked, or may cloudflare are using other IPs than those mentioned in their file
 

10 More Discussions You Might Find Interesting

1. IP Networking

IPtables

Hey guys, I have just started using IP tables and was wondering if anyone could direct me to any good online resources as I am totally new to this. Thanks. (1 Reply)
Discussion started by: 182x
1 Replies

2. IP Networking

Need help with iptables

Trying to create a whitelist to limit bandwidth. My sync speed is 1536/256 kbps. Simple rules in order: 1. Do not limit (or set to 1536/256) MAC 00:00:00:00:00 (computer is in 192.168.1.0/24). 2. Do not limit (or set to 1536/256) MAC 00:00:00:00:01 (computer is in 192.168.1.0/24). 3. Do not... (1 Reply)
Discussion started by: kripz
1 Replies

3. IP Networking

Iptables

Thanks in advance I have to remove ip_tables_name from /proc/net/... i was trying to do so and getting the following error cmd : rm ip_tables_names error : rm: remove regular empty file `ip_tables_names'? y rm: cannot remove `ip_tables_names': Operation not permitted (4 Replies)
Discussion started by: sudeepiit
4 Replies

4. IP Networking

Iptables

What should be the iptables rule so that only the subnet 64.61.11.224/255.255.255.248 may access the mysql port 3306 (1 Reply)
Discussion started by: proactiveaditya
1 Replies

5. IP Networking

iptables changes

Hello We have one linux machine in the office which happens to be an important firewall. I just know the basics and need to make one change Essentially it is forward mysql traffic to another internal machine. This is the original rule (forward to 192.20.0.17) which is working ... (0 Replies)
Discussion started by: rina5392
0 Replies

6. UNIX for Dummies Questions & Answers

help with iptables

Hi, On the IPTABLES, I did iptables --flush. I want to start fresh. Now I only want two things. Allow one ip address to this server. Allow port 443 as incoming from every where. Please advice how to do this. This is what I did so for. iptables -I INPUT -i eth0 -s 1.2.3.4 -j ACCEPT... (5 Replies)
Discussion started by: samnyc
5 Replies

7. UNIX for Dummies Questions & Answers

Help with iptables

Hi, I just build a Linux server, I said yes to enable the firewall. I only choose SSH conneciton. When I check the iptables. I see all of this (see below). I want to reject every thing only allow SSH from subnet 192.168.1.xx. Can you advise, how to do. Chain RH-Firewall-1-INPUT (2... (2 Replies)
Discussion started by: samnyc
2 Replies

8. IP Networking

Help with iptables

photo... (1 Reply)
Discussion started by: beerpong1
1 Replies

9. Red Hat

iptables help for port 80

Hi I enable the IPtables but port 80 was not working. Below is my active configuration (10 Replies)
Discussion started by: ranjancom2000
10 Replies

10. Ubuntu

iptables

Hi I need help with an iptables configuration, this is what I have server A Server B A and B are using different gateways i am sending port 22 from A to B, I see the packages coming in B but B is not sending the package to internet. please give me some examples. (0 Replies)
Discussion started by: lmartinez073
0 Replies
JDRESOLVE(1)						User Contributed Perl Documentation					      JDRESOLVE(1)

NAME
jdresolve - resolves IP addresses into hostnames SYNOPSIS
jdresolve [-h] [-v] [-n] [-r] [-a] [-d <level>] [-m <mask>] [-l <line cache>] [-t <timeout>] [-p] [-s <number of sockets>] [--database=<db path>] <LOG FILE> jdresolve [--help] [--version] [--nostats] [--recursive] [--anywhere] [--debug=<level>] [--mask=<mask>] [--linecache=<line cache>] [--timeout=<timeout>] [--sockets=<number of sockets>] [--database=<db path>] [--dbfirst] [--dbonly] [--dumpdb] [--mergedb] [--expiredb=<hours>] [--unresolved] [--progress] <LOG FILE> DESCRIPTION
jdresolve resolves IP addresses to hostnames. Any file format is supported, including those where the line does not begin with the IP address. One of the strongest features of the program is the support for recursion, which can drastically reduce the number of unresolved hosts by faking a hostname based on the network that the IP belongs to. DNS queries are sent in parallel, which means that you can decrease run time by increasing the number of simultaneous sockets used (given a fast enough machine and available bandwidth ). By using the database support, performance can be increased even further, by using cached data from previous runs. OPTIONS
-h, --help produces a short help message -v, --version display version information -n, --nostats don't display stats after processing -r, --recursive recurse into C, B and A classes when there is no PTR (default is no recursion) -d, --debug=<debug-level> debug mode - no file output, just statistics during run (verbosity level range: 1-3) -t, --timeout=<seconds> timeout in seconds for each host resolution (default is 30 seconds) -l, --line-cache=<lines> numbers of lines to cache in memory (default is 10000 -s, --sockets=<sockets> maximum number of concurrent sockets (use ulimit -a to check the max allowed for your operating system - defaults to 64) -m, --mask=<mask> <mask> accepts %i for IP and %c for class owner, e.g. "somewhere.in.%c" or "%i.in.%c" (default is "%i.%c") -a, --anywhere resolves IPs found anywhere on a line (will resolve all IPs if there is more than one) -p, --progress prints a nice progress bar indicating the status of the resolve operations --database=<db path> path to database that holds resolved hosts/classes --dbfirst check if we have resolved entries in the database before sending out DNS queries --dbonly don't send DNS queries, use only resolved data in the database --dumpdb dumps a database to STDOUT --mergedb merges resolved IP/classes from a file (or STDIN) with a database --expiredb=<hours> expires entries in the database that are older than <hours> hours --unresolved won't attempt to resolve IPs, only lists those that were not resolved <LOG FILE> the log filename or '-' for STDIN EXAMPLES
jdresolve access_log > resolved_log jdresolve -r -s 128 access_log > resolved_log jdresolve -r --database hosts.db access_log > res_log SEE ALSO
rhost(1) AUTHOR
jdresolve was written by John D. Rowell <me@jdrowell.com>, and is licensed under the terms of the GNU General Public License. The original version of this man page was written by Craig Sanders <cas@taz.net.au>, for the Debian GNU/Linux package of jdresolve, and is also licensed under the terms of the GNU GPL. 3rd Berkeley Distribution perl 5.005, patch 03 JDRESOLVE(1)
All times are GMT -4. The time now is 09:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy