Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79406 - [n2n] n2n federation not working properly

Attached to Project: Arch Linux
Opened by bbaa (bbaa) - Friday, 18 August 2023, 07:06 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
federation not working properly

Additional info:
* package version(s)
n2n 3.1.1-2

Steps to reproduce:
Running n2n federation supernode on two hosts

Host 1 (10.0.1.1)
supernode -p 12345 -l 10.0.1.2:12345 -F test -vvvv -f

Host 2 (10.0.1.2)
supernode -p 12345 -l 10.0.1.2:12345 -F test -vvvv -f

Federation can't be created properly.
Will continue to receive time_stamp_verify_and_update found a timestamp out of allowed frame error.
Using a source code rebuild package seems to solve this problem.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:19 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/n2n/issues/1
Comment by bbaa (bbaa) - Friday, 18 August 2023, 07:07 GMT
Host 2 (10.0.1.2)
supernode -p 12345 -l 10.0.1.1:12345 -F test -vvvv -f
Comment by Toolybird (Toolybird) - Saturday, 19 August 2023, 06:56 GMT
> Using a source code rebuild package seems to solve this problem.

Please always specify *exactly* how you did the rebuild. Did you use a clean chroot as per [1]? This is important because a plain `makepkg' will likely end up using different build flags and 1 of these flags could be the root cause of the problem.

[1] https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
Comment by bbaa (bbaa) - Saturday, 19 August 2023, 15:24 GMT
I tried to build using the extra-x86_64-build help script.
The built package reproduces the same error as the package in the repository.
But I can't confirm that it's that package in my environment that's causing the problem.
Comment by bbaa (bbaa) - Saturday, 19 August 2023, 16:11 GMT
It seems that lto breaks the n2n timestamp.
I added the following option to PKGBUILD
options=(!lto)
and built again with extra-x86_64-build and the problem disappeared
Comment by Toolybird (Toolybird) - Saturday, 19 August 2023, 22:14 GMT
> It seems that lto breaks the n2n timestamp.

As suspected. Please report this problem upstream.

Loading...