Revision history [back]
Reject-Message-To-Network
Hi all, I have an interesting case and I have no idea how to solve it and couldn't find something in the forum. Maybe on of you can help me?
- I have a controller BACnet/IP (172.16.50.50)
- There is a "Gateway" from Samsung which connects the IP world somehow with another bus system (looks like IP based also but somehow proprietary => 172.16.50.2)
Now I see from time to time "Reject-Message-To-Network" messages on the IP but I have no idea why. I am even not sure who is rejecting this message. Is it the source of this telegram which would be the controller BACnet/IP or is it the Gateway or somebody else?
Further, the reject reason is mentioned with "Other error (0)". So it is quite useless since there are no details available. Does somebody knows more about this behavior?
EDIT: I have copied 2 traces. "NoRejectMessage.pcapng" shows when communication works and the controller is able to subscribe. The trace "RejectMessage.pcapng" shows just a few minutes/hours later the reject message. After that, communication does not work anymore and no COV updates are visible anymore...
Reject-Message-To-Network
Hi all, I have an interesting case and I have no idea how to solve it and couldn't find something in the forum. Maybe on of you can help me?
- I have a controller BACnet/IP (172.16.50.50)
- There is a "Gateway" from Samsung which connects the IP world somehow with another bus system (looks like IP based also but somehow proprietary => 172.16.50.2)
Now I see from time to time "Reject-Message-To-Network" messages on the IP but I have no idea why. I am even not sure who is rejecting this message. Is it the source of this telegram which would be the controller BACnet/IP or is it the Gateway or somebody else?
Further, the reject reason is mentioned with "Other error (0)". So it is quite useless since there are no details available. Does somebody knows more about this behavior?
EDIT: I have copied 2 traces. "NoRejectMessage.pcapng" shows when communication works and the controller is able to subscribe. The trace "RejectMessage.pcapng" shows just a few minutes/hours later the reject message. After that, communication does not work anymore and no COV updates are visible anymore...
Reject-Message-To-Network
Hi all, I have an interesting case and I have no idea how to solve it and couldn't find something in the forum. Maybe on of you can help me?
- I have a controller BACnet/IP (172.16.50.50)
- There is a "Gateway" from Samsung which connects the IP world somehow with another bus system (looks like IP based also but somehow proprietary => 172.16.50.2)
Now I see from time to time "Reject-Message-To-Network" messages on the IP but I have no idea why. I am even not sure who is rejecting this message. Is it the source of this telegram which would be the controller BACnet/IP or is it the Gateway or somebody else?
Further, the reject reason is mentioned with "Other error (0)". So it is quite useless since there are no details available. Does somebody knows more about this behavior?
EDIT:
Somehow I have copied 2 traces. "NoRejectMessage.pcapng" shows when communication works and the controller is am not able to subscribe. The upload the WireShark trace "RejectMessage.pcapng" shows just a few minutes/hours later the reject message. After that, communication does not work anymore and no COV updates are visible anymore...
link texthere...