Hello!
I am thinking about a honking big UPS but the one I want is, ah, more
like a solar power rig also found parked on and inside someone's
home..........
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Wed, Sep 25, 2013 at 5:26 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Wed, 25 Sep 2013, Gregg Levine wrote:
Hello!
According to the ISP it will change only when the hardware used to
connect to the Internet gets restarted. So far that last happened
several weeks earlier.
Rig it up to a battery. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Wed, 25 Sep 2013, Gregg Levine wrote:
Hello!
According to the ISP it will change only when the hardware used to
connect to the Internet gets restarted. So far that last happened
several weeks earlier.
Rig it up to a battery. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Hello!
According to the ISP it will change only when the hardware used to
connect to the Internet gets restarted. So far that last happened
several weeks earlier.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Wed, Sep 25, 2013 at 11:55 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-09-25 17:04, Gregg Levine wrote:
Hello!
Still thinking about working on how to bring up a system that's
eligible for participation within our group. The only stumbling block
isn't the OS or the emulated system. In fact it happens to be the fact
that my Internet connection is managed via a DSL device who is
assigned an IP address via PPPoE services. Does any of our members
also have that problem? I actually asked the service provider what was
involved with ordering service for a static one several years earlier.
Problem then, was that the copper was too old in my part of the country.
I imagine that FIOS (Fiber-optic based service from the phone company)
is the reason why the copper isn't be upgraded.
And since my cable company can be all thumbs when performing service I
turned down their offers......
Several people (including me) do not have a fixed address. However, my ISP
seems to change my IP less than once a year, so it's not really a big
problem.
So I think it more depends on how often do you see address changes?
Johnny
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
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
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
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
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
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
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