From: Gary E. Kohtala (vlwhrc.befsw@hal-pc.org)
Date: Sat Sep 29 2001 - 21:03:50 EEST
Hello everyone,
Yes, I am seeing the same things here on my system. I am presently
using TNOS (linux version). I am working towards running the native
linux AX25 stuff and hope to be able to change my AXIP setup over
to AX25IPD and Linuxnode. There is a considerable learning curve.
I am very close but still have issues to overcome. I believe that YO4GAB
is also running TNOS as well.
I get very strange connect requests from my AXIP links as described
previously. What I thought is that someone was running one of those
network mapper programs again, possibly the W0RLI Netwalker
which has caused networks to crash and burn every time it is let loose
in the Pacific Northwest. My reject file of butchered callsigns and
aliases grows by day. I get connects on my TNOS box from such
things as X0IST, G5BDU5, TE0ST, G1KZH0-13, R9DIP0, etc.
There are dozens of them. Butchered callsigns and aliases. When
they connect to my TNOS, nothing happens. They just open a
socket and waste resources. Doing a look in trace mode and I
see legitimate netrom traffic in addition to the protocol family 43
stuff described by many. I don't like it but don't see any way to
get rid of it until we figure out what is going on. I don't think it is
a problem with LinuxNode. I think it is someone running some
other type of program that may be causing this... That's only an opinion,
however. If you figure out what is causing this and how to stop
it please let me know.
Thank you.
73,
Gary, W7NTF
--Tacoma, WA Linux/TNOS TCPIP Gateway: 44.24.115.8 - 9600 baud on 145.09 Linux DXNet DX Cluster Node: 207.207.72.5 9000 Linux Apache Personal Webserver: http://w7ntf.dhs.org Linux FBB BBS: 207.207.72.5 6300
--
Cees Tool wrote:
> Hi Richard/Tomi & others, > > Richard wrote : > > > 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. > > > > Yes I can verify this. And it is not only happening with AXIP internet > links, but I see rubbish like this also on our radio links. > > Do you know what software is used by YO4GAB-2 ?? > > Here, we have seen some strange-frames passing our nodes and also > connect-requests to our nodes. After debugging, those frames seem to be > defective netrom nodes-broadcast frames. We have seen them originating from > TNOS nodes. (but maybe other sofware is also involved) Such a > broken-node-broadcast frame have a "sender" of the originating node. The > netrom content of frame itself is sent to the node which would be the first > node in the nodes-broadcast-frame and his alias is in place of the normal > TTL, ID-bytes and opcode. When you look at the frames, the alias can still > be recognized, however it changes every hop, because one byte is in place of > the TTL. > > If your node is "lucky" to be the top-node in a frame of nodes-broadcast, > then you will receive also connects of very exotic (non existing calls) on > your netrom-appication if the bytes of the 'alias' represent a > 'connect-request'. Otherwise you may receive invalid netrom frames. I don't > know why this is happening yet, but I hope it has the attention of writers > of the software from where these frames seem to originate. > > The full description of what we have observed some months ago is on my > homepage : > http://www.qsl.net/pa3aes/pub/broken-netrom.txt > > 73, > Cees - PA3AES > > - > To unsubscribe from this list: send the line "unsubscribe linux-hams" in > the body of a message to mxk@mail.dy.fi > More majordomo info at http://vger.kernel.org/majordomo-info.html
- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to terhi.victor@logonet.com More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sat Sep 29 2001 - 21:23:02 EEST