LAN costs are 4 by default (for VMS nodes anyway).
Maybe on VMS, but check MIM - the UNA-0 cost is 3, not 4.
I've seen both values used; I think the default must vary depending on the
system or OS version.
Bob
One script does it all. I am reworking the script so that the host will
not have to reboot. Should be ready later today. The only issue left
is the email forwarder is down (CHIMPY::). I am setting up this end to
become an email forwarder/Internet gateway.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Mark Wickens
Sent: Tuesday, December 27, 2011 8:20 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] ROOSTA routing problem
Steve Davidson has a few scripts which will detect an IP address change,
reconfigure the link and reboot the system. Assuming the IP only changes
'once in a while' this is a fairly painless solution.
Mark.
On 27/12/11 12:08, Peter Lothberg wrote:
On 26/12/2011 18:39, Mark Benson wrote:
On 26 Dec 2011, at 16:00, Bob Armstrong wrote:
I assumed (perhaps stupidly) that as long as Chrissie's machines
are
bridged onto HECnet somewhere using Johnny's bridge,
She's not using the bridge, though. ROOSTA has a multinet
connection to
LEGATO (which I don't mind, but as Johnny said, isn't going to
work).
Okay, well STAR69 has Multinet on it but as for tunnelling between
them
I ain't got a clue, chief, and again I can't guarantee 100% uptime
on the
link if it is opened.
So can you set up a multinet link to chrissie.homelinux.net (warning
IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP
address
and I'll set up a multinet link here. That should do.
If it does down sometimes we'll just have to live with the
consequences ;-)
Chrissie
Someone had "magic" to deal with changing adresses?
Sure I can set up a link, and I'll suggest metric 5..
The VAXen with multinet is 192.108.200.211.
-P
Hey folks...
LAN costs are 4 by default (for VMS nodes anyway). If we make use of
that then all we have to touch are the Multinet circuits. I set my
Multinet circuits to 3 because they are much faster and I would prefer
to use the most "efficient" path possible. You will loose the ability
to use SET HOST/LAT, and MOM/MOP, and LAD/LAST, but that should me
minor...
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Bob Armstrong
Sent: Tuesday, December 27, 2011 10:00 AM
To: hecnet at Update.UU.SE
Subject: [HECnet] Circuit costs
Peter Lothberg wrote:
Here is a suggestion....
Set all Multinet links to cost 5 in both ends
Set all bridged Ethernet interfaces to 10
Set all Multinet link nodes Level2 Area Routers
Well, I like it. I'll do it if you do it...
Actually that's a problem with DECnet - everybody _has_ to do their
own;
circuit costs are individually defined per node.
Bob
Peter Lothberg wrote:
Here is a suggestion....
Set all Multinet links to cost 5 in both ends
Set all bridged Ethernet interfaces to 10
Set all Multinet link nodes Level2 Area Routers
Well, I like it. I'll do it if you do it...
I did it on my side.
Actually that's a problem with DECnet - everybody _has_ to do their own;
circuit costs are individually defined per node.
It's the smae problem if you use OSPF or ISIS for IP... -:)
-Peter
(The person you should complain to in this case is Radia Perlman..)
Peter Lothberg wrote:
Here is a suggestion....
Set all Multinet links to cost 5 in both ends
Set all bridged Ethernet interfaces to 10
Set all Multinet link nodes Level2 Area Routers
Well, I like it. I'll do it if you do it...
Actually that's a problem with DECnet - everybody _has_ to do their own;
circuit costs are individually defined per node.
Bob
On 27 Dec 2011, at 13:16, Chrissie Caulfield wrote:
Hmm nothing is showing up at my end. Doe you have a firewall blocking
port 700/udp ?
Yes. I can open that though. Be warned that my UDP forwarding abilities
seem a bit patchy based on what Johnny and I found out when I joined HECnet
via the bridge.
Though I think you said you already had multinet running to other nodes,
so that sounds unlikely.
No I don't. I run MUTLINET as my IP stack on that machine but I have no
other links, hence why I didn't know how to set one up :)
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
Steve Davidson has a few scripts which will detect an IP address change, reconfigure the link and reboot the system. Assuming the IP only changes 'once in a while' this is a fairly painless solution.
Mark.
On 27/12/11 12:08, Peter Lothberg wrote:
On 26/12/2011 18:39, Mark Benson wrote:
On 26 Dec 2011, at 16:00, Bob Armstrong wrote:
I assumed (perhaps stupidly) that as long as Chrissie's machines are
bridged onto HECnet somewhere using Johnny's bridge,
She's not using the bridge, though. ROOSTA has a multinet connection to
LEGATO (which I don't mind, but as Johnny said, isn't going to work).
Okay, well STAR69 has Multinet on it but as for tunnelling between them
I ain't got a clue, chief, and again I can't guarantee 100% uptime on the
link if it is opened.
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
If it does down sometimes we'll just have to live with the consequences ;-)
Chrissie
Someone had "magic" to deal with changing adresses?
Sure I can set up a link, and I'll suggest metric 5..
The VAXen with multinet is 192.108.200.211.
-P
On 27/12/2011 12:36, Mark Benson wrote:
On 27 Dec 2011, at 12:00, Chrissie Caulfield wrote:
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Okay, done. Assuming that was the right IP, we'll see what
happens :)
Hmm nothing is showing up at my end. Doe you have a firewall blocking
port 700/udp ?
Though I think you said you already had multinet running to other nodes,
so that sounds unlikely.
Chrissie
On 27 Dec 2011, at 12:00, Chrissie Caulfield wrote:
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Okay, done. Assuming that was the right IP, we'll see what
happens :)
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 27/12/2011 10:57, Mark Benson wrote:
On 27 Dec 2011, at 10:43, Chrissie Caulfield wrote:
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
I honestly haven't the first clue how.
My IP is 213.123.127.24 if you want to set your end up.
It's pretty easy, just type the following on the VAX when logged in as SYSTEM (typing is in bold, if you can see that)
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Chrissie
