From: pa3gcu (asjmmr.zcadkx@kerailya.tunkki.fi)
Date: Sat Sep 29 2001 - 12:00:22 EEST
On Thursday 27 September 2001 05:43, Tomi Manninen OH2BNS wrote:
> Could you explain why these are undesired to you? Remember I was talking
> about fully compliant NET/ROM routing broadcasts sent to a unicast
> address. Nothing fishy, except that the destination address is not NODES
> but your own NETROM callsign.
Yes we were talking about 2 different things, they seemed rather simalar which
is why i churped up.
I dont really like netrom period, but others want to see "nodes" and be able
to connect, if a normall ax25 user connects to a remote system and see no
nodes, then he simply does not know what to do and simply leaves.
But that is besides the point.
>
> > Something like reject a mnemonic that contains an asterisk, i remember
> > way back when Jonathan first started writing netrom into the kernel i
> > sent him a patch which excluded asterisks, or at least tryed to, that
> > same patch inclded upper and lower case letters, (contrary i beleve to
> > RFC) which he did include. This problem seems to be becoming more of a
> > problem thesedays, or am i getting older and too grumpy.?
>
> Nodes with asterisk in the mnemonic field are never propagated in routing
> broadcasts. Also that asterisk is not really the mnemonic. It's just
> something the kernel shows when then mnemonic field is _empty_. Anyway
> those routes also have quality=0 so they are _not_propagated_.
Firstly they do get propergated, secondly the nodes with the asterisk given
to them by the kernel get repropergated as well and on top of that they all
have a quality and certainly not "0".
>
> If you ever see (with listen -a) a NET/ROM routing broadcast with a "*" in
> in then that is 100% a bug and you should report it right away (with
> details). However I'm pretty sure you won't see that.
No i dont see asterisks in broadcasts, what i see is the following.
axip: fm XE2EBC-5 to NODES ctl UI^ pid=CF(NET/ROM) len 238
NET/ROM Routing: CICESE
DB0AAC VE1DRG-7 141
DB0CRL VE1DRG-7 147
DB0LEL VE1DRG-7 155
DB0II MG VE1DRG-7 139
4N1ZKL-5 #KGSWP VE1DRG-7 176
DB0HW VE1DRG-7 138
YU1K KGIP VE1DRG-7 173
HA6KNH-5 KNH VE1DRG-7 183
DB0HSK HSK VE1DRG-7 151
DB0GOS GOS VE1DRG-7 138
N7XS-4 #PIH4 VE1DRG-7 144
I then see with cat /proc/net/nr_nodes | grep -e "*"
DB0CLX-0 * 1 1 120 5 00006
DB0KT-0 * 1 1 119 3 00006
DB0GE-0 * 1 1 120 5 00006
SR6DJC-8 * 1 1 173 4 00006
DB0HW-0 * 1 1 120 3 00006
DB0LEL-0 * 1 1 136 5 00006
DB0CRL-0 * 1 1 137 3 00006
DB0AAC-0 * 1 1 119 5 00006
DB0CLW-0 * 1 1 135 5 00006
HB9AJ-9 * 1 1 153 5 00006
HB9AJ-4 * 1 1 153 5 00006
ON0CK-4 * 1 1 171 4 00006
UT1WPR-2 * 1 1 150 5 00006
OH2RBI-0 * 1 1 173 5 00006
ON1CED-4 * 1 1 168 5 00006
>
> If, on the other hand, you see a broadcast with an empty mnemonic field
> then that is something I'd like to know more about. I don't think this is
> possible either however.
I'm afriad it is.
There are other curcumstancies when "bogus" nodes get into the nodelist.
If my netrom partner (i only have one partner who broadcasts to me at the
minute) goes off line then strange things happen, i am propergating only my
own node callsign pa3gcu-9 i do not have the following callsigns in my
ax25ipd.conf file and do not have any routes set to them, i do however have a
route to w5dav-7.
axip: fm W5DAV-7 to PA3GCU-9 ctl SABM+
axip: fm PA3GCU-9 to W5DAV-7 ctl UA-
axip: fm W5DAV-7 to PA3GCU-9 ctl I00^ pid=CF(NET/ROM) len 238
NET/ROM: YO4GAB-2->PA3GCU-9 ttl 66
protocol family 43, proto 55
axip: fm PA3GCU-9 to W5DAV-7 ctl RR1v
Now YO4GAB-2 shows up in my nodelist with an asterisk and a quality of "0"
Those are the packets i object to, these packets come from other partners as
well, not only w5dav, they can create quite a lot of traffic in some cases
much traffic, takeing into consideration that my node partner has not sent me
a broadcast for hours and sometimes a complete day, thats when these packets
start arriving.
In those packets are hidden nodes, note listen -a does not show the data
content, the LEN is 238, i once used chl-net to get a partial ascii dump of
such a packet, its full of control chars and node callsigns.
Thats why i dont like them, they have a content one cannot "easily see" which
makes me susspious and weary of such packets.
If you want more info i am sure others can verifiy what i have added in this
mail.
-- Regards Richard pshmuhs.futuk@infobaz.com http://people.zeelandnet.nl/pa3gcu - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to vvaktwp.fmevjdmyvs@sofnet.com More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sat Sep 29 2001 - 12:05:46 EEST