Select port tcp-0-19 and modify the address.
FWIW, you cannot actually enter "bridge.declab.net" into Multinet - it
only accepts a dotted IP address.
Bob
Mark,
$multinet configure/menu
Select DECnet over IP, or something like that. Select port tcp-0-19
and modify the address. Save and exit. This will fix the "permanent"
database, but not the the in-memory copy. You can either fix that
manually, or reboot. It has been a while since I've done the manual
mode, so I would have to look that up myself, but rebooting will check
to see that everything works for startup. This should be done
periodically anyway.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Benson
Sent: Wednesday, March 21, 2012 10:11
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Eastern US HECnet hub will be down this Friday
Can you give me some idea how to check Multinet? I let you
set it up remotely and I don't know what/how to check it >.<
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 21 Mar 2012, at 14:04, "Steve Davidson" <jeep at scshome.net> wrote:
The Eastern US HECnet hub will be down this Friday due to static IP
address reassignment and bandwidth increases. Any systems that
currently connect to IP address 69.21.253.230 should change to
bridge.declab.net. This includes bridge and Multinet Tunnel
connections as well as UUHEC (UUCP port 540) connections.
Regards,
-Steve
I know that part, I meant to check in Multinet to see
where my tunnel was connecting to at Steve's end :)
It's in MULTINET:DECNET-CIRCUITS.COM.
--
Regards, Rok
I know that part, I meant to check in Multinet to see where my tunnel was connecting to at Steve's end :)
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 21 Mar 2012, at 16:20, Rok Vidmar <rok.vidmar at gmail.com> wrote:
Can you give me some idea how to check Multinet? I let you set
it up remotely and I don't know what/how to check it >.<
$ mcr ncp sho kno circ
Known Circuit Volatile Summary as of 21-MAR-2012 17:18:25
Circuit State Loopback Adjacent
Name Routing Node
EWA-0 on
TCP-0-0 on 3.171 (NUK1C)
TCP-0-1 on 3.47 (RVDSXL)
TCP-0-2 on -starting
The other end at TCP-0-2 is down.
--
Regards, Rok
Can you give me some idea how to check Multinet? I let you set
it up remotely and I don't know what/how to check it >.<
$ mcr ncp sho kno circ
Known Circuit Volatile Summary as of 21-MAR-2012 17:18:25
Circuit State Loopback Adjacent
Name Routing Node
EWA-0 on
TCP-0-0 on 3.171 (NUK1C)
TCP-0-1 on 3.47 (RVDSXL)
TCP-0-2 on -starting
The other end at TCP-0-2 is down.
--
Regards, Rok
Can you give me some idea how to check Multinet? I let you set it up remotely and I don't know what/how to check it >.<
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 21 Mar 2012, at 14:04, "Steve Davidson" <jeep at scshome.net> wrote:
The Eastern US HECnet hub will be down this Friday due to static IP
address reassignment and bandwidth increases. Any systems that
currently connect to IP address 69.21.253.230 should change to
bridge.declab.net. This includes bridge and Multinet Tunnel connections
as well as UUHEC (UUCP port 540) connections.
Regards,
-Steve
The Eastern US HECnet hub will be down this Friday due to static IP
address reassignment and bandwidth increases. Any systems that
currently connect to IP address 69.21.253.230 should change to
bridge.declab.net. This includes bridge and Multinet Tunnel connections
as well as UUHEC (UUCP port 540) connections.
Regards,
-Steve
On 3/19/2012 4:15 PM, Dave McGuire wrote:
Brian, I think the best way to approach it is to just try this:
interface Tunnel1
no ip address
decnet cost 10
bridge-group 1
You know, I was thinking about this. I don't think you should need to do the bridge-group if all you want to do is DECnet routing.
Let's try it without. :-D
-brian
On 03/20/2012 10:18 AM, Brian Hechinger wrote:
Another possibility might be to to just bridge everything across the
tunnel, then use ACLs to filter on EtherType (DECnet Phase IV is 0x6003):
We'll have to do some testing, but I don't *think* we should need to do
that. I'll check with some cisco guys smarter than me.
What'd you find out? I'm ready to start hacking whenever you are.
access-list 200 permit 0x6003
...
interface Tunnel1
no ip address
bridge-group 1 input-type-list 200 # or output-type-list?www
What about LAT/MOP/etc? I'm assuming we may or may not want to allow those?
Definitely LAT, but I kinda think not for MOP. I mean, everyone has a copy of PR0801ENG.SYS, right? ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 3/19/2012 4:15 PM, Dave McGuire wrote:
Brian, I think the best way to approach it is to just try this:
interface Tunnel1
no ip address
decnet cost 10
bridge-group 1
Sometimes the simplest approach is best. =) Offhand I don't see why that wouldn't work.
We'll find out, but I don't see why it wouldn't.
Another possibility might be to to just bridge everything across the tunnel, then use ACLs to filter on EtherType (DECnet Phase IV is 0x6003):
We'll have to do some testing, but I don't *think* we should need to do that. I'll check with some cisco guys smarter than me.
access-list 200 permit 0x6003
...
interface Tunnel1
no ip address
bridge-group 1 input-type-list 200 # or output-type-list?www
What about LAT/MOP/etc? I'm assuming we may or may not want to allow those?
-brian
