make sure only 'full' PC16s have any effect

diff --git a/Changes b/Changes
index f3f209d8b27381d4b5e1e259fd5fa064c966f41d..5e3e1c049de97fe24518ac26b60d6b79cdb0d1d0 100644 (file)
--- a/Changes
+++ b/Changes
@@ -9,6 +9,10 @@ users, then you can do a set/routepc19 <node> to enable PC19 propagation. In
 the even more rare case of you wanting to prevent PC19s being routed thru 
 your node, you can use unset/routepc19. THIS IS NOT A SUBSTITUTE FOR ROUTE
 FILTERING!!!!! [translators: I have added wpc16s, wpc16u, wpc19s, wpc19u]
+
+BTW the first time you connect again you will notice a separate PC19 go out
+for each 'new' PC16 that the node sees. This is normal and will go away the
+second time the system needs to issue a PC19.
 2. Alter the export_user command to remove users that have no useful info
 and have not been seen for more than (default) 1 year.
 17Jan03=======================================================================

diff --git a/perl/DXProt.pm b/perl/DXProt.pm
index 9a6dabf39224fd25d54b59824ddfe562f59913d7..095b130580ce2760f32607dbb2fafc7d43d53566 100644 (file)
--- a/perl/DXProt.pm
+++ b/perl/DXProt.pm
@@ -645,7 +645,7 @@ sub normal
                        # if there is a parent, proceed, otherwise if there is a latent PC19 in the PC19list, 
                        # fix it up in the routing tables and issue it forth before the PC16
                        unless ($parent) {
-                               if (my $nl = $pc19list{$ncall}) {
+                               if (my $nl = $pc19list{$ncall} && @field > 2) {
 
                                        # this is a new (remembered) node, now attach it to me if it isn't in filtered
                                        # and we haven't disallowed it