ClientOriginIPAddress is 0.0.0.0 or ""

[Jun-Lin Chen (陳俊霖)]

Hi,
If continously send POST sessions Redfish request via Postman. I observe bmcweb debug logs, it will established connection at first request then not fetch user ip after the second request.

That's why ClientOriginIPAddress in session after the second created is always 0.0.0.0 (not be assigned).

In HTTP 1.1 It uses keep-alive Header default. so BMC does not fetch user IP when its connection is established.

Is this behavior we expect?

Best regards,
Jun-Lin Chen

From: Jun-Lin Chen (陳俊霖)
Sent: Friday, March 5, 2021 4:05 PM
To: sunharis at in.ibm.com
Cc: openbmc at lists.ozlabs.org
Subject: ClientOriginIPAddress is 0.0.0.0 or ""

Hi Sunitha,

I found some problem when I create session.
The property “ClientOriginIPAddress” is “” after POST https://${bmc}/login<https://$%7bbmc%7d/login> -d '{"username": <>,"password": <>}
And it is 0.0.0.0 after POST https://${bmc}/redfish/v1/SessionService/Sessions<https://$%7bbmc%7d/redfish/v1/SessionService/Sessions> -d '{"username": <>,"password": <>}'
Both of them looked like something wrong. And I also look for source code in bmcweb repository.
There only defined the default value: “” in generateUserSession() and not found fetch user ip in elsewhere.
I think it is why ClientOriginIPAddress is strange.

May I ask what step or something I lack in creation session so this property is abnormal?


Best regards,
Jun-Lin Chen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210318/adc2b855/attachment.htm>