-
Notifications
You must be signed in to change notification settings - Fork 22
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
"Invalid PVA header 16" / "Bad request ... CA 01 00 16" #135
Comments
It look like somehow |
As background:
The idea (as I understand it) is to allow unicast UDP search to "just work" for hosts with multiple PVA servers, without having to manually manage TCP port numbers. The only (as yet hypothetical) problem which I know of with this idea is that it will cause both sides of a PVA gateway to see unicast searches or beacons from either sides. redirection on the server side: pvAccessCPP/src/server/responseHandlers.cpp Lines 290 to 301 in f84774e
redirection on the client side: pvAccessCPP/src/remoteClient/clientContextImpl.cpp Lines 2661 to 2677 in 31261ce
Handling in UDP receiver common to both client and server:
|
pvAccessCPP/src/server/responseHandlers.cpp Lines 161 to 164 in f84774e
|
Log files at SLAC have been filling up with:
Note that "header 16" is really 0x16.
The text was updated successfully, but these errors were encountered: