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

luci-app-xinetd: incorrect handling of REDIRECT option in the UI #7664

Closed
1 task done
lars18th opened this issue Mar 6, 2025 · 5 comments · Fixed by #7689
Closed
1 task done

luci-app-xinetd: incorrect handling of REDIRECT option in the UI #7664

lars18th opened this issue Mar 6, 2025 · 5 comments · Fixed by #7689

Comments

@lars18th
Copy link

lars18th commented Mar 6, 2025

Is there an existing issue for this?

  • I have searched among all existing issues (including closed issues)

screenshots or captures

Hi,

This is related to commit #6194

Image

Actual behaviour

When you want to use the REDIRECT option with the UNLISTED Type, the SERVER option continues to be required. Therefore using the Luci UI you can't add any redirect port.

Expected behaviour

The SERVER option has to be optional if the REDIRECT option is used.

Steps to reproduce

  1. go to: Services -> Xinetd
  2. Select "Add new service entry"
  3. Type Servicename (test), Port (11122) and Redirect (127.0.0.1:22) and press "Save"

You can't

Additional Information

Powered by LuCI openwrt-24.10 branch (25.062.67750~c03591c) / OpenWrt 24.10.0 (r28427-6df0e3d02a)

What browsers do you see the problem on?

No response

Relevant log output

@systemcrash
Copy link
Contributor

@feckert do you have a good idea to fix this?

@lars18th
Copy link
Author

@feckert do you have a good idea to fix this?

Yes. Here the idea for the fix:

  • Convert the "Redirect" box into a select tick (on/off).
  • If "Redirect" is off then "Server" box is visible.
  • If "Redirect" is on then "Server" box is disabled, and replaced by a "Redirect" box.

What you think?

@feckert
Copy link
Member

feckert commented Mar 19, 2025

@lars18th This should fix your issue #7689
Can you please report back.

@lars18th
Copy link
Author

@lars18th This should fix your issue #7689 Can you please report back.

Hi @feckert ,

Tested and working. Ready to merge. Thank you. 👍

@feckert feckert closed this as completed Mar 19, 2025
@feckert feckert mentioned this issue Mar 19, 2025
10 tasks
@lars18th
Copy link
Author

Thank you @feckert

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

Successfully merging a pull request may close this issue.

3 participants