On 1/30/2013 9:37 PM, Cory Smelosky wrote:
Now, dynamic IP handling: I was thinking a script that would:
1). Periodically ping the hostname
2). If it stops responding to ping, update the destination hostname for the tunnel (as the tunnel resolves hostnames right then and there, correct?) (perhaps a simple database of the current IP for the tunnel would be better?)
I think we need to get this working natively in IOS somehow. I don't want to generate a new config if someone's IP changes, although I *could* if I needed to.
Assuming it doesn't happen all the time I guess that's not so bad, really.
-brian
On 1/30/2013 9:33 PM, Ian McLaughlin wrote:
Full mesh is great by me.
Ok, cool.
Am I understanding this correctly that you will keep a database of all the Cisco devices, and when a new member signs up you will generate a new config for everyone ?
Exactly!
Anytime anyone new sends me the required info i'll generate a new config set and email it out to everyone (well, the script will)
-brian
On 30 Jan 2013, at 21:33, Ian McLaughlin <ian at platinum.net> wrote:
Full mesh is great by me. Am I understanding this correctly that you will keep a database of all the Cisco devices, and when a new member signs up you will generate a new config for everyone ?
I support full-mesh as well.
Now, dynamic IP handling: I was thinking a script that would:
1). Periodically ping the hostname
2). If it stops responding to ping, update the destination hostname for the tunnel (as the tunnel resolves hostnames right then and there, correct?) (perhaps a simple database of the current IP for the tunnel would be better?)
Ian
Sent from my iPhone
On 2013-01-30, at 6:21 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
Ok, I'm motivated. Let's get this automated.
I've got a small bit of python I wrote to generate cisco configs for the tunnels.
If you are interested in getting auto-generated tunnel configs please send me the following information:
1) The email address you want new configs sent to
2) Your routers public IP address(es)
3) The source interface(s) for your tunnels in full interface text. re: FastEthernet0/1
4) The cost you want your tunnels to be if you don't want them to be 10.
Once you've gotten your first config text from me delete all your current HECnet tunnels and then apply the config text you'll have been emailed.
Unless anyone objects, I'm starting tunnel indexes at 50.
Steve D. -- if you want a router let me know. I'm going to eventually get off my ass and migrate to this 2851 which will free up the 1841. I'm more than happy to loan it to you as long as I have no need for it. (Which I doubt I ever will)
The one question I have for everyone is.... Do we do a full mesh or do we choose 1-3 "hubs" to connect everyone to? If 20 people have cisco's and we do a mesh that's 20 tunnels, FYI. I'm ok with that, but I want to get an idea of what everyone else thinks.
-brian
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=F33139E26B4C11E2A…
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
Full mesh is great by me. Am I understanding this correctly that you will keep a database of all the Cisco devices, and when a new member signs up you will generate a new config for everyone ?
Ian
Sent from my iPhone
On 2013-01-30, at 6:21 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
Ok, I'm motivated. Let's get this automated.
I've got a small bit of python I wrote to generate cisco configs for the tunnels.
If you are interested in getting auto-generated tunnel configs please send me the following information:
1) The email address you want new configs sent to
2) Your routers public IP address(es)
3) The source interface(s) for your tunnels in full interface text. re: FastEthernet0/1
4) The cost you want your tunnels to be if you don't want them to be 10.
Once you've gotten your first config text from me delete all your current HECnet tunnels and then apply the config text you'll have been emailed.
Unless anyone objects, I'm starting tunnel indexes at 50.
Steve D. -- if you want a router let me know. I'm going to eventually get off my ass and migrate to this 2851 which will free up the 1841. I'm more than happy to loan it to you as long as I have no need for it. (Which I doubt I ever will)
The one question I have for everyone is.... Do we do a full mesh or do we choose 1-3 "hubs" to connect everyone to? If 20 people have cisco's and we do a mesh that's 20 tunnels, FYI. I'm ok with that, but I want to get an idea of what everyone else thinks.
-brian
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=F33139E26B4C11E2A…
Ok, I'm motivated. Let's get this automated.
I've got a small bit of python I wrote to generate cisco configs for the tunnels.
If you are interested in getting auto-generated tunnel configs please send me the following information:
1) The email address you want new configs sent to
2) Your routers public IP address(es)
3) The source interface(s) for your tunnels in full interface text. re: FastEthernet0/1
4) The cost you want your tunnels to be if you don't want them to be 10.
Once you've gotten your first config text from me delete all your current HECnet tunnels and then apply the config text you'll have been emailed.
Unless anyone objects, I'm starting tunnel indexes at 50.
Steve D. -- if you want a router let me know. I'm going to eventually get off my ass and migrate to this 2851 which will free up the 1841. I'm more than happy to loan it to you as long as I have no need for it. (Which I doubt I ever will)
The one question I have for everyone is.... Do we do a full mesh or do we choose 1-3 "hubs" to connect everyone to? If 20 people have cisco's and we do a mesh that's 20 tunnels, FYI. I'm ok with that, but I want to get an idea of what everyone else thinks.
-brian
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Steve Davidson
Sent: 30 January 2013 02:04
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Returning to HECNET
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rob Jarratt
Sent: Tuesday, January 29, 2013 18:50
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Returning to HECNET
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE]
On Behalf Of sampsa at mac.com
Sent: 29 January 2013 23:25
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Returning to HECNET
2. Persuade someone who has a fixed IP to run the user mode
router, if you register your IP with something like DynDns then
the user mode router periodically checks for a change of IP.
Is the user mode router ready? I could deploy that..
[Rob Jarratt]
It has been used in a couple of configurations now and
seems to work
OK, I use it permanently now. You could try it and if it does not
work for you it is only seconds to switch back to the bridge.
Oh I was going to run the bridge as well, act as a sort of
connections
hub (Bridge, MULTINET on GORVAX and the user mode router).
What OS does the user mode router run on?
sampsa
It runs on Windows (as a Windows Service) and it runs on linux (as a
Daemon). I built the linux version on the Raspberry Pi using a flavour
of Debian. I think it has been built on FreeBSD too.
Regards
Rob
Would it run on NetBSD???
Not tried it so I don't know. I am not really very knowledgeable on all the
different Unix flavours, but the code does not do a lot that is special so
it should work. Try building it, if it doesn't compile or work let me know
and I will build a NetBSD virtual machine and get it working.
Regards
Rob
On 30 Jan 2013, at 14:45, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/29/2013 5:57 PM, Rob Jarratt wrote:
A couple of other options are:
1. Never switch off your router so that it keeps its IP address. In my case
(Virgin Media in the UK), my IP address does not change for months at a
time, and just ask Johnny (or whoever you peer to), to restart the bridge
with a new IP.
2. Persuade someone who has a fixed IP to run the user mode router, if you
register your IP with something like DynDns then the user mode router
periodically checks for a change of IP.
3. Use the upcoming SIMH emulation of the DMC11, which allows you to connect
using TCP to someone else who has a fixed IP. Again you would need to
persuade someone who has a static IP to peer with you. But the SIMH
emulation does actually do a fresh DNS lookup if the connection goes down,
so a change of IP would work in any case.
Cory, any progress on the Cisco dynamic IP thing?
Haven't had the time to poke at cisco scripting lately. Been too busy migrating to VMWare. I should have time later tonight. I'll let you know my progress.
-brian
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 1/29/2013 5:57 PM, Rob Jarratt wrote:
A couple of other options are:
1. Never switch off your router so that it keeps its IP address. In my case
(Virgin Media in the UK), my IP address does not change for months at a
time, and just ask Johnny (or whoever you peer to), to restart the bridge
with a new IP.
2. Persuade someone who has a fixed IP to run the user mode router, if you
register your IP with something like DynDns then the user mode router
periodically checks for a change of IP.
3. Use the upcoming SIMH emulation of the DMC11, which allows you to connect
using TCP to someone else who has a fixed IP. Again you would need to
persuade someone who has a static IP to peer with you. But the SIMH
emulation does actually do a fresh DNS lookup if the connection goes down,
so a change of IP would work in any case.
Cory, any progress on the Cisco dynamic IP thing?
-brian
sampsa at mac.com writes:
On 30 Jan 2013, at 16:22, Tim Sneddon <tim at sneddon.id.au> wrote:
X25 and UUCP have been dropped when MX became open source. SITE is
definitely still there. I've seend that used for lots of interesting
stuff. I'm pretty sure it was Ruslan Laishev that developed an SMS >
gateway for MX.
Damn it - we could've interfaced it via UUCP to UUHECNET...
The V4.x MX pachage is still out on the internet with these pieces. It
might be possible to use the older package or use these components from
it.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
