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

Getting Error: Cloud not read open message due to buffer having less bytes than open message size #93

Open
Hekkel opened this issue Dec 12, 2021 · 0 comments

Comments

@Hekkel
Copy link

Hekkel commented Dec 12, 2021

Hello, I'm trying to connect BMP with a CoreEMU instance.
Everything looks fine until I start getting events, then I get this error

2021-12-12T22:09:31.513341 | INFO     | runServer          | Accepted new connection; active connections = 2
2021-12-12T22:09:31.513381 | INFO     | runServer          | Client Connected => 192.168.0.116:57276, sock = 10
2021-12-12T22:09:34.619630 | INFO     | ClientThread       | Thread started to monitor BMP from router 192.168.0.116 using socket 10 buffer in bytes = 314572800
2021-12-12T22:09:34.619769 | INFO     | ReadIncomingMsg    | 192.168.0.116: Init message received with length of 24
2021-12-12T22:09:34.619807 | INFO     | handleInitMsg      | Init message type 1 and length 13 parsed
2021-12-12T22:09:34.619811 | INFO     | handleInitMsg      | Init message type 1 = FRRouting 7.3
2021-12-12T22:09:34.619813 | INFO     | handleInitMsg      | Init message type 2 and length 3 parsed
2021-12-12T22:09:34.619815 | INFO     | handleInitMsg      | Init message type 2 = n47
2021-12-12T22:09:34.619822 | INFO     | hashRouter         | Router ID hashed with hash_type: 1
2021-12-12T22:09:34.619824 | INFO     | ReadIncomingMsg    | Router ID hashed with hash_type: 1
2021-12-12T22:09:34.619897 | INFO     | ReadIncomingMsg    | 192.168.0.116: PEER UP Received, local addr=10.0.3.2:45824 remote addr=10.0.3.1:36508
2021-12-12T22:09:34.619910 | WARN     | parseOpenMsg       | 10.0.3.1: Cloud not read open message due to buffer having less bytes than open message size
2021-12-12T22:09:34.619912 | ERROR    | handleUpEvent      | 10.0.3.1: rtr=192.168.0.116: Failed to read sent open message
2021-12-12T22:09:34.619928 | INFO     | ReadIncomingMsg    | 192.168.0.116: Caught: Failed to read open message
 

As you can see in the logs I configured the buffers using persistant config with 300Mb (tried with 8,16,32....all the way up to 300mb) but I'm still getting that error message, which by the way has a typo: Cloud -> Could.

Any ideas/suggestions what I'm doing wrong?
Thanks in advance.

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