Hi Martin,
Sorry, it can be confusing to new folks.
With 99% of IPMI over LAN, the communication is always through port 623.
With SOL, it can be slightly different. The series of events is:
1. Client connects to server/BMC over port 623.
2. Client authenticates w/ server/BMC.
3. server/BMC informs client what port to communicate for SOL.
4a. If server/BMC tells client to use port 623, SOL session continues
under the current connection/session
4b. If server/BMC tells client to use port XXX, client should
disconnect and reconnect under port XXX.
To my knowledge, the disconnect/reconnect under non-port-623 is not
supported in ipmitool. If this is happening with your motherboard, it
would explain your problem.
Al
On Fri, 2011-12-30 at 08:06 -0800, Martin Hamant wrote:
> I'm lost.
> Let me formulate what I understand:
>
> ipmitool is a tool to connect to any (most?) baseboard management
> controller, to get/set system settings.
> ipmitool with default settings connects on port 623/UDP
>
> This was the easiest part :D And to this point all is going well WITH or
> without PNAT (I can use "chassis" commands etc)
>
> now SOL. Something different is happening when ipmitool ask a SOL
> session. (thru lanplus interface)
>
> Do I have to understand that ipmitool "sol" arg simply doesn't take the
> given command line "-p <port>" arg into account ?
>
>
> I tried to read IPMI specification but I have to say this is a little
> complex to eat it like this, at least for me :)
>
> If someone can briefly explain me what's happen when asking a SOL
> session thru IPMI (what is "this" trying to connect to "that", on which
> (random) port)
>
>
> Maybe I could find a workaround then (other than SOLProxy ^^ ) to get to
> my BMC interface / console redirection from the internet
>
> Thanks again !!
>
> -
>
> Le 30/12/2011 16:41, Al Chu a écrit :
> > I think this is what Hank is talking about. SOL connects at port 623,
> > but it may communicate over a different port later in the session.
> >
> > However, ipmitool doesn't support communication over any port other than
> > 623. So if SOL works for you w/o port forwarding, then this isn't your
> > issue.
> >
> > Al
> >
> > On Fri, 2011-12-30 at 04:27 -0800, Martin Hamant wrote:
> >> Hi Hank,
> >>
> >> Thanks for you reply, but I'm still not sure we speak about the same
> >> thing :/
> >>
> >> I also have discovered in ipmi_sol.c / ipmitool :
> >>
> >> (...)
> >> /* NOTE: the spec does allow for SOL traffic to be sent on
> >> * a different port. we do not yet support that feature. */
> >> if (intf->session->sol_data.port != intf->session->port)
> >> {
> >> /* try byteswapping port in case BMC sent it incorrectly */
> >> uint16_t portswap = BSWAP_16(intf->session->sol_data.port);
> >>
> >> if (portswap == intf->session->port) {
> >> intf->session->sol_data.port = portswap;
> >> }
> >> else {
> >> lprintf(LOG_ERR, "Error: BMC requests SOL session on
> >> different port");
> >> return -1;
> >> }
> >> }
> >> (...)
> >>
> >> the comment seems to explains why I get this message...
> >>
> >> Le 30/12/2011 13:12, Hank Bruning a écrit :
> >>> The RMCP server can use any UDP port it wants to for a SOL session.
> >>> Some implementations use port 623. If you have more than two SOL
> >>> sessions open on a single RMCP server at least one will be on a port
> >>> other than 623. Each of the SOL sessions may be encrypted
> >>> differently using separate cipher suites(or none at all).
> >>> Hank
> >>> JBlade
> >>>
> >>> On Fri, Dec 30, 2011 at 6:34 AM, Martin Hamant<mar...@sound4.biz>
> >>> wrote:
> >>> Hi !!!
> >>>
> >>> I have a BMC configured with a local IP adress (192.168.X.X)
> >>> listening
> >>> on default port (623).
> >>>
> >>> I want to access it from the outside world. For that I have
> >>> set a port
> >>> forwarding rules on the router to the port 623 of this local
> >>> IP.
> >>>
> >>> every ipmitool commands works well BUT not SOL.
> >>>
> >>> # ipmitool -I lanplus -p (external_port) -U (...) -P (...)
> >>> -H (external
> >>> IP) sol activate
> >>>
> >>> I get the message: "Error: BMC requests SOL session on
> >>> different port"
> >>>
> >>> I'm not sure to understand exactly what it means ? What I
> >>> need to do to
> >>> make this work ?
> >>>
> >>> Thanks !!
> >>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't
> >>> need a complex
> >>> infrastructure or vast IT resources to deliver seamless,
> >>> secure access to
> >>> virtual desktops. With this all-in-one solution, easily
> >>> deploy virtual
> >>> desktops for less than the cost of PCs and save 60% on VDI
> >>> infrastructure
> >>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> >>> _______________________________________________
> >>> Ipmitool-devel mailing list
> >>> Ipmitool-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
> >>>
--
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
