On 10 Jan 2013, at 15:52, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:51 PM, Cory Smelosky wrote:
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router.;)
I got a different error though when that happened.
What error?
I got Host unreachable before.
Before it was: my end -> VPN -> SIMH on vps -> SG1
Now it's: my end -> Dave's cisco using a GRE tunnel. Anything we're forgetting to update?
-brian
On 1/10/2013 3:51 PM, Cory Smelosky wrote:
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router.;)
>
>I got a different error though when that happened.
What error?
I got Host unreachable before.
-brian
On 10 Jan 2013, at 15:50, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:49 PM, Cory Smelosky wrote:
On 10 Jan 2013, at 15:48, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router. ;)
I got a different error though when that happened.
What error?
-brian
On 1/10/2013 3:49 PM, Cory Smelosky wrote:
On 10 Jan 2013, at 15:48, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router. ;)
I got a different error though when that happened.
-brian
On 10 Jan 2013, at 15:48, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router. ;)
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
On 10 Jan 2013, at 10:00, Cory Smelosky <b4 at gewt.net> wrote:
On 10 Jan 2013, at 09:47, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
There used to be, but I removed the multinet tunnel connection and removed it from the VPN.
What I'm getting at is do you have a split area with no link between the "halves"?
There shouldn't be anymore. Unless SG1 is still trying to link me despite that link being down.
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
-brian
On 10 Jan 2013, at 09:47, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
There used to be, but I removed the multinet tunnel connection and removed it from the VPN.
What I'm getting at is do you have a split area with no link between the "halves"?
There shouldn't be anymore. Unless SG1 is still trying to link me despite that link being down.
-brian
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
What I'm getting at is do you have a split area with no link between the "halves"?
-brian
On 10 Jan 2013, at 09:38, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/9/2013 10:29 PM, Cory Smelosky 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.
Just to throw my own data out there for you, from 52.1:
bart#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 = 24/25/28 ms
bart#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 100 percent (5/5), round-trip min/avg/max = 144/220/260 ms
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds:
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Success rate is 0 percent (0/5)
bart#
What does show decnet route show as the router for area 9?
