Problem with the host button
D3C0D3-H4cK opened this issue · 6 comments
did you click the three buttons on top right?
did you click the three buttons on top right?
Yes, but the host option still does not appear, I thought it was my network that had a firewall but when I scanned with nmap the connected hosts did appear
Hi, this is by design.
You're running ettercap in Bridge mode, actually bridging the same physical interface, which doesn't make much sense. Bridge comes from the classic Ethernet Bridge, the ancestor of today's Ethernet switches. So you bridge between two different collision domains, meaning Ethernet segmentes, but all share the same Broadcast domain, meaning subnet.
With Bridge mode (usually when bridging between two different Ethernet adapters), Host Scanning and Host list and even poisoning MITM techniques do not make sense, as with Bridge Mode MITM, you're man-in-the-middle, by network topology. Therefore, these menu buttons are intentionally not shown.
This is actually not a defect.
Hi, this is by design. You're running ettercap in Bridge mode, actually bridging the same physical interface, which doesn't make much sense. Bridge comes from the classic Ethernet Bridge, the ancestor of today's Ethernet switches. So you bridge between two different collision domains, meaning Ethernet segmentes, but all share the same Broadcast domain, meaning subnet.
With Bridge mode (usually when bridging between two different Ethernet adapters), Host Scanning and Host list and even poisoning MITM techniques do not make sense, as with Bridge Mode MITM, you're man-in-the-middle, by network topology. Therefore, these menu buttons are intentionally not shown.
This is actually not a defect.
hello, ohhh ok thank you very much, but what happens is that when I do it without bridget ettercap it closes
The error is: FATAL ERROR: Can't insert firewall redirects
Thank you very much to koeppea , I already solved the problem, the problem with it closing is in /etc/ettercap/etter.conf in this line redir_command_on/off since it does not have #
For doing DNS poisoning, you don't need any firewall redirects.