[sr-dev] Re: [kamailio/kamailio] [pua] reginfo_increase_version does nothing (Issue #3234)

2024-02-09 Thread Matteo via sr-dev
Sorry for the late reply, but seems good to me! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3234#issuecomment-1936214221 You are receiving this because you are subscribed to this thread. Message ID: ___

[sr-dev] [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
### Description While trying latest kamailio 5.7 branch, when tls_threads_mode is set to 1, it fails to load self signed certificates. Setting tls_threads_mode to 0 works as expected. Certificates are self signed for a local test env, generated with openssl 3.x. ### Troubleshooting The issu

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
After further digging in my setup, as soon as I disabled the mqtt module everything works. So there's maybe someting in the mqtt module that's not yet adapted to the new tls setup? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomme

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
Yes, mqtt is using TLS, the config is pretty trivial ``` modparam("mqtt", "host", MQTT_HOST) modparam("mqtt", "port", 8883) modparam("mqtt", "keepalive", 5) modparam("mqtt", "id", MQTT_NODE_NAME) modparam("mqtt", "username", MQTT_USER) modparam("mqtt", "password", MQTT_PASS) modparam("mqtt", "will

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
it makes an immediate connection to the broker on startup -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961439777 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
I'll try, since my setup is dockerized I'll need to play a bit with it. Will report as soon as I'm able to do it, should not be too hard. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961450787 You are receiving this because

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
I've tried and gdb stops at ``` Thread 1 "kamailio" hit Breakpoint 2, 0x7ff30a1c2a70 in CRYPTO_THREAD_set_local () from /lib/x86_64-linux-gnu/libcrypto.so.3 (gdb) bt ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-196148

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
> I can't reproduce any error with the config below. well, I have various other modules loaded, but only disabling mqtt makes it work, that's why I pointed at it. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961492335 You a

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
Yep, sorry ``` Thread 1 "kamailio" hit Breakpoint 2, 0x7fb1301c2a70 in CRYPTO_THREAD_set_local () from /lib/x86_64-linux-gnu/libcrypto.so.3 #0 0x7fb1301c2a70 in CRYPTO_THREAD_set_local () from /lib/x86_64-linux-gnu/libcrypto.so.3 #1 0x7fb1301bfad3 in OPENSSL_thread_stop () from /l

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
yes, that break reports only shutdown routines. Well actually a lot of modules: ``` loadmodule "tls.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "db_postgres.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "dialog.so" loadmodule "maxfwd.so" loadmodule "xlog.so" loa

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
Ok, further progress: my setup has `enable_tls=yes` in the config. removing it (which disables SIP TLS) kamailio works with mqtt too. So seems something related to concurrent startup of mqtt tls and core tls? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kama

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
while disabling TLS on mqtt (let it go in plain) and keeping enable_tls=yes works too -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961536868 You are receiving this because you are subscribed to this thread. Message ID: ___

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
further infos: launching with "strace -ff kamailio" which slows down things... it works. so seems a race condition? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961687589 You are receiving this because you are subscribed to

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-23 Thread Matteo via sr-dev
last for today: switching to `tlsa` works, too. Unfortunately I'm not expert enough to perform further analysys. Let me know if I can help in some way. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1961701052 You are receiving

[sr-dev] Re: [kamailio/kamailio] TLS certificate decode error / ee key to small with tls_threads_mode = 1 (Issue #3764)

2024-02-26 Thread Matteo via sr-dev
@space88man seems that fixes in current 5.7 branch after #3765 makes it work, so I think this can be closed. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3764#issuecomment-1963614539 You are receiving this because you are subscribed to this th

[sr-dev] Re: [kamailio/kamailio] [pua] reginfo_increase_version does nothing (Issue #3234)

2023-12-21 Thread Matteo via sr-dev
Sure, I'll be able to test it in the very beginning of the new year, will keep you posted. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3234#issuecomment-1866982085 You are receiving this because you are subscribed to this thread. Message ID:

[sr-dev] Re: [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-07 Thread Matteo via sr-dev
a very minimal config that exposes the issue: ``` #!KAMAILIO debug=3 log_stderror=yes fork=yes auto_bind_ipv6=1 request_route { exit; } ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4098#issuecomment-2575056797 You are receiving th

[sr-dev] [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-07 Thread Matteo via sr-dev
### Description When `auto_bind_ipv6` is enabled on a system without ipv6, kamailio starts, enumerates all interfaces but does not perform no listening at all. In addition, no errors are reported, see below from final part of boot log, no other infos are logged. While this can be worked arou

[sr-dev] Re: [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-08 Thread Matteo via sr-dev
Seems a container-related stuff. Even on podman. Running the same on a standard machine w/o ipv6 enabled work as expected, even with the `auto_bind_ipv6` flag on. What happens is that the netlink message `RTM_GETADDR` with AF_INET6 type get sent correctly, but kamailio is stuck on waiting (in s

[sr-dev] Re: [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-08 Thread Matteo via sr-dev
Yup, in background I'm trying to understand, because a minimal program that do a similar thing using a netlink socket message/receive on af_inet6 works, so something is happening there. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4098#issuec

[sr-dev] Re: [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-20 Thread Matteo via sr-dev
Tried, seems to work (progress after the 4sec timeout), but bind on localhost does not happen (127.0.0.1) with the example config above. If `auto_bind_ipv6` is removed or set to `0` kam listens to all ips, even looopback ones. Not a real issue, but maybe it should work? -- Reply to this email

[sr-dev] Re: [kamailio/kamailio] auto_bind_ipv6 prevents listening also on ipv4 if system has no ipv6 (Issue #4098)

2025-01-20 Thread Matteo via sr-dev
In my case, I'm not actively disabling ipv6 on docker, but just leaving the param on the config set, regardless on how it configured docker. On Mon, Jan 20, 2025 at 3:57 PM Daniel-Constantin Mierla < ***@***.***> wrote: > I tried to simulate a no-ipv6 system by running docker with --sysctl > net.

[sr-dev] [kamailio/kamailio] auto_bind_ipv6 prevents startup when kamailio pid is 1 ( docker ) (Issue #4094)

2025-01-02 Thread Matteo via sr-dev
### Description When starting Kam inside a docker container and the `auto_bind_ipv6` option is enabled, kam fails to start, see below for error logs. Instead, inside the very same container, by executing it from a shell, it works. The difference is that starting from the entrypoint kam has pi

[sr-dev] Re: [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-11 Thread Matteo via sr-dev
xadhoom left a comment (kamailio/kamailio#4203) No load, is just a test system. the only traffic I have are dispatcher pings toward a couple of kamailios. Happens continuosly, I would say one every 20 logs line (when in debug mode) -- Reply to this email directly or view it on GitHub: https://

[sr-dev] Re: [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-16 Thread Matteo via sr-dev
xadhoom left a comment (kamailio/kamailio#4203) Ok a container with debian bookworm works as expected. So is definitely something within ubuntu noble. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4203#issuecomment-2808916586 You are receiving

[sr-dev] Re: [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-16 Thread Matteo via sr-dev
xadhoom left a comment (kamailio/kamailio#4203) Going on with my tests, those errors seems "interleaving" problems, where one thread writes to stderr while another is writing, most of the times you can see the "interrupted" line continuing after the interleaved one. This should not happen, sinc

[sr-dev] Re: [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-15 Thread Matteo via sr-dev
xadhoom left a comment (kamailio/kamailio#4203) Going on with investigation, seems that also normal logs are affected, for example: ``` 130(137) DEBUG: , "callid": "1a0c92885690f77a-264@127.0.0.1", "ts": 1744705480.227433 dispatcher [dispatch.c:3339]: ds_update_st129(136) DEBUG: , "callid": "1a

[sr-dev] Re: [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-04 Thread Matteo via sr-dev
xadhoom left a comment (kamailio/kamailio#4203) Additional infos: - logging happens over stderr: kamailio `-E` flag and `log_stderror=yes` - kamailio forked with `-DD` to have it running as pid 1 in the container -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/

[sr-dev] [kamailio/kamailio] Corrupted output with log-engine json (Issue #4203)

2025-04-04 Thread Matteo via sr-dev
xadhoom created an issue (kamailio/kamailio#4203) ### Description Enabled json logging engine, with the following setup: - kam cmd line params: `--log-engine=json:Mp` - prefix: `log_prefix=", \"callid\": \"$ci\",\"srcip\": \"$si\", \"ts\": $TV(Sn), \"method\": \"$rm\", \"mt\": $mt, \"ua\": \"$

[sr-dev] [kamailio/kamailio] wip: pua_reginfo: add helper to disable publishing for current message (PR #4253)

2025-05-22 Thread Matteo via sr-dev