From: Sunitha Harish <sunithaharish04@gmail.com>
To: "Ed Tanous" <ed@tanous.net>,
"Jun-Lin Chen (陳俊霖)" <Jun-Lin.Chen@quantatw.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: ClientOriginIPAddress is 0.0.0.0 or ""
Date: Fri, 9 Apr 2021 11:21:52 +0530 [thread overview]
Message-ID: <d9176b8e-1944-e654-baea-81064f195d35@gmail.com> (raw)
In-Reply-To: <CACWQX81k7NO-+8OyPhAbk9BNfB58xuK13RvHhG4m-G+nDHPniA@mail.gmail.com>
On 06-04-2021 22:21, Ed Tanous wrote:
> On Tue, Mar 23, 2021 at 3:28 PM Jun-Lin Chen (陳俊霖)
> <Jun-Lin.Chen@quantatw.com> wrote:
>> 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
>
> Sunitha,
> Considering this is code you wrote, would you mind replying to Jun-Lin
> about his experience and what the expected behavior is? For what it's
> worth, I've seen it report 0.0.0.0 before on my system, I just haven't
> had a chance to chase it down and debug it.
>
> -Ed
Hi Jun-Lin,
The ClientOriginIPAddress is expected to get populated when the session
is established to the BMC ( the first request). This is a one time
fetch, and it will be persisted for that session.
Regards,
Sunitha
>>
>>
>> From: Jun-Lin Chen (陳俊霖)
>> Sent: Friday, March 5, 2021 4:05 PM
>> To: sunharis@in.ibm.com
>> Cc: openbmc@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 -d '{"username": <>,"password": <>}
>>
>> And it is 0.0.0.0 after POST https://${bmc}/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 prev parent reply other threads:[~2021-04-09 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 8:05 ClientOriginIPAddress is 0.0.0.0 or "" Jun-Lin Chen (陳俊霖)
2021-03-18 6:23 ` Jun-Lin Chen (陳俊霖)
2021-04-06 16:51 ` Ed Tanous
2021-04-09 5:51 ` Sunitha Harish [this message]
2021-04-09 14:58 ` Ed Tanous
2021-04-16 13:42 ` Ivan Mikhaylov
2021-04-16 14:57 ` Ed Tanous
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9176b8e-1944-e654-baea-81064f195d35@gmail.com \
--to=sunithaharish04@gmail.com \
--cc=Jun-Lin.Chen@quantatw.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).