Hello !
-----Oorspronkelijk bericht-----
Van: Jonathan NAYLOR <[EMAIL PROTECTED]>
>Hi
>
>> My neighbour node does not send it's NET/ROM broadcasts to NODES but to
>> a specified callsign (PI8ZAA in this case).
>
>This is breaking the NET/ROM protocol. Routing messages should be sent to
>NODES, and that is all.
>
>
>I am not sure it is something that we should want to do. In this case
>your neighbour is breaking the protocol and I do not believe that we
>should be doing likewise. Get him to fix his software, what is he
>running anyway ?
Changing the netrom-broadcast adress is possible in CHL-NET for a long time.
This feature is very usefull to prevent 'false-routes'.
Here in the Netherlands we have a interlink-network on 23cm. All interlink
stations are using dedicated link-frequencies, so no user access is
possible. Normally only the other-side of the link is heard on this
frequency. However, when tropo-conditions are above normal, it is possible
that you hear other interlinks which are at a few hundred kilometers
distance and using the same channel.
When this station is transmitting a 'NODES' broadcast, those routes would be
picked-up by the distant station too. As this node cannot be reached, this
would cause a mess-up of the netrom destinations.
PE1CHL implemented the feature where you can change the destination address
and set it to the call of your link-partner. Now only your link-partner will
pick-up this broadcast.
So this is only used on point-to-point links. On general user-access
channels it will be set to 'NODES' (if broadcast is enabled on
user-channels) So this 'extention' will never cause conflicts and there is
no need to 'fix' this software.
As this can be easy configured for every port, it should just be set to
'nodes' on PI1EHV so PI8ZAA will pick-up routes again. Sure they know this
at PI8ZAA/PI1EHV, but I think it was just a question to check if LINUX could
be configured in the same way.
Regards,
Cees Tool - PA3AES
