ticket	summary	component	version	milestone	type	owner	status	created	_changetime	_description	_reporter
213	BNC 2.13.4 macOS build blocked by Gatekeeper and crashes due to invalid code signature (Code 2, CODESIGNING)	BNC	BNC 2.2		defect	stuerze	new	2026-02-14T15:10:22+01:00	2026-05-19T12:02:28+02:00	"Dear BNC Development Team,
I would like to report an issue with the macOS build of BNC 2.13.4.
On macOS 26.3 (Apple Silicon, M2), the application initially shows the system warning:
“bnc.app is damaged and can’t be opened. You should move it to the Trash.”
After manually removing the quarantine attribute, the application no longer shows the “damaged” message, but it immediately crashes on launch with:

Termination Reason: Namespace CODESIGNING, Code 2
Exception Type: SIGKILL (Code Signature Invalid)
The crash report also shows the bundle identifier as:
com.yourcompany.bnc

As a temporary workaround, I was able to run the application by re-signing it locally using:
codesign --force --deep --sign - /Applications/bnc.app

After applying an ad-hoc signature, the application launches and runs normally.
It appears the distributed macOS build may not be properly signed and/or notarized. On current macOS versions, this results in Gatekeeper blocking the application and the system terminating the process at launch.
Could you please confirm whether the macOS build is intended to be signed and notarized for distribution?
Best regards,
Arda Yeşil"	ardayesil@…
201	Connect BKG NtripCaster to LDAP using LDAP authentication	Professional Caster			defect	stoecker	new	2025-03-06T13:54:40+01:00	2025-03-11T11:13:31+01:00	"Dear BKG team,

We are trying to integrate our BKG NtripCaster V2.0.47 with an LDAP server using simple LDAP authentication (i.e. providing the bind DN and bind password) but we don't know if the BKG supports the LDAP bind authentication and in this case how to configure it. We have tried several options using the configuration ldap parameters included in the ntripcaster.conf but we couldn't make it work.

For us this is relevant as, due to cybersecurity constraints, the anonymous access to the LDAP server is not permitted and we need to integrate our external caster with a LDAP directory for managing the access of external users to our Galileo Ntrip service.

Thank you in advance!!
Jorge
"	jrocamora@…
206	BNC for IPAD	Other			defect	wiese	assigned	2025-04-16T07:16:52+02:00	2026-05-19T12:01:35+02:00	is there a BNC that will run on Apple IPAD from what i can tell there is none on the download page. Thanks	nick.townsend@…
218	Technical Support: High RAM usage/data drop issues and mountpoint relay failures in BNC 2.13.2+	BNC			defect	stuerze	new	2026-05-26T13:23:57+02:00	2026-06-17T16:47:55+02:00	"Dear BKG BNC Support Team,
We are currently encountering two critical issues after upgrading from BNC version 2.13.1, and we would appreciate your guidance or any suggestions you can provide.
**Environment Details:**
**OS / Environment:** Ubuntu 24.04 running inside Docker containers.
**Execution:** We run BNC in no-window mode using the -nw option (generally launched as /opt/bnc-[version] -nw -conf BNC.ini).
**Working Version:** 2.13.1 (and v2.13.2 for the relay feature)
**Problematic Versions:** 2.13.2 & 2.13.4 (RAM issue) / 2.13.4 (Relay issue)
**Server Specs:** Tested across multiple environments, including a 256 GB RAM / HDD setup.

**Issue 1:** High RAM Usage and Data Drops (v2.13.2 & v2.13.4)
When running BNC 2.13.2 and 2.13.4, the application begins to ignore incoming data, and its RAM usage climbs exponentially—reaching up to 100 GB on our 256 GB machine.
Here is some information regarding this:
We do not experience this issue in Version 2.13.1 under the exact same load.
We initially thought this might be related to HDD disks not handling the I/O load, but version 2.13.1 works perfectly with the exact same HDD setup.
We have replicated this RAM issue across different machines running the same Ubuntu 24.04 Docker setup.
While it happens consistently with a large number of mountpoints, we have also occasionally experienced it when testing with a low number of mountpoints.
The issue appears significantly more likely to happen if the casters are accessed via a secure port (e.g., 443, 2102).
Has there been a change in how BNC handles internal queuing, threading, or secure port connections in no-window mode within these newer versions that could account for this memory accumulation?

**Issue 2:** Mountpoint ""Relay"" Feature in v2.13.4
In version 2.13.1, we successfully used BNC to relay a specific mountpoint to an internal service. Our configuration relied primarily on the following options:
mountPoints
casterPort
miscMount
miscPort
This setup allowed a downstream service (for example, running str2str -in tcpcli://my_server:port/MOUNTPOINT) to successfully listen to and consume the relayed mountpoint.
As of version 2.13.4, this functionality has stopped working for us.
The incoming data works and can be seen in a file if the outFile option is used
Could you please indicate if there was a change to how miscPort / casterPort broadcasting is handled in the latest release, or if we need to adjust our configuration format to achieve the same result?
We would be happy to provide our configuration files (BNC.ini) or bnc log outputs if that helps diagnose the issue. Looking forward to your insights.

Many thanks for the help in advance,

Best regards,"	altmb297@…
222	"Fresh installation and repair of BNC 2.13.6 Windows MSI did not resolve the 'Qt Library compiled without QT_WEBENGINE' error in PPP(4) → Open Map."""	Other			defect	stuerze	new	2026-07-30T20:09:09+02:00	2026-07-30T20:09:09+02:00	"BNC version: 2.13.6 Windows MSI

Action:
PPP(4) -> Open Map

Error:
Qt Library compiled without QT_WEBENGINE

Notes:
Fresh install from official Windows MSI.
Repair installation performed.
Same error persists."	R
170	structured logging	BNC			enhancement	stuerze	new	2023-12-07T09:11:23+01:00	2023-12-07T09:11:23+01:00	"Currently the logfiles are not easy to parse, as they are not structured. Nowadays the logs are often JSON formated or key=value pairs separated by spaces.
JSON example line: {{{{""level"":""debug"",""time"":""2023-12-07T08:03:47.162"",""sender"":""SCP"",""message"":""executed command \""/usr/local/bin/myHooks\"", elapsed: 1.007732187s, error: <nil>""}}}}

To facilitate the monitoring purposes with BNC, this should be introduced.
To discuss: 
- as new log to not break existing workflows?
- new log with metrics only?
- write to port instead of file?
- ...

See #168 and #108."	wiese
196	Users.aut modification	Professional Caster			enhancement	stoecker	new	2025-02-07T14:54:18+01:00	2025-05-14T15:08:51+02:00	"Hi,

We are currently working on a project based on your Professional Caster and have a question regarding the users.aut configuration file. 

From our understanding reading the manual, adding N users does not require a restart of the caster since a rehash can be commanded; however, editing a username or removing an existing user are actions that require this restart.

Is it possible to not restart the Caster after a user has been removed for the change to take place? In case that the current version does not allow it, is this a functionality planned to be included in the future?

Thanks in advance!
"	mvargasp
210	"help on ""14_SaveSp3.bnc"""	BNC			task	stuerze	reopened	2025-05-30T00:00:21+02:00	2026-07-17T01:52:33+02:00	"HI,

This is a question that I need help with BNC 2.13.2.
I wanted to save corrections to SP3 file in CoM, and I'm using example config file ""14_SaveSp3.bnc"".
My question is that the example is using APC correction ""SSRA00BKG1"", so BNC is using ""igs20.atx"" to convert orbits to CoM?
What if I use CoM correction ""SSRC00BKG1"", and still check the ""CoM"" box, will BNC try to convert orbits to CoM again? (which will be wrong)

Best Regards,
Gary"	garyli@…