Sounds like a good idea.
Mark, please provide me with the following information:
your IP:
Is IP dynamic:
hostname:
your area number:
the source interface:
The email you want config alerts sent to:
The snmp community you want me to use:
For snmp, please protect it with an ACL:
snmp-server community <your community name here> RW 10
access-list 10 permit 199.166.5.172
-brian
On Thu, Mar 06, 2014 at 10:48:56PM -0500, Dave McGuire wrote:
The tunnel between here and Mark's network is outside of the 5x
numeric range that the autogeneration system uses, so they won't buck
heads. Let's fold him into that system when you get it all up and running.
-Dave
On 03/06/2014 10:30 PM, Brian Hechinger wrote:
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
--
Dave McGuire, AK4HZ
New Kensington, PA
The tunnel between here and Mark's network is outside of the 5x
numeric range that the autogeneration system uses, so they won't buck
heads. Let's fold him into that system when you get it all up and running.
-Dave
On 03/06/2014 10:30 PM, Brian Hechinger wrote:
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
--
Dave McGuire, AK4HZ
New Kensington, PA
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
On Thu, 6 Mar 2014, Brian Hechinger wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
Done.
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Reloading router: 50.73.179.1 xxxx 199.166.5.172 tunnel-gw.neurotica.com-ipv4.txt
running........
successful
Reloading router: 208.73.57.126 xxxxxx 199.166.5.172 tunnel-hub.platinum.net-ipv4.txt
Error reloading router: hub.platinum.net :: No SNMP response received before timeout
Reloading router: 10.42.255.33 xxxxxxxxxx 199.166.5.172 tunnel-bart.4amlunch.net-ipv4.txt
running...........................................................................................................................................................
successful
Reloading router: 75.49.17.245 xxxxxxxxxx 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
Reloading router: 50.73.179.1 xxxx 199.166.5.172 tunnel-gw.neurotica.com-ipv4.txt
running........
successful
Reloading router: 208.73.57.126 xxxxxx 199.166.5.172 tunnel-hub.platinum.net-ipv4.txt
Error reloading router: hub.platinum.net :: No SNMP response received before timeout
Reloading router: 10.42.255.33 xxxxxxxxxx 199.166.5.172 tunnel-bart.4amlunch.net-ipv4.txt
running...........................................................................................................................................................
successful
Reloading router: 75.49.17.245 xxxxxxxxxx 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
-brian
