--- On Wed, 5/27/09, Johnny Billquist <bqt at update.uu.se> wrote:
And yes, the help system actually holds everything you need
to know.
The trickiest thing is getting the firmware to load when it MOP boots. Once you're past that it's easy enough to configure ports and if I remember correctly the serial lines can autoconfigure anyway which will get you into the help system.
There seemed to be plenty of copies of the firmware image floating around on the web a couple of years back.
-Dave
Sampsa Laine wrote:
Thanks Chrissie, already seen this, unfortunately it does not contain anything like a command reference that would help me set up the ports etc. Anyone have something like this? How close are the commands of say a DECserver 100 to a 200?
Pretty much identical. As Chrissie said, the differences are modem related. But the follow the same patterns, so everything you can do on a DS100 also work on a DS200, you just have a few more parameters...
And yes, the help system actually holds everything you need to know.
Johnny
Sampsa
On 27 May 2009, at 14:25, Chrissie Caulfield wrote:
Sampsa Laine wrote:
Gentlemen, anyone happen to have softcopy documentation for the above?
Just got one off Ebay, will wire it up sooner or later.
Sampsa
If you'll take a reply from a non-gentleman ... I found this :
http://vt100.net/mirror/antonio/d200cin1.pdf
;-)
Chrissie
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
OK, great!
I found a manual for the 100 at: http://vt100.net/mirror/antonio/aaz085atk.pdf
Thought I'd post that here should this question arise again.
Sampsa
On 27 May 2009, at 14:54, Chrissie Caulfield wrote:
Sampsa Laine wrote:
Thanks Chrissie, already seen this, unfortunately it does not contain
anything like a command reference that would help me set up the ports
etc. Anyone have something like this? How close are the commands of say
a DECserver 100 to a 200?
It's very similar to a DECserver 100. Most of the differences are to do
with modem control.
I seem to remember it has quite good help too.
--
Chrissie
Sampsa Laine wrote:
Thanks Chrissie, already seen this, unfortunately it does not contain
anything like a command reference that would help me set up the ports
etc. Anyone have something like this? How close are the commands of say
a DECserver 100 to a 200?
It's very similar to a DECserver 100. Most of the differences are to do
with modem control.
I seem to remember it has quite good help too.
--
Chrissie
Thanks Chrissie, already seen this, unfortunately it does not contain anything like a command reference that would help me set up the ports etc. Anyone have something like this? How close are the commands of say a DECserver 100 to a 200?
Sampsa
On 27 May 2009, at 14:25, Chrissie Caulfield wrote:
Sampsa Laine wrote:
Gentlemen, anyone happen to have softcopy documentation for the above?
Just got one off Ebay, will wire it up sooner or later.
Sampsa
If you'll take a reply from a non-gentleman ... I found this :
http://vt100.net/mirror/antonio/d200cin1.pdf
;-)
Chrissie
Sampsa Laine wrote:
Gentlemen, anyone happen to have softcopy documentation for the above?
Just got one off Ebay, will wire it up sooner or later.
Sampsa
If you'll take a reply from a non-gentleman ... I found this :
http://vt100.net/mirror/antonio/d200cin1.pdf
;-)
Chrissie
On Wed, May 13, 2009 at 11:57:01AM +0100, Sampsa Laine wrote:
I agree, reliability could definitely be an issue. Of course the SSH
tunnel has the advantage of not really requiring any additional
software to be installed or configured.
While that's certainly a valid point, it's not like it's hard to install.
Setting it up on the other hand, well, if you've never done that before, it
can be a bit daunting.
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
On Fri, May 15, 2009 at 01:27:25PM +0200, Johnny Billquist wrote:
But in addition, for this to work, you need to allow the remote users to
get ssh access to your local machine, otherwise ssh can't set up tunneling.
And for me, that's not something I'll do for all you guys... :-)
After we get moved and get settled in, the two VAX 4000 boxes are going to
bet setup again. I'll also setup a cisco router or two to go along with them.
At that point I'd be willing to do GRE/OpenVPN/SSH/etc for people.
Also, within the next two to three weeks I'll be upgrading my colocated box.
It's got great bandwidth (100MB+) and I'd be more than willing to setup OpenVPN
for HECnet. I think for our purposes OpenVPN in bridging mode would work best.
Hmmm, I wonder how hard it would be to get DECnet support rolled into something
like OpenVPN?
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
Sampsa Laine wrote:
Came across this whilst looking for some SSH stuff and realized this could be used to either securely transmit HECnet data between two hosts or enable a host with a dynamic IP to run the bridge/MULTINET UDP thing:
http://24.97.150.195/nstwiki/index.php/Tunnelling_UDP_Traffic_Through_An_SS… Basically, they use a combination of SSH port forwarding (which is TCP only) and nc to create a secure UDP tunnel between two sites. Setting this up would be trivial on a standard Unix box and if we use public key authentication we don't even need to store passwords anywhere. Also, we would of course benefit from the authentication and cryptographic features that SSH brings to the table.
The main disadvantage I can see is that SSH runs over TCP so any dropped packets might cause more delays than using straight UDP.
Yes, tunneling through something would always work. It will cost a lot in overhead, but for some that may be okay.
Also, as you note, it might cause retransmits at several levels, which also cost some.
And of course, you also risk additional delays.
But in addition, for this to work, you need to allow the remote users to get ssh access to your local machine, otherwise ssh can't set up tunneling.
And for me, that's not something I'll do for all you guys... :-)
There are other aspects to this as well, but I'll leave it at this. I've also read the other comments. :-)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol