Thank you for your replies!
If it is easier for you I can set up an area router too. I only
thought running end nodes would not occupy a whole area...
Steve, I gladly sent you an email...
Regards,
Wolfgang
On 1 Feb 2013, at 16:27, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-02-01 22:22, Cory Smelosky wrote:
On 1 Feb 2013, at 16:21, Johnny Billquist <bqt at softjar.se> wrote:
Steve, since Wolfgang indicated he wanted to run an endnode, you'll have to decide the area.
Am I the only one that thinks an area dedicated to just endnodes is a good idea?
Probably, since that would be impossible. An area needs atleast one area router... Or are you saying that you think we should set up one area for people who only want to run endnodes? That seems like going over the river to get water.
I was thinking more like that, yes. I see your point though, maybe save that for when we're running out of areas.
Then everyone who wants to run an endnode needs to connect to some specific endpoint. And what for? There are absolutely no problems with having just an endnode anywhere.
That would get rather difficult, I see.
And since you need to have an area router, what is the problem of using an existing area router. Preferrably one close to you, and then just place your endnode in that area.
I am totally missing the point here, in which it seems people think that endnodes are somehow difficult. They are the simplest of DECnet nodes.
Johnny
Johnny
On 2013-02-01 22:11, Steve Davidson wrote:
Send me the following information (offline):
Your physical location: country at a minimum - this determines which Multinet router you will connect to
External dynamic - DNS name - this will be resolved every x number of minutes to maintain your link
DECnet area - this is used for naming the Multinet circuits
email address to send updates to (both external and internal (<node>::<username>))
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Wolfgang Eichberger
Sent: Fri 2/1/2013 02:30
To: Johnny Billquist
Cc: hecnet at update.uu.se
Subject: Re: [HECnet] Joining HECNET
Now as things settled I am back with my SimH/Vax (running 24/7 on a
raspberry pi) and my Alpha (an Alphastation 255 I newly aquired).
There are Decstations in Storage too (these odd MIPS Boxes) - maybe
one of these could be connected too - provided there's DECNet Support
in Ultrix.
There is. You just need to find the distribution.
Nice. I should have approbiate media and will give this a try.
You need to figure out who to connect to first, then we can fix the node
numbers. I have a terribly short memory. Who was it that could handle
Multinet with dynamic IP? Steve?
Care to help out? Also, Wolfgang, do you want to set a level 1 router, or do
you just epxect all your machines to be endnodes, and have each on have
their own link?
My memory isn't best too, so don't worry ;)
Primary intention is to bring up at least the simulated VAX 24/7. The
other machines would run on occasional basis. As my DecNET experience
is way too rusty best practice would be operating the simulated VAX as
Endnode for start.
It'd be greatly appreciated if Steve could help out with the Dynamic IP....
Regards,
Wolfgang
On 2013-02-01 22:22, Cory Smelosky wrote:
On 1 Feb 2013, at 16:21, Johnny Billquist <bqt at softjar.se> wrote:
Steve, since Wolfgang indicated he wanted to run an endnode, you'll have to decide the area.
Am I the only one that thinks an area dedicated to just endnodes is a good idea?
Probably, since that would be impossible. An area needs atleast one area router... Or are you saying that you think we should set up one area for people who only want to run endnodes? That seems like going over the river to get water.
Then everyone who wants to run an endnode needs to connect to some specific endpoint. And what for? There are absolutely no problems with having just an endnode anywhere.
And since you need to have an area router, what is the problem of using an existing area router. Preferrably one close to you, and then just place your endnode in that area.
I am totally missing the point here, in which it seems people think that endnodes are somehow difficult. They are the simplest of DECnet nodes.
Johnny
Johnny
On 2013-02-01 22:11, Steve Davidson wrote:
Send me the following information (offline):
Your physical location: country at a minimum - this determines which Multinet router you will connect to
External dynamic - DNS name - this will be resolved every x number of minutes to maintain your link
DECnet area - this is used for naming the Multinet circuits
email address to send updates to (both external and internal (<node>::<username>))
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Wolfgang Eichberger
Sent: Fri 2/1/2013 02:30
To: Johnny Billquist
Cc: hecnet at update.uu.se
Subject: Re: [HECnet] Joining HECNET
Now as things settled I am back with my SimH/Vax (running 24/7 on a
raspberry pi) and my Alpha (an Alphastation 255 I newly aquired).
There are Decstations in Storage too (these odd MIPS Boxes) - maybe
one of these could be connected too - provided there's DECNet Support
in Ultrix.
There is. You just need to find the distribution.
Nice. I should have approbiate media and will give this a try.
You need to figure out who to connect to first, then we can fix the node
numbers. I have a terribly short memory. Who was it that could handle
Multinet with dynamic IP? Steve?
Care to help out? Also, Wolfgang, do you want to set a level 1 router, or do
you just epxect all your machines to be endnodes, and have each on have
their own link?
My memory isn't best too, so don't worry ;)
Primary intention is to bring up at least the simulated VAX 24/7. The
other machines would run on occasional basis. As my DecNET experience
is way too rusty best practice would be operating the simulated VAX as
Endnode for start.
It'd be greatly appreciated if Steve could help out with the Dynamic IP....
Regards,
Wolfgang
On 2/1/2013 4:21 PM, Cory Smelosky wrote:
Two things:
1). Does it handle dynamic IPs?
Yes.
2). If not, does it support IPv6? As that's static for me.
No.
-brian
On 1 Feb 2013, at 16:21, Johnny Billquist <bqt at softjar.se> wrote:
Steve, since Wolfgang indicated he wanted to run an endnode, you'll have to decide the area.
Am I the only one that thinks an area dedicated to just endnodes is a good idea?
Johnny
On 2013-02-01 22:11, Steve Davidson wrote:
Send me the following information (offline):
Your physical location: country at a minimum - this determines which Multinet router you will connect to
External dynamic - DNS name - this will be resolved every x number of minutes to maintain your link
DECnet area - this is used for naming the Multinet circuits
email address to send updates to (both external and internal (<node>::<username>))
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Wolfgang Eichberger
Sent: Fri 2/1/2013 02:30
To: Johnny Billquist
Cc: hecnet at update.uu.se
Subject: Re: [HECnet] Joining HECNET
Now as things settled I am back with my SimH/Vax (running 24/7 on a
raspberry pi) and my Alpha (an Alphastation 255 I newly aquired).
There are Decstations in Storage too (these odd MIPS Boxes) - maybe
one of these could be connected too - provided there's DECNet Support
in Ultrix.
There is. You just need to find the distribution.
Nice. I should have approbiate media and will give this a try.
You need to figure out who to connect to first, then we can fix the node
numbers. I have a terribly short memory. Who was it that could handle
Multinet with dynamic IP? Steve?
Care to help out? Also, Wolfgang, do you want to set a level 1 router, or do
you just epxect all your machines to be endnodes, and have each on have
their own link?
My memory isn't best too, so don't worry ;)
Primary intention is to bring up at least the simulated VAX 24/7. The
other machines would run on occasional basis. As my DecNET experience
is way too rusty best practice would be operating the simulated VAX as
Endnode for start.
It'd be greatly appreciated if Steve could help out with the Dynamic IP....
Regards,
Wolfgang
Steve, since Wolfgang indicated he wanted to run an endnode, you'll have to decide the area.
Johnny
On 2013-02-01 22:11, Steve Davidson wrote:
Send me the following information (offline):
Your physical location: country at a minimum - this determines which Multinet router you will connect to
External dynamic - DNS name - this will be resolved every x number of minutes to maintain your link
DECnet area - this is used for naming the Multinet circuits
email address to send updates to (both external and internal (<node>::<username>))
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Wolfgang Eichberger
Sent: Fri 2/1/2013 02:30
To: Johnny Billquist
Cc: hecnet at update.uu.se
Subject: Re: [HECnet] Joining HECNET
Now as things settled I am back with my SimH/Vax (running 24/7 on a
raspberry pi) and my Alpha (an Alphastation 255 I newly aquired).
There are Decstations in Storage too (these odd MIPS Boxes) - maybe
one of these could be connected too - provided there's DECNet Support
in Ultrix.
There is. You just need to find the distribution.
Nice. I should have approbiate media and will give this a try.
You need to figure out who to connect to first, then we can fix the node
numbers. I have a terribly short memory. Who was it that could handle
Multinet with dynamic IP? Steve?
Care to help out? Also, Wolfgang, do you want to set a level 1 router, or do
you just epxect all your machines to be endnodes, and have each on have
their own link?
My memory isn't best too, so don't worry ;)
Primary intention is to bring up at least the simulated VAX 24/7. The
other machines would run on occasional basis. As my DecNET experience
is way too rusty best practice would be operating the simulated VAX as
Endnode for start.
It'd be greatly appreciated if Steve could help out with the Dynamic IP....
Regards,
Wolfgang
On 1 Feb 2013, at 16:19, Brian Hechinger <wonko at 4amlunch.net> wrote:
Oh, one last thing. The config tool automatically updates the firewall rules on the tftp server to only allow you people to access it. If you can't access it make sure you are coming in as the IP the tunnel connects to. If you need to come in as a different IP let me know and i'll get that added.
Two things:
1). Does it handle dynamic IPs?
2). If not, does it support IPv6? As that's static for me.
-brian
Oh, one last thing. The config tool automatically updates the firewall rules on the tftp server to only allow you people to access it. If you can't access it make sure you are coming in as the IP the tunnel connects to. If you need to come in as a different IP let me know and i'll get that added.
-brian
On 02/01/2013 04:16 PM, Brian Hechinger wrote:
How do you assign tunnel interface numbers? My router has many
tunnels running for things unrelated to HECnet; I don't want to clobber
them.
I was originally letting it generate them but realized that could result
in tunnel interface numbers changing around which might break something
like performance data with snmp so now it's all statically assigned in
the CSV data file.
I've started at 50 and go up from there because I figure that's probably
a safe range to use.
This can be changed very easily, however.
Ok, this sounds like a good approach. Starting at 50 works for me.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2/1/2013 4:08 PM, Cory Smelosky wrote:
You can load these directly from your cisco to have it update the tunnels.
Can I make KRON load them?;)
Probably? I wouldn't though because there's no reason to re-load them unless they've changed.
There is a way to trigger the tftp load via snmp and I'm working on that now. Once that's done auto-load is a little easier.
-brian
