-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example to capture tcpdump on remotehosts #1
Comments
Sure thing, I'll write something up after work. In the meantime, please check the following things:
There should be a file called |
Yes Please share the script to capture the tcpdump on multiple hosts. The version of remotecap you are using. You'll need to check that using pip
That your ssh access is working: Whether you are using ssh keys or a password If you're using a password, you must enter that password using the -p option That you are sshing as the correct user. The default is root unless you specify otherwise
Note: from user 'kodiak' am able to capture tcpdump. If your user is not root, you probably need to escalate privileges with sudo on the remote system using the -e option If this is the case, you must have sudo installed on the remote system That tcpdump is installed on the remote systems you're sshing to There should be a file called test.log or test.pcap.log in the same folder where you ran remotecap. Could you post the contents of that file here in a code block?
|
Argh, I apologize for not looking at this yesterday. I can't work on this in the office, but I will try to remember to check it out today after work. |
Hi Evanfoster,
Not a problem at all. Please check when you are free.
Thank you very much for responding.
…On Thu 2 May, 2019, 12:04 AM Evan Foster, ***@***.***> wrote:
Argh, I apologize for not looking at this yesterday. I can't work on this
in the office, but I will try to remember to check it out today after work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIARUBWR6DDCLMOMOCK3AJ3PTHPC5ANCNFSM4HI6YNBA>
.
|
I've made some major changes. Would you like to try again? EDIT: Actually, hold off, something's not right. EDIT 2: Fixed, please give it a go if you'd like. Apologies for the delay on this, it's been a crazy year! |
Sure I will check
…On Mon, 7 Oct, 2019, 1:23 AM Evan Foster, ***@***.***> wrote:
I've made some major changes. Would you like to try again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AIARUBXE544QXZFUWCAON5DQNI62RA5CNFSM4HI6YNBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOSPZY#issuecomment-538781671>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIARUBWXSHS6Y7DHX6WTTT3QNI62RANCNFSM4HI6YNBA>
.
|
can you give an examples to capture the tcpdump on two remote host simultaneously.
I may be wrong, i have tried following:
remotecap -w test.pcap 192.168.X.X
above command immediately stops, and doesn't capture the tcpdump. Please guide commands to capture
The text was updated successfully, but these errors were encountered: