At the moment, HECnet is somewhat split, since a central router isn't up and running. So not everyone can reach area 2. :-(
That's sad. :-(
What's needed to fix that?
--Marc
Marc Chametzky wrote:
If anyone wants to try PHONE this evening, I'm logged into my VMS system as DUSTY::MARC. Old fashioned chatting at its best. :-)
(DUSTY is a relatively new node. For those who don't have the address, it's 2.210.)
At the moment, HECnet is somewhat split, since a central router isn't up and running. So not everyone can reach area 2. :-(
Johnny
Sampsa Laine wrote:
Now correct me if I'm wrong but at least my bridge setup file has a DNS address in it, not an IP address. Will Johnny's bridge not work against a DynDNS type setup?
Sorry, but no.
While I do name lookups, I'm not doing it for every packet that goes out, or comes in. It's done at startup, and when the config file is re-read. So if someones address change, the bridge program will "stop working".
Johnny
Sampsa
On 18 Aug 2008, at 21:28, Fred wrote:
Hello all ...
After a bit of communication with a list member off-list, it seems that my dynamic IP address scenario is going to throw a wrench into the works regarding getting on to HECNet. Would someone know of a dynamic-address friendly method? I have DSL here, and switching to cable isn't an option as they block ports and are generally nasty around here. Static DSL is a last resort option as I'd rather not double my DSL bill if I don't have to.
I do not want anyone to have to "babysit" my connection to the network - if there's any babysitting to be done, I'll do it - or write some DCL to automate it, or what-have-you.
Do I have any options?
Cheers,
Fred
Marc Chametzky wrote ...
$ MCR NCP SET CIRCUIT TCP-x-y STATE OFF
$ MULTINET SET/DECNET/REMOTE=a.b.c.d/CONNECT
$ MCR NCP SET CIRCUIT TCP-x-y STATE ON
Yes, you could do this. The only part missing is something that queries
DNS to determine the actual IP address. That's do-able too, but not quite
as trivial.
One could also reflect this change in MULTINET:DECNET-CIRCUITS.COM to
save the change for later (best done indirectly through MULTINET
CONFIGURE/DECNET).
You'd have to; otherwise the next time you rebooted the new IPs would go
away.
Does DECnet routing require explicitly created paths to avoid routing
loops, or can one have multiple parallel connections and have DECnet
manage the routing dynamically?
The short answer is that this is what circuit costs are for - in the event
of multiple paths, DECnet will pick the least cost route to the destination.
Having multiple paths from node A to node B isn't supposed to be a problem.
Bob
On Mon, 18 Aug 2008, Marc Chametzky wrote:
I was looking through the MultiNet configuration and it looks as though it might be possible to get it to handle dynamic addresses somewhat reasonably.
[cut]
Also, in lieu of Multinet and DECNet-over-IP - I've been able to get the bridge program to run on my Linux firewall, although I'm having some difficulty deciphering the config file format. Perhaps my lack of valid entries to stick in there is the thorn in my side ... :-/
Bridge compiled fine on my main Linux server, and FTP'ed over to the Smoothwall box with no problems and no complaining of missing libraries.
Fred
I was looking through the MultiNet configuration and it looks as though it might be possible to get it to handle dynamic addresses somewhat reasonably.
Assuming one had a script to check the status of the DECnet circuit or otherwise check to see if the dyndns.org address had changed, one can cycle the circuit to connect to the new address this way:
$ MCR NCP SET CIRCUIT TCP-x-y STATE OFF
$ MULTINET SET/DECNET/REMOTE=a.b.c.d/CONNECT
$ MCR NCP SET CIRCUIT TCP-x-y STATE ON
One could also reflect this change in MULTINET:DECNET-CIRCUITS.COM to save the change for later (best done indirectly through MULTINET CONFIGURE/DECNET).
Does DECnet routing require explicitly created paths to avoid routing loops, or can one have multiple parallel connections and have DECnet manage the routing dynamically? If so, I'm willing to help with DECnet routing since I've got an area router running on my virtual VAX and a high-speed FiOS connection at home.
--Marc
On Mon, 18 Aug 2008, Sampsa Laine wrote:
Now correct me if I'm wrong but at least my bridge setup file has a DNS address in it, not an IP address. Will Johnny's bridge not work against a DynDNS type setup?
(replying to list)
Hi Sampsa ...
I'm willing to run the bridge if needed. I have a Smoothwall Linux firewall here that I'm sure I could shoehorn the bridge onto.
I would guess when my IP changes the bridge would disconnect, and then attempt to reconnect to whatever my new IP address happens to be. What kind of OPCOM messages that might generate is left as an exercise to the reader. :)
I'm going to download the bridge software and see if I can get it working (or at least compiled ...) on the Smoothwall ...
Fred
If anyone wants to try PHONE this evening, I'm logged into my VMS system as DUSTY::MARC. Old fashioned chatting at its best. :-)
(DUSTY is a relatively new node. For those who don't have the address, it's 2.210.)
--Marc
Now correct me if I'm wrong but at least my bridge setup file has a DNS address in it, not an IP address. Will Johnny's bridge not work against a DynDNS type setup?
Sampsa
On 18 Aug 2008, at 21:28, Fred wrote:
Hello all ...
After a bit of communication with a list member off-list, it seems that my dynamic IP address scenario is going to throw a wrench into the works regarding getting on to HECNet. Would someone know of a dynamic-address friendly method? I have DSL here, and switching to cable isn't an option as they block ports and are generally nasty around here. Static DSL is a last resort option as I'd rather not double my DSL bill if I don't have to.
I do not want anyone to have to "babysit" my connection to the network - if there's any babysitting to be done, I'll do it - or write some DCL to automate it, or what-have-you.
Do I have any options?
Cheers,
Fred
Hello all ...
After a bit of communication with a list member off-list, it seems that my dynamic IP address scenario is going to throw a wrench into the works regarding getting on to HECNet. Would someone know of a dynamic-address friendly method? I have DSL here, and switching to cable isn't an option as they block ports and are generally nasty around here. Static DSL is a last resort option as I'd rather not double my DSL bill if I don't have to.
I do not want anyone to have to "babysit" my connection to the network - if there's any babysitting to be done, I'll do it - or write some DCL to automate it, or what-have-you.
Do I have any options?
Cheers,
Fred
