Guys,
Looking to tap into your collective knowledge.
I'd like to set up a 3G dongle for the DEC Legacy event.
The plan will be to add my machine as an area router then other participants machines into that area.
Steve Davidson has pointed out that there are decnet numbers allocated for experimental purposes.
I think I understand how to setup my 3G dongle to connect to the internet via an ubuntu machine. I am happy setting up a DHCP and DNS server on the same machine. The bit I don't understand is how I would fit the hecnet bridge into this network. Normally on my DSL router I have a port redirection rule setup on port 4711 to point to a Debian based box on my LAN.
How would I achieve the same effect on a linux box? If I run the bridge on the same box, does this negate the need for a rule?
If all this works, is there a restriction of one decnet area per lan segment? Can I run two areas on my side of the bridge?
Thanks for the help, Mark
Chimpy wont boot for some reason anymore.
I've reseated all the RAM, the CPU and PCI cards - but get nothing. Not even the diagnostic beeps.
Any ideas?
Sampsa
On 2011-09-07, at 8:06 AM, Brian Hechinger wrote:
On 9/7/2011 8:23 AM, Sampsa Laine wrote:
Hmm, it's working now? Any one else want to try it and see if the 503 was a random hamster dying or something?
Sampsa
PS: Make sure you use exactly this URL to log in:
http://rhesus.sampsa.com/ftalk/
On 6 Sep 2011, at 21:48, Ian McLaughlin wrote:
On 2011-09-06, at 12:56 PM, Sampsa Laine wrote:
http://rhesus.sampsa.com/ftalk/
I get a 503 Service Unavailable error. Did I break it?
Ian
I get: Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
-brian
I'm still getting "503 Service Unavailable Unable to connect to 188.220.63.2".
Ian
On 9/7/2011 8:23 AM, Sampsa Laine wrote:
Hmm, it's working now? Any one else want to try it and see if the 503 was a random hamster dying or something?
Sampsa
PS: Make sure you use exactly this URL to log in:
http://rhesus.sampsa.com/ftalk/
On 6 Sep 2011, at 21:48, Ian McLaughlin wrote:
On 2011-09-06, at 12:56 PM, Sampsa Laine wrote:
http://rhesus.sampsa.com/ftalk/
I get a 503 Service Unavailable error. Did I break it?
Ian
I get: Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
-brian
Mark,
Since my phone only allows topposting I've deleted the original text. Your question was how decnet devices get their names.
The letters indicate the controller, they tell you what hardware is in use. So UNA indicates a DEUNA and ESA an on board controller for a microVAX. After the hyphen follows the controller number, the first interface is nr 0.
VMS device names differ: two ethernet controllers may be called EWA0: and EWB0: in VMS and be known in NCP as EWA-0 and EWA-1.
The name for the circuit is the same for the line (AFAIK).
Serial interfaces (for DDCMP) or CI interfaces follow different rules.
Hans
Verzonden vanaf mijn draadloze BlackBerry -toestel
On 07/09/11 13:57, hvlems at zonnet.nl wrote:
Two options: 1 rerun Netconfig,
2 manually create the circuit EWA-1 and line EWA-1 (assuming that the current ones are called EWA-0).
Hans
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] New network card in the Alpha, how do I reconfigure DECNET?
Verzonden: 7 september 2011 14:30
Hi,
I've got an AlphaServer 300 running as a clustered satellite node from
an AlphaServer 1000A. The 300 has a built in DE450 network card (10MB).
I've augmented that with a PCI DE500 100MB network card.
My question is how I move DECnet off the old card (which is now
disconnected) to the new card.
I've tried running NETCONFIG but this doesn't seem to recognise the new
card.
The old card is EWA0: the new one EWB0:
The remote booting and cluster server are running fine, so the machine
boots OK off the new card, and I have reconfigured TCP/IP for the new
card, it's just DECNET I'm stumbling with.
The old card won't be connected to the network any more.
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
Thanks, I did re-run netconfig and it didn't seem to make any difference, but maybe I got caught in the make change/reboot trap.
I've just rebooted and it's working.
So for reference could I ask the question of how decnet associates a network controller with the decnet configuration?
Cheers, Mark
Two options: 1 rerun Netconfig,
2 manually create the circuit EWA-1 and line EWA-1 (assuming that the current ones are called EWA-0).
Hans
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] New network card in the Alpha, how do I reconfigure DECNET?
Verzonden: 7 september 2011 14:30
Hi,
I've got an AlphaServer 300 running as a clustered satellite node from
an AlphaServer 1000A. The 300 has a built in DE450 network card (10MB).
I've augmented that with a PCI DE500 100MB network card.
My question is how I move DECnet off the old card (which is now
disconnected) to the new card.
I've tried running NETCONFIG but this doesn't seem to recognise the new
card.
The old card is EWA0: the new one EWB0:
The remote booting and cluster server are running fine, so the machine
boots OK off the new card, and I have reconfigured TCP/IP for the new
card, it's just DECNET I'm stumbling with.
The old card won't be connected to the network any more.
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
Hi,
I've got an AlphaServer 300 running as a clustered satellite node from an AlphaServer 1000A. The 300 has a built in DE450 network card (10MB). I've augmented that with a PCI DE500 100MB network card.
My question is how I move DECnet off the old card (which is now disconnected) to the new card.
I've tried running NETCONFIG but this doesn't seem to recognise the new card.
The old card is EWA0: the new one EWB0:
The remote booting and cluster server are running fine, so the machine boots OK off the new card, and I have reconfigured TCP/IP for the new card, it's just DECNET I'm stumbling with.
The old card won't be connected to the network any more.
Thanks for the help, Mark.
Hmm, it's working now? Any one else want to try it and see if the 503 was a random hamster dying or something?
Sampsa
PS: Make sure you use exactly this URL to log in:
http://rhesus.sampsa.com/ftalk/
On 6 Sep 2011, at 21:48, Ian McLaughlin wrote:
On 2011-09-06, at 12:56 PM, Sampsa Laine wrote:
http://rhesus.sampsa.com/ftalk/
I get a 503 Service Unavailable error. Did I break it?
Ian
At 12:31 AM +0200 9/7/11, Johnny Billquist wrote:
On 2011-09-07 00:21, Zane H. Healy wrote:
At 11:48 PM +0200 9/6/11, Johnny Billquist wrote:
Does anyone have sources to RMS-11 V2.0. Specifically for RSX, in case
they differ.
I don't believe I have that in my archives.
(And no, the TCP/IP is not available for distribution yet, but might
be in the future, depending on interest and so on...)
Is this your own TCP/IP implementation or the one from Process Software?
This is my. Process Software's is much less capable. Not to mention slower. :-)
I'd be inclined to say agonizingly slow on a PDP-11/73 running RSX-11M+ V4.6. Time to release your version! ;-)
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com | OpenVMS Enthusiast |
| | Photographer |
+----------------------------------+----------------------------+
| My flickr Photostream |
| http://www.flickr.com/photos/33848088 at N03/ |