| |
N1URO > PACKET 12.01.18 19:11l 37 Lines 1319 Bytes #999 (0) @ WW
BID : 58251_N1URO
Read: GUEST
Subj: Re: g7vja > Uronode
Path: IW8PGT<IR2UBX<DB0RES<DB0OVN<DB0GOS<ON0AR<GB7CIP<N1URO
Sent: 180112/1807Z @:N1URO.#CCT.CT.USA.NOAM #:58251 [Unionville] $:58251_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : PACKET@WW
Kenny;
As Paul G4APL states, this has to do with the poor use of ax25udp not with
URONode. URONode is a front end which allows end users to connect to you and
use whatever services your system offers. Any and all gateway services such
as node connects, etc is relied upon by the settings/configs of the ax25-apps/
ax25-tools packages.
As for ax25udp, this in my opinion should never be used for the following
reasons:
1 - if you're using linux, you should have NO trouble obtaining and using a
static amprnet IP.
2 - if you have a static amprnet IP, use axIP instead of axUDP. UDP is a
non error-correcting protocol
3 - only accept links with those on amprnet. At least you have that extra
check that your link partner is also a LICENSED operator. NON Licensed
operators have fudged their way into the amateur radio NetRom network.
4 - links won't change IPs. You'll have the error correction of axip, and
you won't run the risk of your interface possibly dying because one link
refuses to get a static amprnet ip.
Your error is caused, as Paul said, by a dynamic IP remote you link to that
either:
- is offline
- IP changed
- they dropped your link.
This is all about the poorness of the ax25udp protocol, not URONode.
73 de N1URO
Read previous mail | Read next mail
| |
