HECnet

hecnet@lists.dfupdate.se

15589 discussions

by jeep＠scshome.net

If you are that worried about your security on a given system then make a standalone system available to the world and be done with it. I am sure that I could come up with something if I could only find the time... It really isn't that difficult. -Steve ________________________________ From: owner-hecnet at Update.UU.SE on behalf of Mark Wickens Sent: Wed 9/25/2013 10:47 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Public access? On 25/09/2013 01:54, Sampsa Laine wrote: I'm always happy to take more users onto CHIMPY and the HILANT clusters - you think I should let people in comp.os.vms know about these? Does anybody mind 'outsiders' getting access to HECnet? I don't mind. Most will probably not explore the fact that there is a big DECnet behind the machines. It is not that we are preventing people today either. It's just that there have never been much fuss about HECnet. However, I can understand if some people feel worried about traffic and issues. If so, let us know, and we'll try to think of what to do. This is why I manually vet the account requests - if the email address or name seem totally bullshit, I just ignore the request. I get maybe 2-3 new users per week on each system..I personally don't want to let the Deathrow guys behind my firewall :) sampsa Sampsa I'd seriously consider picking Steven Hoffman's brains on this before opening a system up to the world. I had thought about trying to get a VMS box collocated for a 'UK deathrow' experience but Hoff seriously put me off the idea ;) And I think you have the same 'seat of your pants' mentality that I do, which probably isn't a win when you're looking to manage a public facing system (or at least a public facing system that the public know about!) Mark. -- http://www.wickensonline.co.uk <http://www.wickensonline.co.uk/> http://hecnet.eu <http://hecnet.eu/> http://declegacy.org.uk <http://declegacy.org.uk/> http://retrochallenge.net <http://retrochallenge.net/> https://twitter.com/#!/%40urbancamo

12 years, 4 months

Public access?

by sampsa＠mac.com

sampsa <sampsa at mac.com> mobile +358 40 7208932 On 25 Sep 2013, at 22:03, Paul_Koning at Dell.com wrote: No, it's an implementation of DECnet in Python. Right now it speaks routing and MOP; other layers later. paul Cool - let me know when you get the other layers working, I've been looking for ways to make Python programs talk DECNET.. sampsa

12 years, 4 months

Public access?

by Paul_Koning＠Dell.com

No, it's an implementation of DECnet in Python. Right now it speaks routing and MOP; other layers later. paul On Sep 25, 2013, at 3:07 PM, Sampsa Laine <sampsa at mac.com> wrote: pydecnet? Please tell me these are Python bindings for DECNET...:) sampsa <sampsa at mac.com> mobile +358 40 7208932 On 25 Sep 2013, at 20:08, Paul_Koning at Dell.com wrote: You mean my pydecnet protocol stack? I've not been able to add to that in the past couple of months. paul On Sep 25, 2013, at 2:01 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I vaugely remember that. I've been too busy and haven't worked on things lately. I was hoping for Paul's stuff because it solves more problems than just your router. :) -brian On Wed, Sep 25, 2013 at 06:56:25PM +0100, Jarratt RMA wrote: I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: What does my router do to break your mapper? If I know it might be something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

Public access?

by sampsa＠mac.com

pydecnet? Please tell me these are Python bindings for DECNET...:) sampsa <sampsa at mac.com> mobile +358 40 7208932 On 25 Sep 2013, at 20:08, Paul_Koning at Dell.com wrote: You mean my pydecnet protocol stack? I've not been able to add to that in the past couple of months. paul On Sep 25, 2013, at 2:01 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I vaugely remember that. I've been too busy and haven't worked on things lately. I was hoping for Paul's stuff because it solves more problems than just your router. :) -brian On Wed, Sep 25, 2013 at 06:56:25PM +0100, Jarratt RMA wrote: I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: What does my router do to break your mapper? If I know it might be something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

Public access?

by wonko＠4amlunch.net

Yes, which is why I hadn't made much progress myself. :) I do need to get things setup to test your GRE bits though. -brian On Wed, Sep 25, 2013 at 06:08:14PM +0000, Paul_Koning at Dell.com wrote: You mean my pydecnet protocol stack? I've not been able to add to that in the past couple of months. paul On Sep 25, 2013, at 2:01 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I vaugely remember that. I've been too busy and haven't worked on things lately. I was hoping for Paul's stuff because it solves more problems than just your router. :) -brian On Wed, Sep 25, 2013 at 06:56:25PM +0100, Jarratt RMA wrote: I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: What does my router do to break your mapper? If I know it might be something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

Public access?

by Paul_Koning＠Dell.com

You mean my pydecnet protocol stack? I've not been able to add to that in the past couple of months. paul On Sep 25, 2013, at 2:01 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I vaugely remember that. I've been too busy and haven't worked on things lately. I was hoping for Paul's stuff because it solves more problems than just your router. :) -brian On Wed, Sep 25, 2013 at 06:56:25PM +0100, Jarratt RMA wrote: I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: What does my router do to break your mapper? If I know it might be something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

Public access?

by wonko＠4amlunch.net

I vaugely remember that. I've been too busy and haven't worked on things lately. I was hoping for Paul's stuff because it solves more problems than just your router. :) -brian On Wed, Sep 25, 2013 at 06:56:25PM +0100, Jarratt RMA wrote: I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: What does my router do to break your mapper? If I know it might be something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

Public access?

by robert.jarratt＠ntlworld.com

I implemented the two commands you need (SHOW ADJACENT NODES and SHOW KNOWN CIRCUITS) a while ago and that is live now if you want to try. I thought I had mentioned this but perhaps I didn't. In case you don't remember I am area 5 and the router is at 5.1023. Regards Rob On 25 September 2013 00:07, Brian Hechinger <wonko at 4amlunch.net> wrote: On Tue, Sep 24, 2013 at 09:16:15PM +0100, Jarratt RMA wrote: > What does my router do to break your mapper? If I know it might be > something I can fix. The mapper currently relies on NICE, so a device that doesn't speak that can't be mapped. -brian

12 years, 4 months

What happens when the host uses a dynamically assigned IP address?

by b4＠gewt.net

On Wed, 25 Sep 2013, Ian McLaughlin wrote: I know something's broken when I don't see a message about Cory's IP changing at least once every other day. s/broken/wrong/ as it means I haven't broken anything for awhile. It usually indicates i'm sick or busy. ;) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects

12 years, 4 months

What happens when the host uses a dynamically assigned IP address?

by b4＠gewt.net

On Wed, 25 Sep 2013, Brian Hechinger wrote: Even then I don't know how much of an issue it is. Cory's IP address changes ALL THE TIME. :) -brian 85% of that is my doing. I tend to break things here a lot. I have most everything stable on a UPS now and I have everything configured to give me enough time to spin up a generator before the UPS runs out. (The NAS is set to shut down and when it does I get about 45 minutes on the UPS) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects

12 years, 4 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet