On Mon, Nov 28, 2005 at 08:04:29PM -0600, Jason L Tibbitts III wrote:
> >>>>> "WV" == Ward Vandewege <ward@...> writes:
> WV> And in fact, it _does_ work for the M3289. It seems to require
> WV> the odd keypress every now and then to keep the link active
> WV> (particularly across a reboot), and I had to change the hardcoded
> WV> management IP in the source, but it seemed to work reliably for
> WV> the rest.
> I wonder how you managed to get things working. I tried poking at it
> when the code first went into CVS and never made any progress.
I tried it and saw it could make the connection but did not get any output on
the console. Then I fired up Ethereal, and saw that traffic was sent to the
M3289 from my client for every keypress, but the responses (and a bunch of
other stuff) went to a bogus ip address (192.168.2.70 I think).
So I grepped the source for the address, found the relevant line, changed it,
recompiled, et voila, it worked.
> When you mentioned the hardcoded address I looked through the source
> and fixed it up, but I still get the same behavior as before: I can
> establish a connection and see packets cross the network and come back
> on every keystroke, but nothing echoes back. When I tried previously,
> I couldn't see anything from the BIOS either, but I can't reboot the
> machine at the moment to try that again.
> Do you have a getty running on the captured serial port so that you
> can get to the console via IPMI?
Why yes, of course! But if you haven't done that, you should still see BIOS
output (if you modify the source to send the traffic to your machine :), and
if you add the relevant options for Lilo/Grub, you should see that output
And assuming you're on Linux, you'll need to make sure that a few kernel
settings are set (most likely the case by default if you are running a distro
kernel). Just google for the Linux Serial Console howto for all the necessary
Bye for now,
Ward Vandewege <ward@...>
Free Software Foundation - Senior System Administrator