How to find “only” IP addresses in a Local Area Network
sudo arp-scan --interface=eth0 --localnet
I know the above command works fine but it outputs everything like MAC address etc, etc.
But I need to find only IP addresses. Is it possible ?
networking lan sharing smb
add a comment |
sudo arp-scan --interface=eth0 --localnet
I know the above command works fine but it outputs everything like MAC address etc, etc.
But I need to find only IP addresses. Is it possible ?
networking lan sharing smb
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34
add a comment |
sudo arp-scan --interface=eth0 --localnet
I know the above command works fine but it outputs everything like MAC address etc, etc.
But I need to find only IP addresses. Is it possible ?
networking lan sharing smb
sudo arp-scan --interface=eth0 --localnet
I know the above command works fine but it outputs everything like MAC address etc, etc.
But I need to find only IP addresses. Is it possible ?
networking lan sharing smb
networking lan sharing smb
asked Mar 18 '14 at 16:30
gowtham nandagowtham nanda
611310
611310
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34
add a comment |
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34
add a comment |
4 Answers
4
active
oldest
votes
I just used awk,tail and head to achieve what you want:
sudo arp-scan --interface=eth0 --localnet| awk '{print $1}'|tail -n +3|head -n -2
this gives the output as
192.168.1.1
192.168.1.3
as I have only these two in my Lan.
Here awk '{print $1}' prints the ip address which is situated in the first column.
tail and head removes unnecessary stuff like the header and just shows the ip addresses.
add a comment |
I would do this using just grep:
$ sudo arp-scan --interface=eth0 --localnet | grep -oP '^[d.]+'
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.10
192.168.0.23
192.168.0.72
192.168.27.1
192.168.27.14
192.168.27.30
Explanation:
The -P tells grep to use Perl Compatible Regular Expressions, where d matches any number. The -o means "print only the matching part of the line". The regular expression I used means match the longest string (that's what the + means) of consecutive numbers (d) or dots (.) that are at the beginning of the line (^).
add a comment |
Here is a one liner to get the IP address using the ifconfig command:
~$ ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}'
192.168.1.10
Does that do what you wanted? Or did you need the arp-scan command?
I re-read and see I missed the point of the question. arp-scan shows the local IP addresses for the network and I only showed the IP of the machine with ifconfig. Below is a version of the above terdon solution only not using the PCRE library. Ubuntu had an issue with pcre and grep when I tried it.
$ sudo arp-scan --interface=eth0 --localnet | grep -o ^[0-9.]*
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Triedpcregrepas well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.
– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern:'[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)
– terdon♦
Mar 18 '14 at 19:03
|
show 3 more comments
another option to simplify @Stormvirux answer is to use the --quiet or -q and --plain or -x arguments provided with arp-scan instead of piping to head and tail commands the final command will be simpler as it will pipe only to awk :
arp-scan -qx --localnet | awk '{print $1}'
and here is a much detailed explanation from arp-scan --help :
--quiet or -q Only display minimal output. No protocol decoding.
If this option is specified, then only the IP address
and MAC address are displayed for each responding host.
No protocol decoding is performed and the OUI mapping
files are not used.
--plain or -x Display plain output showing only responding hosts.
This option suppresses the printing of the header and
footer text, and only displays one line for each
responding host. Useful if the output will be
parsed by a script.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f435982%2fhow-to-find-only-ip-addresses-in-a-local-area-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just used awk,tail and head to achieve what you want:
sudo arp-scan --interface=eth0 --localnet| awk '{print $1}'|tail -n +3|head -n -2
this gives the output as
192.168.1.1
192.168.1.3
as I have only these two in my Lan.
Here awk '{print $1}' prints the ip address which is situated in the first column.
tail and head removes unnecessary stuff like the header and just shows the ip addresses.
add a comment |
I just used awk,tail and head to achieve what you want:
sudo arp-scan --interface=eth0 --localnet| awk '{print $1}'|tail -n +3|head -n -2
this gives the output as
192.168.1.1
192.168.1.3
as I have only these two in my Lan.
Here awk '{print $1}' prints the ip address which is situated in the first column.
tail and head removes unnecessary stuff like the header and just shows the ip addresses.
add a comment |
I just used awk,tail and head to achieve what you want:
sudo arp-scan --interface=eth0 --localnet| awk '{print $1}'|tail -n +3|head -n -2
this gives the output as
192.168.1.1
192.168.1.3
as I have only these two in my Lan.
Here awk '{print $1}' prints the ip address which is situated in the first column.
tail and head removes unnecessary stuff like the header and just shows the ip addresses.
I just used awk,tail and head to achieve what you want:
sudo arp-scan --interface=eth0 --localnet| awk '{print $1}'|tail -n +3|head -n -2
this gives the output as
192.168.1.1
192.168.1.3
as I have only these two in my Lan.
Here awk '{print $1}' prints the ip address which is situated in the first column.
tail and head removes unnecessary stuff like the header and just shows the ip addresses.
answered Mar 18 '14 at 16:49
StormviruxStormvirux
3,7961831
3,7961831
add a comment |
add a comment |
I would do this using just grep:
$ sudo arp-scan --interface=eth0 --localnet | grep -oP '^[d.]+'
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.10
192.168.0.23
192.168.0.72
192.168.27.1
192.168.27.14
192.168.27.30
Explanation:
The -P tells grep to use Perl Compatible Regular Expressions, where d matches any number. The -o means "print only the matching part of the line". The regular expression I used means match the longest string (that's what the + means) of consecutive numbers (d) or dots (.) that are at the beginning of the line (^).
add a comment |
I would do this using just grep:
$ sudo arp-scan --interface=eth0 --localnet | grep -oP '^[d.]+'
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.10
192.168.0.23
192.168.0.72
192.168.27.1
192.168.27.14
192.168.27.30
Explanation:
The -P tells grep to use Perl Compatible Regular Expressions, where d matches any number. The -o means "print only the matching part of the line". The regular expression I used means match the longest string (that's what the + means) of consecutive numbers (d) or dots (.) that are at the beginning of the line (^).
add a comment |
I would do this using just grep:
$ sudo arp-scan --interface=eth0 --localnet | grep -oP '^[d.]+'
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.10
192.168.0.23
192.168.0.72
192.168.27.1
192.168.27.14
192.168.27.30
Explanation:
The -P tells grep to use Perl Compatible Regular Expressions, where d matches any number. The -o means "print only the matching part of the line". The regular expression I used means match the longest string (that's what the + means) of consecutive numbers (d) or dots (.) that are at the beginning of the line (^).
I would do this using just grep:
$ sudo arp-scan --interface=eth0 --localnet | grep -oP '^[d.]+'
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.10
192.168.0.23
192.168.0.72
192.168.27.1
192.168.27.14
192.168.27.30
Explanation:
The -P tells grep to use Perl Compatible Regular Expressions, where d matches any number. The -o means "print only the matching part of the line". The regular expression I used means match the longest string (that's what the + means) of consecutive numbers (d) or dots (.) that are at the beginning of the line (^).
edited Mar 18 '14 at 19:31
answered Mar 18 '14 at 17:40
terdon♦terdon
65.6k12138220
65.6k12138220
add a comment |
add a comment |
Here is a one liner to get the IP address using the ifconfig command:
~$ ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}'
192.168.1.10
Does that do what you wanted? Or did you need the arp-scan command?
I re-read and see I missed the point of the question. arp-scan shows the local IP addresses for the network and I only showed the IP of the machine with ifconfig. Below is a version of the above terdon solution only not using the PCRE library. Ubuntu had an issue with pcre and grep when I tried it.
$ sudo arp-scan --interface=eth0 --localnet | grep -o ^[0-9.]*
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Triedpcregrepas well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.
– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern:'[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)
– terdon♦
Mar 18 '14 at 19:03
|
show 3 more comments
Here is a one liner to get the IP address using the ifconfig command:
~$ ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}'
192.168.1.10
Does that do what you wanted? Or did you need the arp-scan command?
I re-read and see I missed the point of the question. arp-scan shows the local IP addresses for the network and I only showed the IP of the machine with ifconfig. Below is a version of the above terdon solution only not using the PCRE library. Ubuntu had an issue with pcre and grep when I tried it.
$ sudo arp-scan --interface=eth0 --localnet | grep -o ^[0-9.]*
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Triedpcregrepas well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.
– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern:'[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)
– terdon♦
Mar 18 '14 at 19:03
|
show 3 more comments
Here is a one liner to get the IP address using the ifconfig command:
~$ ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}'
192.168.1.10
Does that do what you wanted? Or did you need the arp-scan command?
I re-read and see I missed the point of the question. arp-scan shows the local IP addresses for the network and I only showed the IP of the machine with ifconfig. Below is a version of the above terdon solution only not using the PCRE library. Ubuntu had an issue with pcre and grep when I tried it.
$ sudo arp-scan --interface=eth0 --localnet | grep -o ^[0-9.]*
Here is a one liner to get the IP address using the ifconfig command:
~$ ifconfig eth0 | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}'
192.168.1.10
Does that do what you wanted? Or did you need the arp-scan command?
I re-read and see I missed the point of the question. arp-scan shows the local IP addresses for the network and I only showed the IP of the machine with ifconfig. Below is a version of the above terdon solution only not using the PCRE library. Ubuntu had an issue with pcre and grep when I tried it.
$ sudo arp-scan --interface=eth0 --localnet | grep -o ^[0-9.]*
edited Mar 18 '14 at 18:04
answered Mar 18 '14 at 16:42
Michael McGarrahMichael McGarrah
29226
29226
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Triedpcregrepas well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.
– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern:'[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)
– terdon♦
Mar 18 '14 at 19:03
|
show 3 more comments
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Triedpcregrepas well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.
– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern:'[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)
– terdon♦
Mar 18 '14 at 19:03
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
You are correct. I see what he was asking now.
– Michael McGarrah
Mar 18 '14 at 17:48
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
Thanks for the edit! Have an upvote. What was the problem on Ubuntu? I tested mine on Debian so there may well be a difference.
– terdon♦
Mar 18 '14 at 18:46
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Tried
pcregrep as well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.– Michael McGarrah
Mar 18 '14 at 19:01
I tried the -P and didn't get the pcre support working for me. I'm on Ubuntu 12.04.3 and 12.10. Tried
pcregrep as well and it wasn't happy. I'm digging some more on my setup because I like Perl syntax better for grep. Perl was the first regex I used so I have a soft spot for it.– Michael McGarrah
Mar 18 '14 at 19:01
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I'm using this to scan my local network and finding some interesting systems I hadn't documented. Glad this question came up.
– Michael McGarrah
Mar 18 '14 at 19:02
I just tried on my 13.10 VM and it worked fine:
echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern: '[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)– terdon♦
Mar 18 '14 at 19:03
I just tried on my 13.10 VM and it worked fine:
echo "1.2.3.44.5 ljasd asdlnasd " | grep -Po '[d.]+'. Make sure you quote the pattern: '[d.]+'. And of course you like PCREs, they're by far the best regex flavor around! :)– terdon♦
Mar 18 '14 at 19:03
|
show 3 more comments
another option to simplify @Stormvirux answer is to use the --quiet or -q and --plain or -x arguments provided with arp-scan instead of piping to head and tail commands the final command will be simpler as it will pipe only to awk :
arp-scan -qx --localnet | awk '{print $1}'
and here is a much detailed explanation from arp-scan --help :
--quiet or -q Only display minimal output. No protocol decoding.
If this option is specified, then only the IP address
and MAC address are displayed for each responding host.
No protocol decoding is performed and the OUI mapping
files are not used.
--plain or -x Display plain output showing only responding hosts.
This option suppresses the printing of the header and
footer text, and only displays one line for each
responding host. Useful if the output will be
parsed by a script.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
another option to simplify @Stormvirux answer is to use the --quiet or -q and --plain or -x arguments provided with arp-scan instead of piping to head and tail commands the final command will be simpler as it will pipe only to awk :
arp-scan -qx --localnet | awk '{print $1}'
and here is a much detailed explanation from arp-scan --help :
--quiet or -q Only display minimal output. No protocol decoding.
If this option is specified, then only the IP address
and MAC address are displayed for each responding host.
No protocol decoding is performed and the OUI mapping
files are not used.
--plain or -x Display plain output showing only responding hosts.
This option suppresses the printing of the header and
footer text, and only displays one line for each
responding host. Useful if the output will be
parsed by a script.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
another option to simplify @Stormvirux answer is to use the --quiet or -q and --plain or -x arguments provided with arp-scan instead of piping to head and tail commands the final command will be simpler as it will pipe only to awk :
arp-scan -qx --localnet | awk '{print $1}'
and here is a much detailed explanation from arp-scan --help :
--quiet or -q Only display minimal output. No protocol decoding.
If this option is specified, then only the IP address
and MAC address are displayed for each responding host.
No protocol decoding is performed and the OUI mapping
files are not used.
--plain or -x Display plain output showing only responding hosts.
This option suppresses the printing of the header and
footer text, and only displays one line for each
responding host. Useful if the output will be
parsed by a script.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
another option to simplify @Stormvirux answer is to use the --quiet or -q and --plain or -x arguments provided with arp-scan instead of piping to head and tail commands the final command will be simpler as it will pipe only to awk :
arp-scan -qx --localnet | awk '{print $1}'
and here is a much detailed explanation from arp-scan --help :
--quiet or -q Only display minimal output. No protocol decoding.
If this option is specified, then only the IP address
and MAC address are displayed for each responding host.
No protocol decoding is performed and the OUI mapping
files are not used.
--plain or -x Display plain output showing only responding hosts.
This option suppresses the printing of the header and
footer text, and only displays one line for each
responding host. Useful if the output will be
parsed by a script.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
user987530user987530
1
1
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user987530 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f435982%2fhow-to-find-only-ip-addresses-in-a-local-area-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Use grep to filter your output (or perl or awk .... )
– Panther
Mar 18 '14 at 16:34