If all you're wanting to do is simply telnet into the VAX... <br><br>Assuming a recent Linux kernel <br><br>Bridge devices, and veth type devices will work wonders to get the VAX on the LAN. <br><br>See: <br><br><a href="http://comments.gmane.org/gmane.comp.emulators.simh/420">http://comments.gmane.org/gmane.comp.emulators.simh/420</a> (or search the archives) <br>
<br>As a good starting point.... Obviously, I've used them at one point.. <br><br>David<br><br><div class="gmail_quote">On Thu, May 19, 2011 at 7:17 PM, Gary Lee Phillips <span dir="ltr"><<a href="mailto:tivo.overo@gmail.com">tivo.overo@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Thu, May 19, 2011 at 12:03 PM, Jason Stevens <<a href="mailto:neozeed@gmail.com">neozeed@gmail.com</a>> wrote:<br>
> I'd try the 'modem' setup for the DZ ... I recall something similar<br>
> with Unix/32v<br>
><br>
> set dz lines=16<br>
> att dz -m 2311<br>
><br>
<br>
</div>Well, that sounded promising, but as far as I can tell, it made no<br>
difference at all.<br>
<br>
After a telnet session to the DZ port 8501, no matter how it<br>
terminates, the unit remains locked up for several minutes and cannot<br>
connect to the VAX emulation again. Eventually a security error is<br>
reported to the OPA0 terminal, saying that no input could be obtained<br>
from TTA0 and the connection has timed out. Then it is possible once<br>
again to connect through port 8501 for another session.<br>
<br>
Sessions work fine while they are connected. The issue is<br>
disconnecting and being able to reconnect. There appears to be some<br>
failure in handshake between the DZ emulation and the VAX driver, such<br>
that the closed telnet session, even if a hangup was sent, remains<br>
active (virtual DSR asserted, maybe?) for some length of time. This<br>
would be OK if the DZ emulation itself rotated through the available<br>
lines, sending the next connect request to line 2, and the next to<br>
line 3, and so forth, but it doesn't do that. As far as it is<br>
concerned, line 0 is now clear and the next SYNC results in a new<br>
connection to line 0. But the VAX driver isn't accepting that<br>
connection, or so it seems.<br>
<br>
The timeout seems to vary, anywhere from five minutes to fifteen or<br>
more. In one case the line was still tied up after sitting unused<br>
overnight.<br>
<br>
Just to clarify, as there seems to be some confusion, I want to use<br>
the DZ emulation to allow terminal sessions that originate on the same<br>
host box that runs the SIMH software to connect to the emulated VAX.<br>
This is not possible if the emulation and the host share the same NIC,<br>
but it can be done by going through the DZ, which provides a<br>
host-based port number. I am not trying to connect an actual VT<br>
terminal, and I don't see that the DZ emulation is really intended to<br>
do that. As for LAT, I found it cumbersome to use even when I had a<br>
real VAX and a real terminal server. It doesn't seem appropriate to<br>
this particular situation at all.<br>
<font color="#888888"><br>
--Gary<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
</div></div></blockquote></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>