-
Notifications
You must be signed in to change notification settings - Fork 647
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
Feature Request: siproxd integration #246
Comments
|
Tomorrow I'll start with the basic layout. |
|
@NicholasRush Very good spec, thank you! |
|
@NicholasRush I'm quite busy with a multi wan issue here, only little time for creating the model. |
|
@mimugmail No problem, because i am currently ill. And i think i need about two weeks to be healthy again. |
It's missing some stuff. |
|
@mimugmail Oh that´s very fast. Yes siproxd definitivly can handle multiple options of these entrys: outbound_domain_name = freenet.de |
|
Ok, then we need two new tabs for users and outbound_domains, use_rport dropdown, ACLs and the plugins. How about registered devices? Is it just looking at the content of |
|
For the registered-devices file, there just have to be a protected text area Box or a scrollable |
|
Regarding plugins, we only need the stuff "Essential for OPNsense"? It's getting quite complex to make all of the useable/configureable like in you doc, esp. regexp and shortcall. |
|
a minimum viable plugin is a great start to wait and reassess later on |
|
I'm only asking because I don't know which ones are essential to run the plugin at all since I have never used siproxd :) |
|
@NicholasRush Can you show me an example output of registrations? ATM my output looks like this: |
|
@mimugmail The siproxd webgui plugin does not need to be "as fast as possible" ready to use. It is better to have more configuration features from the beginning, than a plugin which you have, but you cannot use it how you need it. I already know that my requirements, how the form should work, are not easy to develop. |
|
@mimugmail Wow, this looks very very nice! I will test it soon. |
|
@NicholasRush with the latest update you can install the plugin via CLI:
Would be cool if you find the time to test it, it wont go stable without your OK :) |
|
PS. siproxd installs automatically |
|
I will test the plugin completely at the weekend. |
|
@mimugmail There are currently too many bugs in it, to make the plugin public available. First there are small bugs like the interface settings, which are not set. The rport option sets a variable. The RTP input and output dejitter cannot be set.
Thats what i have currently found out. If i find more bugs i will post them here. |
|
“Option3” is a new core feature that is missing from your install (development version) Siproxd is still in development mode... we can take as many iterations as necessary before it is shipped as 1.0 in an actual opnsense release. 😊 |
|
The Bugs, that i have described, are all that i could find. If they are fixed to the end of next weekend, i will test it again. |
|
Thanks for testing! I'll fix them the next days and give you a note :) |
|
Hi @NicholasRush, patches are in but not as a pkg yet. If you want to test: |
|
This is enough... ;) |
|
again what learned :D |
|
Which browser are you using? For me dejitter stuff is working fine. I can add an additional save button in the users tab, no problem :) |
|
@mimugmail I use Google Chrome for browsing and testing. With the dejitter stuff i only mean, that i cannot set the value, how much milliseconds delayed should. When you add an additional save button to the users tab, you should also add a save button to the outbound proxy tab. Then i am happy. :) |
|
Oh, I thought this is 0 for disable and 1 for enable :) I'll fix this! |
|
motivational post: @mimugmail @NicholasRush thank you both for the work! |
|
Show must go on :) If you want the option thing fixed: And the other things just to again: |
|
the "option thing" has been shipped in OPNsense 17.7.4 ;) https://github.com/opnsense/changelog/blob/master/doc/17.7/17.7.4#L24 |
|
Whoopsie .. so forget about this one :) |
|
@mimugmail Now everything is working fine. Great work. I think it could be now released to the public. |
|
ok, if @mimugmail agrees I'll change it to 1.0 and remove the development lock so that it will show up in 17.7.6. :) |
|
@EugenMayer have tested it yet? Would be cool to have a second beta tester before going stable :) |
|
@mimugmail i would love to, still waiting for the answer in the forum ( https://forum.opnsense.org/index.php?topic=5799.msg25578#msg25578 ) to be actually sure i am falling into that case.. before i test and the result is "still not working" .. but the reason is, its just not for my case. Does not help here, if i add FUD to the issue :) |
|
@mimugmail release? :D |
|
Release, but dont be mad when there is some trouble in the beginning ;) |
|
never! thanks to you all! |
|
The trouble in the beginning should not be a big problem. If anyone have trouble with it, he or she should write in this Forum topic: https://forum.opnsense.org/index.php?topic=6112.0 |











Bezogen auf Forenthread: https://forum.opnsense.org/index.php?topic=5799
Dokumentation zur Integration von Siproxd in OPNsense.pdf
Ich hoffe ich habe das gut genug erklärt.
The text was updated successfully, but these errors were encountered: