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

Connection management insufficient #1

Open
grrrr opened this issue Sep 20, 2023 · 1 comment
Open

Connection management insufficient #1

grrrr opened this issue Sep 20, 2023 · 1 comment

Comments

@grrrr
Copy link
Collaborator

grrrr commented Sep 20, 2023

Currently, upon connected a stream, e.g. from RME Digiface AVB to the ALSA AVB driver, hive will show the connection, but in a "red", that is defunct state.

It seems that upon a connection request (AVB_ACMP_MSGTYPE_CONNECT_RX_CMD), the driver as a listener not only has to respond with a AVB_ACMP_MSGTYPE_CONNECT_RX_RESP response (which it does), but must also send a AVB_ACMP_MSGTYPE_CONNECT_TX_CMD command, which again should be answered with AVB_ACMP_MSGTYPE_CONNECT_TX_RESP by the talker.

In wireshark one can observe that sequence with working AVB devices using a ieee1722.subtype == 0xfc filter.

@grrrr
Copy link
Collaborator Author

grrrr commented Sep 20, 2023

Obiously, apart from the message type and the sequence id, all the data are the same between AVB_ACMP_MSGTYPE_CONNECT_RX_CMD/AVB_ACMP_MSGTYPE_CONNECT_RX_RESP and AVB_ACMP_MSGTYPE_CONNECT_TX_CMD messages.

The order, whether AVB_ACMP_MSGTYPE_CONNECT_TX_CMD or AVB_ACMP_MSGTYPE_CONNECT_RX_RESP is sent first, doesn't seem to matter.

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

No branches or pull requests

1 participant