On Sun, Jul 21, 2013 at 12:23:22AM -0000, Cory Smelosky wrote:
On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote:
65.19.130.45
I used the address the email told me to use. ;)
The email told you to use 65.19.130.45, so no you didn't. :)
The one you were using is the old one. The one you were supposed to STOP
using. :)
-brian
On 20 Jul 2013, at 20:23, Cory Smelosky <b4 at gewt.net> wrote:
On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote:
65.19.130.45
I used the address the email told me to use. ;)
New config pulled. Is something not working on my end or has nobody else s tunnel to me come up?
On 20 Jul 2013, at 20:16, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sun, Jul 21, 2013 at 12:09:54AM -0000, Cory Smelosky wrote:
On 20 Jul 2013, at 20:08, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sun, Jul 21, 2013 at 12:04:48AM -0000, Cory Smelosky wrote:
Do you need OSPF? If not, your network isn't crazy enough! :)
I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this?
Why did you need to stop using it? What exactly was the issue? I'll need
to know that first before I can help you work around it. :)
It seems the OSPF packets weren?t actually flowing. RIPng had the same issue. IPv4 stuff (eigrp) still can pass fine.
Oh, so it flat out just stops working on an interface that's in a
bridge-group? Hmm, I'll have to look into that. Never did that before. I
go out of my way to avoid bridge groups if at all possible.
Yeah. It could be multicast related. Not sure. I need the bridge group for LAT.
-brian
On Sun, Jul 21, 2013 at 12:09:54AM -0000, Cory Smelosky wrote:
On 20 Jul 2013, at 20:08, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sun, Jul 21, 2013 at 12:04:48AM -0000, Cory Smelosky wrote:
Do you need OSPF? If not, your network isn't crazy enough! :)
I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this?
Why did you need to stop using it? What exactly was the issue? I'll need
to know that first before I can help you work around it. :)
It seems the OSPF packets weren?t actually flowing. RIPng had the same issue. IPv4 stuff (eigrp) still can pass fine.
Oh, so it flat out just stops working on an interface that's in a
bridge-group? Hmm, I'll have to look into that. Never did that before. I
go out of my way to avoid bridge groups if at all possible.
-brian
On Sun, Jul 21, 2013 at 12:09:12AM -0000, Cory Smelosky wrote:
On 20 Jul 2013, at 19:50, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sat, Jul 20, 2013 at 12:05:32AM -0400, Gregg Levine wrote:
Hello!
Perhaps work got the best of him? Be patient.
Work, yes. It's been crazy.
Home has also been crazy. Had people staying with us all week.
It's done, Cory!
Thanks. Config got emailed to me.
However:
madison#copy tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt running-config
Destination filename [running-config]?
Accessing tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt...
%Error opening tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt (Timed out)
Am I forgetting a NAT rule?
-brian
Yeah, you ignored several emails back. That's no longer the IP this
stuff is found at.
65.19.130.45
Please update to that IP. :)
-brian
On 20 Jul 2013, at 20:08, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sun, Jul 21, 2013 at 12:04:48AM -0000, Cory Smelosky wrote:
Do you need OSPF? If not, your network isn't crazy enough! :)
I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this?
Why did you need to stop using it? What exactly was the issue? I'll need
to know that first before I can help you work around it. :)
It seems the OSPF packets weren t actually flowing. RIPng had the same issue. IPv4 stuff (eigrp) still can pass fine.
-brian
On 20 Jul 2013, at 19:50, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sat, Jul 20, 2013 at 12:05:32AM -0400, Gregg Levine wrote:
Hello!
Perhaps work got the best of him? Be patient.
Work, yes. It's been crazy.
Home has also been crazy. Had people staying with us all week.
It's done, Cory!
Thanks. Config got emailed to me.
However:
madison#copy tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt running-config
Destination filename [running-config]?
Accessing tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt...
%Error opening tftp://216.15.64.181/tunnel-dev.gimme-sympathy.org-ipv4.txt (Timed out)
Am I forgetting a NAT rule?
-brian
On Sun, Jul 21, 2013 at 12:04:48AM -0000, Cory Smelosky wrote:
Do you need OSPF? If not, your network isn't crazy enough! :)
I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this?
Why did you need to stop using it? What exactly was the issue? I'll need
to know that first before I can help you work around it. :)
-brian
On 20 Jul 2013, at 19:51, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sat, Jul 20, 2013 at 06:17:26PM -0000, Cory Smelosky wrote:
On Sat, 20 Jul 2013, Sampsa Laine wrote:
And why you can't access a VM that's downstairs because you didn't make your network config static enough..
True. My network is a bit crazy.
Do you need OSPF? If not, your network isn't crazy enough! :)
I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this?
-brian
