Motzart
-
Posts
5 -
Joined
-
Last visited
Posts posted by Motzart
-
-
Pinging works, but I don't understand my captures.
Same scenario as above, I just pinged my pi instead of my router.
Victim:
Attacker:
Pi:
What I don't understand: In my attacker I only monitor tower->weiss (attacker->victim), nothing else. Is this normal?
Still: Pinging my router, or sending DNS requests to it does not work at all.
Thanks for your help again!
-
I started wireshark on my victim ("weiss") and on my attacker ("tower") and pinged to my router ("speedport.ip").
I filtered for ICMP.
Attacker:
Victim:
What I see:
The ICMP requests are directed to my attacker (ofc I am not in promiscuous mode). My attacker sends them to the router, but the router does not answer.Thanks for your help!
-
I did. Sorry I forgot to mention.
-
Hi!
I am new to ettercap (although I am not new to security, and I am not a kiddy ).Because I am working on a mac I enabled the "quick and dirty fix" in etter.conf.
I followed the standard tutorials to spoof arp (Added roter and victim to target 1 and 2, arp poisoning, start sniffing).
What I expect: My victim is able to browse HTTP ordinarily.
What I get:
The arp is spoofed correctly (the cache got my attacker's mac instead of the router's), but I get request timeouts when pinging my router. I cannot open web pages anymore, nothing loads.
Although the connections tab lists the victim's connections correctly.
First I thought I needed a software that listens on my attacker in order to tunnel the traffic to the router (man in the middle). I found a thread saying it should listen on 8080. But after watching a video I guess that's already included when I select ARP poisoning?
What point am I missing?
I hope I provided enough information. Thanks for any help!
Victim does not establish connections after arp poisoning (ettercap)
in Security
Posted · Edited by Motzart
The output is:
I don't think this will be very helpful :(
My terminal that is attached to ettercap shows