On Thu, 2016-03-10 at 06:31 +0700, EXT Corey Minyard wrote: > But the telnet socket option works just as well, I think. > As long as you assign the socket address to local-only, > I don't think there are any more security implications.
I was originally thinking that when ipmi_sim is the client it might miss some output from QEMU after it had been started but the TCP connection had not been established yet. After some thought I realized that one can easily configure QEMU so that it won't actually do anything before the connection is actually established. Taking this into consideration, I have no objection for the ipmi_sim being the client. So, I finally had the chance to switch my setup for the version and test the TCP based SoL. The verdict is that it works great and allows me to get rid of one extra socat process per IPMI instance, which makes the whole setup simpler and more robust. Thanks again for your effort on making this happen. The only minor thing I noticed that when I used telnet protocol on both ipmi_sim and QEMU side, SoL client seemed to receive some line noise like non-printable characters around the time when the connection was established. Closer examination revealed them to be TCP configuration directives, namely these: IAC DO TRANSMIT-BINARY IAC WILL TRANSMIT-BINARY IAC DON'T ECHO IAC WON'T ECHO That exact sequence is also in sol_telnet_initseq[] in sol.c and from the code it seems to me that it probably gets put into the wrong buffer, which would explain why it is sent to the SoL client instead of the intended target i.e. QEMU. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
