incoming connection counts seems unrealistic and doesn't match system

[Gingeropolous]

Height: 2969840/3354567 (88.5%) on mainnet, not mining, net hash 2.08 GH/s, v16, 12(out)+11172(in) connections, uptime 4d 7h 49m 27s

ss -tn | grep ":18080" | wc -l 
665

so the daemon reports 11k inc cnxns, but the system reports 665 on port 18080. This is a seed node, so it doesn't have a in-peers limit set (just whatever the default is, which I think is unlimited?) Also has dns blocklist and the file

[selsta]

How quickly does it rise to such an amount when you restart? and also does this happen with releae-v0.18 branch and v0.18.3.4`?

[Gingeropolous]

this is with release-v0.18 , with 9740 pulled in (shouldn't matter tho), and its still synchronizing.

this is the current output of status:

Height: 2993884/2993884 (100.0%) on mainnet, not mining, net hash 3.31 GH/s, v16, 10(out)+11653(in) connections, uptime 4d 17h 1m 29s

so about 500 was added in 10 hours.

lemme restart and see how quickly it goes up. i'll also test with 18.3.4

[Gingeropolous]

release w/ 9740, 11 mins

Height: 2994324/3354892 (89.3%) on mainnet, not mining, net hash 2.90 GH/s, v16, 12(out)+30(in) connections, uptime 0d 0h 11m 22s

41 mins
Height: 2995604/3354906 (89.3%) on mainnet, not mining, net hash 3.19 GH/s, v16, 12(out)+98(in) connections, uptime 0d 0h 41m 51s

6.5 hours:
Height: 3011432/3355094 (89.8%) on mainnet, not mining, net hash 2.63 GH/s, v16, 12(out)+714(in) connections, uptime 0d 6h 36m 39s
ss -tn | grep ":18080" | wc -l
249

[Gingeropolous]

now after 3 days,

Height: 3118316/3357753 (92.9%) on mainnet, not mining, net hash 2.07 GH/s, v16, 7(out)+5998(in) connections, uptime 3d 23h 35m 35s

whereas,

ss -tn | grep ":18080" | wc -l
641

[vtnerd]

What os/distro? What is the Boost version in use?

[Gingeropolous]

Description: Ubuntu 22.04.5 LTS

#define BOOST_LIB_VERSION "1_74"