You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bettercap does not listen to a tcp socket, thus no web interface in manual mode.
Maybe this is due that I have a waveshare_3 and therefore needed to replace a couple of files from the 1.5.5 image with the most recent github version to get that display working?
To Reproduce
Steps to reproduce the behavior:
Connect USB Network (or bluetooth Netzwork).
Access pwnagotchi on port 8080 and switch to manual mode.
Log-In via ssh, spawn a root shell via sudo, verify bettercap is running:
root@pwnagotchi:~# systemctl status bettercap
● bettercap.service - bettercap api.rest service.
Loaded: loaded (/etc/systemd/system/bettercap.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-07-10 10:12:04 BST; 8min ago
Docs: https://bettercap.org
Main PID: 16342 (bash)
CGroup: /system.slice/bettercap.service
├─16342 bash /usr/bin/bettercap-launcher
└─16359 /usr/bin/bettercap -no-colors -caplet pwnagotchi-manual -iface mon0
Check for listening sockets and their processes:
root@pwnagotchi:~# netstat -anpl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 16369/python3
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 498/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 468/sshd
tcp 0 0 127.0.0.1:8666 0.0.0.0:* LISTEN 403/pwngrid
Conclusion: Web-UI of bettercap is not listening.
Expected behavior
bettercap listening to port 80 in manual mode.
Screenshots
N/A
Environment (please complete the following information):
Pwnagotchi version
=> 1.5.5 with /usr/local/bin/pwnagotchi and content of /usr/local/lib/python3.7/dist-packages/ from actual master
OS version
=> Raspbian Buster
Type of hardware
=> Pi Zero W
Any additional hardware used
=> PiSugar Battery + waveshare 2.13 inch display, version on back tells 2.1 sticker on back tells V4, but runs only with
waveshare_3 setting (found instructions in this issue tracker on how to get that to work)
The text was updated successfully, but these errors were encountered:
Describe the bug
Bettercap does not listen to a tcp socket, thus no web interface in manual mode.
Maybe this is due that I have a waveshare_3 and therefore needed to replace a couple of files from the 1.5.5 image with the most recent github version to get that display working?
To Reproduce
Steps to reproduce the behavior:
Connect USB Network (or bluetooth Netzwork).
Access pwnagotchi on port 8080 and switch to manual mode.
Log-In via ssh, spawn a root shell via sudo, verify bettercap is running:
root@pwnagotchi:~# systemctl status bettercap
● bettercap.service - bettercap api.rest service.
Loaded: loaded (/etc/systemd/system/bettercap.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-07-10 10:12:04 BST; 8min ago
Docs: https://bettercap.org
Main PID: 16342 (bash)
CGroup: /system.slice/bettercap.service
├─16342 bash /usr/bin/bettercap-launcher
└─16359 /usr/bin/bettercap -no-colors -caplet pwnagotchi-manual -iface mon0
Check for listening sockets and their processes:
root@pwnagotchi:~# netstat -anpl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 16369/python3
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 498/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 468/sshd
tcp 0 0 127.0.0.1:8666 0.0.0.0:* LISTEN 403/pwngrid
Conclusion: Web-UI of bettercap is not listening.
Expected behavior
bettercap listening to port 80 in manual mode.
Screenshots
N/A
Environment (please complete the following information):
=> 1.5.5 with /usr/local/bin/pwnagotchi and content of /usr/local/lib/python3.7/dist-packages/ from actual master
=> Raspbian Buster
=> Pi Zero W
=> PiSugar Battery + waveshare 2.13 inch display, version on back tells 2.1 sticker on back tells V4, but runs only with
waveshare_3 setting (found instructions in this issue tracker on how to get that to work)
The text was updated successfully, but these errors were encountered: