Hi,
After prolonged downtime, and a major upheaval in my room, including shutting down my Microserver that formally ran 24/7, I have finally got STAR69 running agin and Area 6's routing functioning once more. STAR69 is not running on a RaspberryPi (old 256MB version) and seems to be working normally again. The bridge is also up on the same Linux unit.
I bet no-one even noticed, right? ;)
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 10/23/2012 08:37 PM, Cory Smelosky wrote:
I might be able to find a Qbus SCSI host adapter, but I those seem to
run quite a bit on ebay, but I have other resources (that don't seem
to have anything DEC )
They are expensive, but they're well worth having if you can scrape
together the bucks.
I think it'd be cheaper for me to find some DSSI drives. (Or add a
DSSI <-----> SCSI adapter in to the mix )
Well, trouble is, they're drying up fast.
Think I could make a VAX work with iSCSI? ;)
That's an idea!
Would be easier on a weekend due to my eyesight making me unable to
drive, so i'd need someone to drive me there. Although I have a few
friends a little ways from Pittsburgh who might be able to help in
some way. Me getting there directly is a bit challenging, both due to
my eyesight and possibly being the youngest here ;).
Understood. I generally don't differentiate much between weekdays and
weekends, so either is fine for me.
(You have no idea how hard it is to get this working in a VM ).
Oh yes I do. ;) I virtualized a gaggle of SCO OpenServer machines
for a customer about two years ago, using VMware. Oh man that was
a mess...VMware was the only virtualization platform that would
work, and even that took some doing. They're all still running,
though, but now on VERY different hardware. :-)
At least it's not Hyper-V I couldn't get anything to run in
Hyper-V save for windows. And not even NT 4!
Eeeeeek!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Ah, I don't know anything about Multinet. Is there a reason why you can't
use the bridge in that case?
The bridge program probably would have worked better, but since I'm shutting down the server hosting these virtual machines (along with a couple Solaris VMs, a Linux VM, and a Windows VM), it's easier just to keep the stuff offline except for the rare times when I might need to boot up a VMS or PDP-11 system. (Given the amount of times I've accessed the systems in the past year, I suspect that it's more about archiving them for reference.)
--Marc
-----Original Message-----
From: Marc Chametzky [mailto:marc at bluevine.net]
Sent: 25 October 2012 20:53
To: hecnet at Update.UU.SE
Cc: Rob Jarratt
Subject: Re: [HECnet] Leaving HECnet
Can you explain a little more about the randomization of the source
port number? I might be being stupid here, but I don't see what
problem that would cause, the bridge runs over UDP. Or are you talking
about some other way of tunnelling DECnet over IP?
I'm not using the bridge program. I'm using MultiNet's DECnet-over-IP
circuit. It sends packets to the remote system over UDP on port 700. The
problem is that its source port is also 700. My firewall randomizes the
source port for security reasons and is not configurable in that regard.
When the destination system receives packets from my network, it drops
them because they don't have the right source port.
--Marc
Ah, I don't know anything about Multinet. Is there a reason why you can't
use the bridge in that case?
Regards
Rob
Can you explain a little more about the randomization of the source port
number? I might be being stupid here, but I don't see what problem that
would cause, the bridge runs over UDP. Or are you talking about some other
way of tunnelling DECnet over IP?
I'm not using the bridge program. I'm using MultiNet's DECnet-over-IP circuit. It sends packets to the remote system over UDP on port 700. The problem is that its source port is also 700. My firewall randomizes the source port for security reasons and is not configurable in that regard. When the destination system receives packets from my network, it drops them because they don't have the right source port.
--Marc
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Marc Chametzky
Sent: 25 October 2012 19:49
To: hecnet at Update.UU.SE
Subject: [HECnet] Leaving HECnet
I'm working on consolidating my system and as part of this, I'm getting
rid
of my ESXi server that's running my virtual systems. I'm going to move
them
to my file server where I'll simply run them on demand from my Mac.
I thought about keeping HECnet around, but given that my connectivity
hasn't been working anyway due to my firewall's insistence on randomizing
the source port number for the DECnet-over-IP circuit, I think I'm just
going
to drop off at this point. Plus, I don't know when I'd be back online
again in
the future once I shut the server down.
The affected nodes to be removed are 19.300 through 19.304.
Thanks so much for letting me hang around. I still love the idea of a
hobbyist
DECnet. :-)
--Marc
Marc,
Can you explain a little more about the randomization of the source port
number? I might be being stupid here, but I don't see what problem that
would cause, the bridge runs over UDP. Or are you talking about some other
way of tunnelling DECnet over IP?
Regards
Rob
On 10/25/2012 02:49 PM, Marc Chametzky wrote:
I'm working on consolidating my system and as part of this, I'm getting
rid of my ESXi server that's running my virtual systems. I'm going to
move them to my file server where I'll simply run them on demand from my
Mac.
I thought about keeping HECnet around, but given that my connectivity
hasn't been working anyway due to my firewall's insistence on
randomizing the source port number for the DECnet-over-IP circuit, I
think I'm just going to drop off at this point. Plus, I don't know when
I'd be back online again in the future once I shut the server down.
The affected nodes to be removed are 19.300 through 19.304.
Thanks so much for letting me hang around. I still love the idea of a
hobbyist DECnet. :-)
:-(
--
Dave McGuire, AK4HZ
New Kensington, PA
I'm working on consolidating my system and as part of this, I'm getting rid of my ESXi server that's running my virtual systems. I'm going to move them to my file server where I'll simply run them on demand from my Mac.
I thought about keeping HECnet around, but given that my connectivity hasn't been working anyway due to my firewall's insistence on randomizing the source port number for the DECnet-over-IP circuit, I think I'm just going to drop off at this point. Plus, I don't know when I'd be back online again in the future once I shut the server down.
The affected nodes to be removed are 19.300 through 19.304.
Thanks so much for letting me hang around. I still love the idea of a hobbyist DECnet. :-)
--Marc
I installed it fine too, I just couldn t get it to actually do anything.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rob Sent: 24 October 2012 23:37 To: hecnet at update.uu.se Subject: [HECnet] Re: HECNet
Well the package installs fine, I am just waiting on an email from Johnny Billquist with the info I need. On Wednesday, October 24, 2012, Rob Jarratt wrote:
I could never get that package to work on Debian. I am not an expert in matters Linux, but if you can share your experiences it might be useful when I have another go at some point.
Thanks
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rob Sent: 24 October 2012 21:25 To: hecnet at update.uu.se Subject: [HECnet] HECNet
Well,
I have been a lurker long enough, I have the router setup on Linux, and ready to install the apt-get install dnet-progs pkg.
Robbie Moran
