Thank you!
I am new to VMS so some of its useful facilities (as HELP /MESSAGE) not yet
known to me.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Peter Coghlan
Sent: Sunday, November 27, 2011 9:17 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Linker warnings
Can anyone bring some light on these linker warnings:
%LINK-W-TRUNC, truncation error in psect CODE offset %X0000046C
in module XXX file YYY
-LINK-W-TRUNCDAT, computed value is %X00000080
value written is %XFFFFFF80 at location %X0000A2B8
Assuming this is VMS, $ HELP /MESSAGE says:
TRUNCDAT, computed value is 'value1'
value written is 'value2' at location 'address'
Facility: LINK, Linker Utility
Explanation: Usually, this error occurs when a reference using byte or
word PC-relative displacement is made to a target requiring
longword relative displacement. 'Value1' is the value the
linker needed to store; 'value2' is the value the linker is
able to store (a truncated version).
User Action: Correct the reference to use longword relative addressing
mode.
For something more specific, it would help to know more background.
Regards,
Peter Coghlan.
Can anyone bring some light on these linker warnings:
%LINK-W-TRUNC, truncation error in psect CODE offset %X0000046C
in module XXX file YYY
-LINK-W-TRUNCDAT, computed value is %X00000080
value written is %XFFFFFF80 at location %X0000A2B8
Assuming this is VMS, $ HELP /MESSAGE says:
TRUNCDAT, computed value is 'value1'
value written is 'value2' at location 'address'
Facility: LINK, Linker Utility
Explanation: Usually, this error occurs when a reference using byte or
word PC-relative displacement is made to a target requiring
longword relative displacement. 'Value1' is the value the
linker needed to store; 'value2' is the value the linker is
able to store (a truncated version).
User Action: Correct the reference to use longword relative addressing
mode.
For something more specific, it would help to know more background.
Regards,
Peter Coghlan.
Hi all!
Can anyone bring some light on these linker warnings:
%LINK-W-TRUNC, truncation error in psect CODE offset %X0000046C
in module XXX file YYY
-LINK-W-TRUNCDAT, computed value is %X00000080
value written is %XFFFFFF80 at location %X0000A2B8
Thanks.
He is on this mailinglist...
Johnny
On 2011-11-26 19.11, Steve Davidson wrote:
Send a mail message to:
gerry77 at mail.com
He should be able to provide you with a list of nodenames (and
addresses).
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Saturday, November 26, 2011 11:25 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 15:37, Bob Armstrong wrote:
Johnny wrote:
That is not really a big issue. DECnet do not have a requirement for
a coherent nodename database. Every machine can have its own.
This is technically true, but it's really not very useful to have a
network with duplicate node names. After all, if I post a message
saying "phone me on ABC::" or "copy these files from XYZ::" and half
the users have a different ABC or XYZ, then people are not going to be
happy.
Yeah. That is very true. However, you could just have a subset that is
"common", and then have your own names for local machines that noone
else cares about, and name conflict between such machines wouldn't be an
issue.
But that is up to people to decide how they want it. I like it better to
have a global name space, and all my machines pick the nodename database
from MIM so I have them as much in synch as possible. I occasionally
also ping people when I notice nodes for which I have no name, but from
which communication have been visible.
Sure, it may be that the Italian guys never access our nodes and
vice versa, but if that's true then what's the point in integrating?
Yup.
P.S. Does anybody have a list of the nodes on the Italian network?
I can probably get a list... But how about exploring if they'd be
interested in hooking up first maybe?
Johnny
Send a mail message to:
gerry77 at mail.com
He should be able to provide you with a list of nodenames (and
addresses).
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Saturday, November 26, 2011 11:25 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 15:37, Bob Armstrong wrote:
Johnny wrote:
That is not really a big issue. DECnet do not have a requirement for
a coherent nodename database. Every machine can have its own.
This is technically true, but it's really not very useful to have a
network with duplicate node names. After all, if I post a message
saying "phone me on ABC::" or "copy these files from XYZ::" and half
the users have a different ABC or XYZ, then people are not going to be
happy.
Yeah. That is very true. However, you could just have a subset that is
"common", and then have your own names for local machines that noone
else cares about, and name conflict between such machines wouldn't be an
issue.
But that is up to people to decide how they want it. I like it better to
have a global name space, and all my machines pick the nodename database
from MIM so I have them as much in synch as possible. I occasionally
also ping people when I notice nodes for which I have no name, but from
which communication have been visible.
Sure, it may be that the Italian guys never access our nodes and
vice versa, but if that's true then what's the point in integrating?
Yup.
P.S. Does anybody have a list of the nodes on the Italian network?
I can probably get a list... But how about exploring if they'd be
interested in hooking up first maybe?
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 2011-11-26 15:37, Bob Armstrong wrote:
Johnny wrote:
That is not really a big issue. DECnet do not have a requirement for a
coherent nodename database. Every machine can have its own.
This is technically true, but it's really not very useful to have a
network with duplicate node names. After all, if I post a message saying
"phone me on ABC::" or "copy these files from XYZ::" and half the users have
a different ABC or XYZ, then people are not going to be happy.
Yeah. That is very true. However, you could just have a subset that is "common", and then have your own names for local machines that noone else cares about, and name conflict between such machines wouldn't be an issue.
But that is up to people to decide how they want it. I like it better to have a global name space, and all my machines pick the nodename database from MIM so I have them as much in synch as possible. I occasionally also ping people when I notice nodes for which I have no name, but from which communication have been visible.
Sure, it may be that the Italian guys never access our nodes and vice
versa, but if that's true then what's the point in integrating?
Yup.
P.S. Does anybody have a list of the nodes on the Italian network?
I can probably get a list... But how about exploring if they'd be interested in hooking up first maybe?
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
Johnny wrote:
That is not really a big issue. DECnet do not have a requirement for a
coherent nodename database. Every machine can have its own.
This is technically true, but it's really not very useful to have a
network with duplicate node names. After all, if I post a message saying
"phone me on ABC::" or "copy these files from XYZ::" and half the users have
a different ABC or XYZ, then people are not going to be happy.
Sure, it may be that the Italian guys never access our nodes and vice
versa, but if that's true then what's the point in integrating?
Bob
P.S. Does anybody have a list of the nodes on the Italian network?
Yes, it's called DTR
------Origineel bericht------
Van: Fred
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Integrating with the Italian network.
Verzonden: 26 november 2011 13:51
On Sat, 26 Nov 2011, Johnny Billquist wrote:
Anyone else could do the same trick, using the remote datatrieve interface to
access the nodename database on MIM, and setting up the local nodename
database. That would also allow you to pick just certain areas, or whatnot...
Speaking of Datatrieve - is there a hobbyist license for this?
Fred
On Sat, 26 Nov 2011, Johnny Billquist wrote:
Anyone else could do the same trick, using the remote datatrieve interface to access the nodename database on MIM, and setting up the local nodename database. That would also allow you to pick just certain areas, or whatnot...
Speaking of Datatrieve - is there a hobbyist license for this?
Fred
On 2011-11-26 13.19, H Vlems wrote:
I wasn't aware that moving to TCP would result in all that. UDP and TCP both
use the same IP addressing functionality. Only UDP is connectionless, i.e.
doesn't use acknowledgement messages and is thus a little faster than TCP
but less reliable. An IP address change is as much as a problem for UDP as
it is for TCP, I'd say.
Yes. IP address change is as much a "problem" for UDP as TCP. But at the same time not. :-)
In TCP, if the other end changes the IP address, the TCP connection will be reset, and your program will get an error returned. Thus you notice this. In UDP, you will continue to transmit as if nothing happened. In fact, nothing have changed from the UDP point of view. Packets are still sent to that same address. Only, there might now be some other machine receiving them than before. What that machine does is not something you have any control over (of course, a clever prgorammer can make the same happen for TCP, but it requires a lot of work, while in UDP it is the only behavior).
There is much more difference between TCP and UDP than the connection/connectionless issue. Of course, you could argue that everything else follows, but not neccesarily.
TCP do not have the concept of "packets". It's all a stream of bytes. As such, there is no guarantee that because you wrote 1500 bytes in one write, the receiver will receive 1500 bytes in one read. The receiver could just as well get three reads of 500 bytes each.
Also, TCP guarantees that data arrive in the same order it was sent. Thus, if the underlying layer loses a packet, TCP will buffer and resend data in order to keep its guarantee. So later data will be buffered, and not delivered, even if it have arrived, until older data have been delivered.
Also, in order to make sure the network is used optimally, TCP can keep from sending data, in order to make packets more "full". This is called the Nagle algorithm, and it can be disabled, but you are still not guaranteed that buffering will not happen somewhere between source and destination, or that TCP won't introduce delays.
And then you have various congestion control algorithms, slow start, and what not.
And of course, at connection time, you have the handshaking that must happen before the connection can be used.
UDP on the other hand guarantees nothing. Packets might be lost, duplicated, delivered out of order, and whatnot. In fact, pretty much (for the most part) just the same as ethernet. And packets are written whole, or not at all, and read the same. One write is delivered in one read. UDP have *packets*, not a stream of bytes.
Security is another issue. As you wrote, authentication is sent as clear
text so is not secure. Then again, it may only be used if there is a
connection to HECnet and that would make no difference anyhow.
With the current scheme in HECnet, packets are not accepted from unknown hosts (IP addresses), so random people cannot inject ethernet packets through the bridge to your local ethernet. Also, your local ethernet packets are not sent to any random host, but only hosts you have listed the address for in the bridge program.
It is way less than secure, but it do avoid the most glaring problems.
Encryption is fine, but it is an up hill struggle: it requires continuous
attention to keep up with technology. I doubt if HECnet is worth that
struggle.
Yeah. I don't think it is. :-)
And sorry for the long ramble about network technologies. :-)
Johnny
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: zaterdag, november 2011 12:59
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 12.48, Johnny Billquist wrote:
On 2011-11-26 12.05, H Vlems wrote:
What I've read about the "enhancements" to the bridge program is yet
another
matter. First off, it ain't called bridge for nothing: like any layer 2
bridge the program moves packets between ports and is transparent to both
the content of the datagrams and the functionality of the protocol.
Including DNS like functionality violates that rule.
I also wanted to keep the complexity and overhead down. Otherwise, yes,
you could change from UDP to TCP, include SSL, and certificates, to make
sure we keep it safe. But that would incur quite some costs both from an
administrative point of view, as well as lots more CPU resources to run
the bridge, and also more problems in porting it to other systems.
To expand, perhaps, a little here.
If we switched to TCP, any change in IP addresses would be detected
"immediately", since the TCP connection would be lost at an IP change.
At that point, the bridge would need to re-resolve the address, and try
to establish a connection again. That would have to be repeated
regularly until a connection comes up. Since this is very blocking, we'd
have to change the bridge to be threaded, so that you have one thread
per connection. And then queue packets inside the bridge, with throwing
away when queues become to large, in order to prevent other connections
from becoming affected.
In addition, this would affect the complexity of things like config
reloads. Everything is, as usual, doable, but the work involved is not
trivial. And then, of course, we have all the certificate issues, and
all the code to deal with them.
And then, also, TCP can introduce unwanted network delays and
burstiness. It really don't fit well with what the bridge do. It
provides services not really needed.
And I really like simple solutions... :-)
Johnny
