X-Git-Url: https://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=doc%2Fman1%2Fhath.1;h=207e87069da13933484907dc3a8c798c8bad647d;hb=9b637112e7112180e3ddb6129a62b5e21953b469;hp=3b245589da85d2280a617a006a6b862fb2172b30;hpb=d31bf1f13b60a813d61be616c825e324bac049a1;p=hath.git diff --git a/doc/man1/hath.1 b/doc/man1/hath.1 index 3b24558..207e870 100644 --- a/doc/man1/hath.1 +++ b/doc/man1/hath.1 @@ -41,7 +41,7 @@ the input CIDR blocks. It's the default mode of operation. .P .nf .I $ hath <<< \(dq10.0.0.0/29 10.0.0.8/29\(dq -((10)\.(0)\.(0)\.(0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15)) +((10)\.(0)\.(0)\.(15|14|13|12|11|10|9|8|7|6|5|4|3|2|1|0)) .fi .IP \(bu 2 \fBReduced\fR @@ -84,7 +84,7 @@ notation. List the IP addresses contained within the given CIDRs. .P .nf -.I $ hath listed <<< \(dq192.168.0.240/29\(dq +.I $ hath listed <<< 192.168.0.240/29 192.168.0.240 192.168.0.241 192.168.0.242 @@ -101,7 +101,7 @@ Perform reverse DNS (PTR) lookups on the IP addresses contained within the given CIDRs. .P .nf -.I $ hath reversed <<< \(dq198.41.0.4/30\(dq +.I $ hath reversed <<< 198.41.0.4/30 198.41.0.4: a.root-servers.net. 198.41.0.5: 198.41.0.6: rs.internic.net. @@ -114,7 +114,7 @@ runtime on the command line; for example, the following will perform 25 lookups in parallel: .P .nf -.I $ hath reversed +RTS -N25 <<< \(dq198.41.0.4/24\(dq +.I $ hath reversed +RTS -N25 <<< 198.41.0.4/24 198.41.0.4: a.root-servers.net. 198.41.0.5: 198.41.0.6: rs.internic.net. @@ -133,7 +133,7 @@ address, and this messes up e.g. \fIgrep -o\fR. Without \fB\-\-barriers\fR, you can match things you shouldn't: .nf -.I $ echo \(dq127.0.0.100\(dq | grep -P $(hath <<< \(dq127.0.0.1/32\(dq) +.I $ echo 127.0.0.100 | grep -P $(hath <<< 127.0.0.1/32) 127.0.0.100 .fi @@ -141,7 +141,7 @@ Without \fB\-\-barriers\fR, you can match things you shouldn't: Using \fB\-\-barriers\fR can prevent this: .nf -.I $ echo \(dq127.0.0.100\(dq | grep -P $(hath -b <<< \(dq127.0.0.1/32\(dq) +.I $ echo 127.0.0.100 | grep -P $(hath -b <<< 127.0.0.1/32) .I $ echo $? 1 .fi @@ -151,6 +151,6 @@ But, this may also cause the regex to match something that isn't an IP address: .nf -.I $ echo \(dqx127.0.0.1x\(dq | grep -Po $(hath -b <<< \(dq127.0.0.1/32\(dq) +.I $ echo x127.0.0.1x | grep -Po $(hath -b <<< 127.0.0.1/32) x127.0.0.1x .fi