Describe the bug:
Using a LilyGO T-Display S3 (non-touch, added an sd card module) There seems to be an issue with Karma Attack not prompting to choose a captive portal gateway and instead defaulting 192.168.4.1 which straight up does not work, not even by typing it manually, while 172.0.0.1 as the captive portal gateway does work without any issues, but as I said, the prompt to choose between 172.0.0.1 and 192.168.4.1 only appears on the stand-alone Evil Portal feature, but on features like Karma Attack that incorporate Evil Portal, there is simply no prompt or way to choose 172.0.0.1 as the gateway and they instead default to 192.168.4.1 which does not work at all.
Steps To Reproduce:
Turn on LilyGO T-Display S3 and choose Karma Attack, choose a captive portal and launch Karma Attack
- Device used: LilyGO T-Display S3 (Non-touch)
Expected behavior:
The user either gets a prompt to choose between 172.0.0.1 or 192.168.4.1 like they already do with the standalone Evil Portal feature, or they can change the default gateway through an exposed setting in the Bruce wi-fi configs or in Bruce config files in LittleFS or SD
Actual behavior:
The user is forced into using 192.168.4.1 as their captive portal gateway, which is not functioning on most devices.
Additional context / logs:
192.168.4.1 as a captive portal gateway just doesn't work, not being able to use 172.0.0.1 instead in Karma Attack makes the feature significantly less capable.
Describe the bug:
Using a LilyGO T-Display S3 (non-touch, added an sd card module) There seems to be an issue with Karma Attack not prompting to choose a captive portal gateway and instead defaulting 192.168.4.1 which straight up does not work, not even by typing it manually, while 172.0.0.1 as the captive portal gateway does work without any issues, but as I said, the prompt to choose between 172.0.0.1 and 192.168.4.1 only appears on the stand-alone Evil Portal feature, but on features like Karma Attack that incorporate Evil Portal, there is simply no prompt or way to choose 172.0.0.1 as the gateway and they instead default to 192.168.4.1 which does not work at all.
Steps To Reproduce:
Turn on LilyGO T-Display S3 and choose Karma Attack, choose a captive portal and launch Karma Attack
Expected behavior:
The user either gets a prompt to choose between 172.0.0.1 or 192.168.4.1 like they already do with the standalone Evil Portal feature, or they can change the default gateway through an exposed setting in the Bruce wi-fi configs or in Bruce config files in LittleFS or SD
Actual behavior:
The user is forced into using 192.168.4.1 as their captive portal gateway, which is not functioning on most devices.
Additional context / logs:
192.168.4.1 as a captive portal gateway just doesn't work, not being able to use 172.0.0.1 instead in Karma Attack makes the feature significantly less capable.