Skip to content
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

Enhancement: Add option to manage entries for the API port in /media/fat/linux/iptables.up.rules #50

Closed
Kreeblah opened this issue Apr 19, 2024 · 2 comments

Comments

@Kreeblah
Copy link

I just saw the news about the new TapTo Life app, and wanted to give it a try, but because I use the security_fixes.sh script, I'm using the built-in iptables firewall on my MiSTer. So, in order to be able to access the API, I had to look through the source to find what port it runs on and write a rule for that.

It would be nice if taptui.sh had an option to do that for me, especially since I need to re-run the script after every Linux update (which means I'll need to re-add the iptables entry after each Linux update as well).

For reference, all I had to add was this:

# Allow TapTo connections
-A INPUT -p tcp -m state --state NEW --dport 7497 -j ACCEPT

It just needs to be before the lines that send things to the REJECT target.

@sigboe
Copy link
Collaborator

sigboe commented Apr 19, 2024

I kind of think this maybe should be added to the documentation, but I don't know if we should handle it directly. Unless Wizzo wants me to add it to TAPTUI.

Maybe I should make a GUI to add and remove firewall rules and donate it to the repo that maintains security_fixes.sh, In that case I would have to add it to my TODO list and not forget about it!

@sigboe
Copy link
Collaborator

sigboe commented May 6, 2024

Opened a PR at the script that manages iptables
MiSTer-devel/Scripts_MiSTer#114

@sigboe sigboe closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants