On 9 Jan 2013, at 22:54, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Any node in area 61 I can reach. Seems any node in area 61 can reach my area, too.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-10 04:44, Dave McGuire wrote:
On 01/09/2013 10:40 PM, Johnny Billquist wrote:
In that case, the next question is obviously how the DECnet routing
table at 61.1 looks like.
Area Cost Hops Next Hop to Node Expires Prio
*1 11 2 Tunnel5 -> 59.11
*2 11 2 Tunnel5 -> 59.11
*3 14 3 Tunnel5 -> 59.11
*4 11 2 Tunnel5 -> 59.11
*5 11 2 Tunnel5 -> 59.11
*6 11 2 Tunnel5 -> 59.11
*7 12 3 Tunnel5 -> 59.11
*8 11 2 Tunnel5 -> 59.11
*9 10 1 Tunnel6 -> 9.1023 38 64 A+
*11 11 2 Tunnel5 -> 59.11
*12 11 2 Tunnel5 -> 59.11
*18 12 3 Tunnel5 -> 59.11
*19 11 2 Tunnel5 -> 59.11
*20 12 3 Tunnel5 -> 59.11
*28 11 2 Tunnel5 -> 59.11
*33 12 3 Tunnel5 -> 59.11
*42 10 1 Tunnel4 -> 42.1023 35 64 A+
*44 11 2 Tunnel5 -> 59.11
*47 13 3 Tunnel5 -> 59.11
*51 13 3 Tunnel5 -> 59.11
*52 10 1 Tunnel1 -> 52.1 37 64 A+
*59 10 1 Tunnel5 -> 59.11 41 64 A+
Can you get any kind of statistics show how many packets are being routed, and possibly over which tunnels? Or atleast how many packets are sent/received on each tunnel?
Actually, why don't you have an entry for area 61 in your routing table?
That's a damn good question.
I also notice that you don't seem to have an area 61 yourself here, Dave. That might explain why Cory don't get one. But the setup looks weird because of this.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
Actually, why don't you have an entry for area 61 in your routing table?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 01/09/2013 10:35 PM, Johnny Billquist wrote:
However! Despite this tunnel being identical to the other tunnels, I
am unable to reach the rest of HECnet via the tunnel to him.
...
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router...
It is, and there are other tunnels terminating here which are working.
Unfortunately I am buried in work tonight and can't hack on this much
further. Do you have any thoughts on what might be screwing things up?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:29, Cory Smelosky wrote:
Hello, all!
Dave and I have been attempting to establish a link between us using dynamips on my end, and real cisco gear on his end and we've hit some issues.
The GRE tunnel comes up fine, I can ping DECnet nodes on his end, and I can set host to nodes in his area. It is also possible for nodes in his area to reach nodes in my area so packets are indeed getting /somewhere/.
However! Despite this tunnel being identical to the other tunnels, I am unable to reach the rest of HECnet via the tunnel to him.
Here's the output of SHOW DECNET ROUTE:
---
marianne#sh decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 16 3 Tunnel0 -> 61.1
*2 16 3 Tunnel0 -> 61.1
*3 19 4 Tunnel0 -> 61.1
*4 16 3 Tunnel0 -> 61.1
*5 16 3 Tunnel0 -> 61.1
*6 16 3 Tunnel0 -> 61.1
*7 18 4 Tunnel0 -> 61.1
*8 16 3 Tunnel0 -> 61.1
*9 0 0 (Local) -> 9.1023
*11 16 3 Tunnel0 -> 61.1
*12 16 3 Tunnel0 -> 61.1
*18 17 4 Tunnel0 -> 61.1
*19 16 3 Tunnel0 -> 61.1
*20 17 4 Tunnel0 -> 61.1
*28 16 3 Tunnel0 -> 61.1
*33 17 4 Tunnel0 -> 61.1
*42 15 2 Tunnel0 -> 61.1
*44 16 3 Tunnel0 -> 61.1
*47 18 4 Tunnel0 -> 61.1
*51 18 4 Tunnel0 -> 61.1
*52 15 2 Tunnel0 -> 61.1
*59 15 2 Tunnel0 -> 61.1
---
And ping:
---
marianne#ping 61.1
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 61.1, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/56/76 ms
marianne#ping 61.3
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 61.3, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/56/68 ms
marianne#ping 1.13
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 1.13, timeout is 5 seconds:
.....
Success rate is 0 percent (0/5)
---
My tunnel config:
---
interface Tunnel0
description Tunnel to HECnet (Dave)
no ip address
decnet cost 5
tunnel source Ethernet1/0
tunnel destination <his ip>
tunnel path-mtu-discovery
---
Ethernet1/0:
---
interface Ethernet1/0
ip address 10.10.10.99 255.255.255.0
no ip route-cache
duplex full
decnet cost 10
---
Overall DECnet config:
---
decnet routing 9.1023
decnet node-type area
---
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
