Is there any plan to introduce tightvnc into openbmc

Is there any plan to introduce tightvnc into openbmc

[常晓明]

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]

Hi，All,


Is there any plan to introduce tightvnc into openbmc ?




Johny

[-- Attachment #2: Type: text/html, Size: 283 bytes --]

ipmid-new.cpp log<level::ERR> entry cannot output

[常晓明]

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Hi, Team,


phosphor-ipmi-host/ipmid-new.cpp has lot log<level:ERR>("Something messages",  entry("CHANNEL=%u", channel))
But journalctl just saves "Something messages" , cannot save the message of entry("CHANNEL=%u", channel).


Does anybody know this?


Johny

[-- Attachment #2: Type: text/html, Size: 504 bytes --]

Re: ipmid-new.cpp log<level::ERR> entry cannot output

[Alexander A. Filippov]

On Thu, Dec 19, 2019 at 04:59:35PM +0800, 常晓明 wrote:
> Hi, Team,
> 
> 
> phosphor-ipmi-host/ipmid-new.cpp has lot log<level:ERR>("Something messages",  entry("CHANNEL=%u", channel))
> But journalctl just saves "Something messages" , cannot save the message of entry("CHANNEL=%u", channel).
> 
> 
> Does anybody know this?

Try `journalctl --output verbose`

> 
> 
> Johny

Why the journal log records IPv6(::ffff:127.0.0.1) not IPv4(127.0.0.1)

[常晓明]

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

Hi, Team,


I enabled the "/xyz/openbmc_project/logging/rest_api_logs" and add the patch code as followed,  the journal log does not record IPv4(10.0.2.2) but IPv6(::ffff:10.0.2.2) .


Does anybody know why?


if constexpr (std::is_same_v<Adaptor,
                                         boost::beast::ssl_stream<
                                             boost::asio::ip::tcp::socket>>)
            {
                boost::system::error_code ec;
                auto remoteEnd = adaptor.next_layer().remote_endpoint(ec);
                if (!ec)
                {
                    req->remoteIp = remoteEnd.address().to_string();
                }
            }
            else
            {
                boost::system::error_code ec;
                auto remoteEnd = adaptor.remote_endpoint(ec);
                if (!ec)
                {
                    req->remoteIp = remoteEnd.address().to_string();
                }
            }


Many Thx
Johny




 

[-- Attachment #2: Type: text/html, Size: 5019 bytes --]

Re: Why the journal log records IPv6(::ffff:127.0.0.1) not IPv4(127.0.0.1)

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

On Thu, Feb 20, 2020 at 04:25:48PM +0800, 常晓明 wrote:
> Hi, Team,
> 
> 
> I enabled the "/xyz/openbmc_project/logging/rest_api_logs" and add the patch code as followed,  the journal log does not record IPv4(10.0.2.2) but IPv6(::ffff:10.0.2.2) .

That IPv6 address is the same as the IPv4 address, just in IPv6 format.

https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4

Generally, applications that support IPv6 don't [need to] know if they are
being connected to by an IPv4 or IPv6 end-point.  This is how the Linux
networking stack handles IPv6.  When the application indicates it
supports IPv6, the network stack will give it IPv6-formatted addresses
even for IPv4 connections.  This is what you're seeing here.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]