sr-dev June 2022

sr-dev@lists.kamailio.org

20 participants
281 discussions

[kamailio/kamailio] Path MTU discovery for IPv6 (PR #3141)

by vanrein

#### Pre-Submission Checklist - [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [X] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [X] Small bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches (no, it is a requirement to use UDP/IPv6 with everyone) - [X] Tested changes locally (same results as before with the Kamailio test framework) - [ ] Related to issue #3119 #### Description The IPv6 support for Path MTU discovery is absent, but IPv6 has no DF flag to allow downstream fragmentation. See Issue #3119 for my discovery / learning path. In short, unconnected UDP sockets do not learn Path MTU problems, so a message dropped once will be dropped again on resend. Using `IPV6_PMTUDISC_WANT`, any knowledge in the kernel can be used to fragment the message at sending time, as intended for IPv6. These patches actually correct two IPv6-related things in the `core/udp_server.c`, 1. Benefit from any kernel knowledge about Path MTU for IPv6 2. The same option to learn from UDP_ERRORS is now available for IPv6 Do note that the last has not been implemented for IPv4 or IPv6. It is more useful for IPv6, allowing instant "tm" resends for Path MTU, but not "sl" I think. I cannot do that work, but this brings IPv6 to the same level as IPv4. ``` commit 0f90cff05c1a448eb2f85f83b4c087ab32ede11 Author: Rick van Rein <rick(a)openfortress.nl> Date: Sat Jun 11 10:57:32 2022 +0000 core: Issue 3119. Handling ICMPv6 Packet too Big - This was only defined for IPv4 under flag UDP_ERRORS - IPv6 has no toggle DF to clear for en-route fragmentation - Kamailio currently does not collect with recvmsg(...,MSG_ERRQUEUE) - The benefits of adding that can be instant resends for "tm" messages - Note that "sl" messages will have been forgotten at this point commit 6b404b5f9807174177bee36eaf3543be0794f55e Author: Rick van Rein <rick(a)openfortress.nl> Date: Sat Jun 11 10:44:27 2022 +0000 core: Issue #3119. Path MTU kernel info for IPv6 - For IPv4, DF is an option; for IPv6 it is always active - This makes pmtu_discover an IPv4-only option - This means that we should set IPV6_MTU_DISCOVER to IPV6_PMTUDISC_WANT - Unconnected UDP sockets can now learn from ICMPv6 "Packet too Big" - As a result, hitting a Path MTU upper bound is a learning process - This should stop consistent SIP packet drops due to Path MTU ``` You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3141 -- Commit Summary -- * core: Issue #3119. Path MTU kernel info for IPv6 * core: Issue 3119. Handling ICMPv6 Packet too Big -- File Changes -- M doc/misc/NEWS (2) M src/core/udp_server.c (44) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3141.patch https://github.com/kamailio/kamailio/pull/3141.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3141 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3141(a)github.com>

2 years, 4 months

[kamailio/kamailio] [stirshaken] add identity header in reply messages or to a separate variable (#2770)

by sergei lavrov

### Description I'm unable to add the generated `Identity` value to reply message when `kamailio` acts as a redirect server and replies with `302 Moved Temporarily` instead of relaying `INVITE`. This code doesn't work, i.e. no `Identity` header in `302 Moved Temporarily` message: ``` if (stirshaken_add_identity($var(x5u), $var(attest), $var(origtn_val), $var(desttn_val), $var(origid)) == 1) { append_branch("sip:$rU@127.0.0.1:6060"); sl_send_reply("302", "Moved Temporarily"); exit; } ``` ### Expected behavior It would be nice if the `stirshaken_add_identity_*` functions would add the generated `Identity` header to the reply messages too, or store the generated `Identity` header in a separate variable, like `$identity`, for the future processing. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2770

2 years, 4 months

[kamailio/kamailio] secfilter: Wrong format on RPC response data (Issue #2992)

by Olle E. Johansson

secfilter RPC functions to get statistics use a console format to printing data, suitable for **kamcmd** but not for any RPC method. This should be converted to a machine-parsable data structure (much like dispatcher, usrloc and htable data dumps). -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2992 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2992(a)github.com>

2 years, 4 months

[kamailio/kamailio] Add 5.6 branch packages for Ubuntu 22.04 (Issue #3147)

by compuwizz

Is it possible to add the 5.6 branch deb/ubuntu packages to https://deb.kamailio.org/ for Ubuntu 22.04? I see Ubuntu 22.04 native repos have kamailio 5.5 in them but I'd like to use 5.6. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3147 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3147(a)github.com>

2 years, 4 months

Releasing v5.6.1

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.6.1 (out of branch 5.6) on Wednesday, July 6, 2022 -- in about 1 week and a half from now. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online: June 20-23, 2022 * https://www.asipto.com/sw/kamailio-advanced-training-online/

2 years, 5 months

(Off-topic) Vienna, meeting

by Henning Westerholt

(Off-topic) Hello, In about two weeks I will be a few days in Vienna (12h - 14th July). If you want to meet for a drink to chat about Kamailio and other topics, just contact me off-list. Thanks, and regards, Henning

2 years, 5 months

[kamailio/kamailio] Location for git submodules in the source tree (Issue #3164)

by Daniel-Constantin Mierla

With the introduction of an external project reference via git submodule by `tls_wolfssl`, I am opening this to discuss where it would be the _best_ place for them. Now it is in the folder of the tls_wolfssl module, but I noticed that many projects have a dedicated folder like `vendor` (or `extern`, `import`), and I would somehow that approach more because it is easier to locate the external code and figure out its implications in licensing, dependencies, etc ... Moreover, it can happen that many modules would need to use that external project/repo. For example, now crypto uses libssl, but for someone that wants to get rid of it and use only libwolfssl may contribute an alternative of that module. Then two modules would need same external repo and having it inside another module would not be straightforward to manage. Given the above, I would suggest to place them in a folder like `misc/vendor` or similar inside the `misc/` directory, not to get back into growing the root folder. I would like to keep `src/` folder only for Kamailio specific code. If someone has other suggestions, propose them in comments and let's try to get to a decision soon. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3164 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3164(a)github.com>

2 years, 5 months

Jenkins build became unstable: kamailio56-nightly-binaries » amd64,bookworm #16

by kamailio＠sipwise.com

See <https://kamailio.sipwise.com/job/kamailio56-nightly-binaries/architecture=a…>

2 years, 5 months

Jenkins build became unstable: kamailiodev-nightly-binaries » amd64,bookworm #2221

by kamailio＠sipwise.com

See <https://kamailio.sipwise.com/job/kamailiodev-nightly-binaries/architecture=…>

2 years, 5 months

[kamailio/kamailio] Errormessage TLS read:error:0D0E10DF:asn1 encoding routines:asn1_get_uint64:too large (Issue #3168)

by MartinPalmAGDS

We use Kamilio as a proxy server to connect softphones to our PBX systems. We have run into some TLS problems. These problems result in a shut down of the TLS connection after the error is encountered. We have looked into serial numbers of certificates. The current code in kamailio seems to be broken due to changes in the world around... many certificates today do not adhere to the previously assumed behaviour of certificate serial numbers anymore. The error which causes the connection to drop seems to be related to a comparison of the certificate serial numbers during renegotiation. tls_err_ret(): TLS read:error:0D0E10DF:asn1 encoding routines:asn1_get_uint64:too large Kamailio expects serial numbers to fit in a 64 bit unsigned, however during the last years, starting around 2003 more and more systems use automatically generated serial numbers, which are frequently 128 bit long. The serialnumber of our own Auerswald root certificate looks to be only 64 bit long, but during the negotiation is presented as 9 bytes starting with 00h, which is interpreted as a 72bit value. Trying to put this serial number in a 64 bit long kills the connection. Due to the different ways that are used to generate serial numbers now, there is no simple algorithm to condense the number into a 64bit value, and the whole number should be compared to see if it is same or higher. We currently have disabled renegotiation to avoid the connection being dropped during renegotiation. Which however can lead to the connection being dropped by the other side during renegotiation, but this is not a good permanent workaround! #### Reproduction This issue happens infrequently ### Possible Solutions No workaround possible on our side ### Additional Information Kamailio Version 5.5.4 LibSSL 1.1.1.n * **Operating System**: Linux, Debian oldstable -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3168 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3168(a)github.com>

2 years, 5 months

← Newer
1
...
8
9
10
11
12
13
14
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2022