Good call. It is stored the same way, thanks! -Travis
On 2/7/2022 11:20 AM, Frey, Rick E wrote:
I’m using memfile (CSV) for leases so not sure if format differs from
SQL, but CSV format for user_context field is JSON with attribute name
of “relay-agent-info” and the value is entire option 82
I’m using memfile (CSV) for leases so not sure if format differs from SQL, but
CSV format for user_context field is JSON with attribute name of
“relay-agent-info” and the value is entire option 82 hex value as sent over
wire. Assuming SQL value is same, you could parse hex value into sub
Is there a delimiter or a way to pull the sub-option 2 from option 82
when it is stored in the user context through the store-extended-info
flag? I am using sql for storing leases. So far I do not see a
delimiter, I just see the two sub-options merged together and then stored.
Does anyone
Maria Hrabosova writes:
> 2022-02-03 08:05:04.134 INFO [kea-ctrl-agent.http/7518.139986295949504]
> HTTP_CONNECTION_HANDSHAKE_FAILED TLS handshake with 192.168.1.42 failed
> with no shared cipher
The "no shared cipher" error from OpenSSL can come from many reasons but
all are about
