Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reject-Message-To-Network single octet as uint8, then the network number parameters as uint16 #13

Open
duffy-ocraven opened this issue Aug 25, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@duffy-ocraven
Copy link

duffy-ocraven commented Aug 25, 2020

Reject-Message-To-Network differs from the other Network Layer messages, that it has as its parameters first: a reject reason single octet as uint8. Then the network number parameters (each is uint16) until the UDP/BVLC-Length.

http://www.bacnet.org/Addenda/Add-135-2010ao.pdf page 5 documents the 7 defined values of the reject reason single octet. Don't worry about understanding code value 5: "source message was rejected due to a BACnet security error and that error cannot be forwarded to the source device. See Clause 24.12.1.1 for more details on the generation of Reject-Message-To-Network messages indicating this reason." The entirety of clause 24 has subsequently been removed from the standard.

@NothinRandom NothinRandom self-assigned this Aug 25, 2020
@NothinRandom NothinRandom added the enhancement New feature or request label Aug 31, 2020
@NothinRandom
Copy link
Contributor

@duffy-corelight, latest update addresses this issue. Like the others, I'll let the customer close the issue if deemed as satisfied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants