This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/23814 ) Change subject: osmo-bts-trx: set don't-fragment flag on all TRXD packets ...................................................................... Patch Set 5: > If you enable the DF bit, you are actively breaking existing situations that are working for the user (with fragmentation overhead). or to be more precise: If you want to enable DF, then you have to implement [in your application] some path-mtu-discovery to dynamically at runtime detect the MTU and then scale your UDP payload sizes to stay below it. In the absence of this, one could possibly introduce a VTY parameter. In the end, as stated above, over loopback it doesn't matter. -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/23814 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: I25415b76b69ccf43f83ddfb0e7dd1e330fb23aa7 Gerrit-Change-Number: 23814 Gerrit-PatchSet: 5 Gerrit-Owner: fixeria <vyanitskiy at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Tue, 26 Oct 2021 15:25:25 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211026/4a7142e2/attachment.htm>