All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: "linux-hams@vger.kernel.org" <linux-hams@vger.kernel.org>
Subject: Re: UBUNTO 12.04 VScom TC800  Serial Kissattach ax??- port configuring corruption HELP Required please
Date: Sun, 06 Apr 2014 11:51:21 -0700	[thread overview]
Message-ID: <5341A229.8010902@trinnet.net> (raw)
In-Reply-To: <0AC34FBF7531404B98449A9318023E3B011B294F@EXMBX16.thus.corp>


Hello Paul,


> test 3 FAILED  I was able to connect out via the three radio interfaces
> then found ax1 had later gone AWOL.  Extracted all that I can find related toe ax0 ax1 ax2 in the
> messages log

So are you saying that ax0, ax1, and ax2 all looked ok and you were able 
to make outgoing connections on each of them but after a period of me, 
ax1 disappeared?  Do you know when?  Maybe it disappeared after you
disconnected from the ax1 link?   This is a key detail we need to know.

> ax0 u433 ttyS8
> ax1 u439 ttyS5
> ax2 v70  ttyS10

What are these "u433, u439, and v70" terms?  Are those the device names 
in /etc/ax25/axports?


> confirm
> connect out via radio on port ax0 u433
> connect out via radio on port ax1 u439
> connect our via radio on port ax2 v70

What program are you using to make these outgoing calls?  "axcall" or 
"call"?  Maybe something else?


What other packet software are you running during these simple tests? 
Any netrom, node, ax25d, ax25ipd, BBS, or other software?  Below it 
shows you might be running the legacy NODE program.  Yes?


> 15:51  u439 has gone AWOl
> ax0       Link encap:AMPR AX.25  HWaddr GB7CIP-8
>            inet addr:44.131.244.1  Bcast:44.131.244.255  Mask:255.0.0.0
>            UP BROADCAST RUNNING  MTU:256  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:10
>            RX bytes:0 (0.0 B)  TX bytes:603 (603.0 B)
>
> ax1       Link encap:AMPR AX.25  HWaddr                           AWOL <<<<<<<<<<<<<<<<<<<<<<
>            BROADCAST MULTICAST  MTU:236  Metric:1          NOTE MTU as changed
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:10
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> ax2       Link encap:AMPR AX.25  HWaddr GB7CIP-4
>            inet addr:44.131.244.1  Bcast:44.131.244.255  Mask:255.0.0.0
>            UP BROADCAST RUNNING  MTU:256  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:10
>            RX bytes:0 (0.0 B)  TX bytes:250 (250.0 B)


> gone through log again after error to pick up anything related to ax0 ax1 ax2 after error noted
> Apr  6 15:38:52 gb7cip kernel: [  394.742748] mkiss: ax0: crc mode is auto.
> Apr  6 15:38:52 gb7cip kernel: [  394.747173] IPv6: ADDRCONF(NETDEV_CHANGE): ax0: link becomes ready
> Apr  6 15:38:56 gb7cip kernel: [  398.758298] mkiss: ax1: crc mode is auto.
> Apr  6 15:38:56 gb7cip kernel: [  398.762874] IPv6: ADDRCONF(NETDEV_CHANGE): ax1: link becomes ready
> Apr  6 15:39:00 gb7cip kernel: [  402.773601] mkiss: ax2: crc mode is auto.
> Apr  6 15:39:00 gb7cip kernel: [  402.777423] IPv6: ADDRCONF(NETDEV_CHANGE): ax2: link becomes ready
> Apr  6 15:39:31 gb7cip kernel: [  434.063357] IPv4 over IPv4 tunneling driver
> Apr  6 15:39:58 gb7cip kernel: [  460.932642] mkiss: ax2: Trying crc-smack
> Apr  6 15:39:58 gb7cip kernel: [  460.932947] mkiss: ax1: Trying crc-smack
> Apr  6 15:39:58 gb7cip kernel: [  460.934640] mkiss: ax4: Trying crc-smack
> Apr  6 15:39:58 gb7cip kernel: [  460.939735] mkiss: ax0: Trying crc-smack

Above it shows you're bringing up ax4.  Where is ax3?  As mentioned 
above, we need to know WHEN ax1 disappears in relation to bringing up or 
using these other interfaces.  I'm suspecting you have a conflicting config.


> Apr  6 15:46:17 gb7cip node[3550]: g4apl @ 44.131.244.1 logged out: Bye
> Apr  6 15:47:41 gb7cip kernel: [  923.663996] mkiss: ax1: crc mode is auto.
> Apr  6 15:53:43 gb7cip node[3633]: g4apl @ 44.131.244.1 logged in

It seems this remote station, G4APL is coming *into* your station and 
then maybe after that things break?  How is this remote station coming 
in.. via AX.25?  via Netrom?  Via IP?



>
> 15:52 AX1 has gone AWOL
> c u439 g4apl-8
> GB7CR:CRNODE CRCHAT:GB7CIP-5 Invalid port

Is this coming from your node program?  How are you accessing the node 
interface?  Are you telnet'ing into localhost on a specific port?  If 
that is the classic LinNode software then I don't understand the prompt. 
  Your machine is GB7CIP but this prompt is showing you're currently 
coming from "GB7CR:CRNODE"


Anyway, there is another thread going on the Linux-hams list on Vger on 
how the LinNode software is pretty old.  Seems that thread mentions a 
known "looping" bug which I think should should be fixed but I don't 
have any details on that.  Regardles, I too would recommend running 
UroNode instead of the LinNode software:

     ftp://ftp.n1uro.net/packet/uronode-2.1.tar.gz

--David

  reply	other threads:[~2014-04-06 18:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08  4:34 Multicast AX.25? Stuart Longland
2014-03-08  9:21 ` Stuart Longland
2014-03-27 13:01   ` netromr.c path quality calc bug ax25tools-1.0.2/netrom Paul Lewis
     [not found]     ` <14505098c38.27e7.5a0dbb80754033f6c6eb17b69a6b1aac@tlen.pl>
2014-03-27 19:46       ` sp2lob@tlen
2014-04-03 10:55         ` AX25IPD /tmp/unix98 invalid export Variable AX25: Paul Lewis
2014-04-05  3:30           ` Stuart Longland
2014-04-05  5:27             ` Marius Petrescu
2014-04-05  7:44               ` Paul Lewis
2014-04-04 15:36         ` UBUNTO 12.04 VScom TC800 Serial Kissattach ax??- port configuring corruption HELP Required please Paul Lewis
2014-04-05 20:49           ` David Ranch
2014-04-05 21:09             ` Paul Lewis
2014-04-06 11:22             ` Paul Lewis
2014-04-06 13:18             ` Paul Lewis
2014-04-06 14:19             ` Paul Lewis
2014-04-06 15:17             ` Paul Lewis
2014-04-06 18:51               ` David Ranch [this message]
2014-04-06 19:42                 ` Paul Lewis
2014-04-08 14:51                 ` Paul Lewis
2014-06-01  9:48                 ` Paul Lewis
2014-06-01 16:04                   ` David Ranch
2014-06-01 19:20                     ` Paul Lewis
2014-03-28  0:36     ` netromr.c path quality calc bug ax25tools-1.0.2/netrom Brian
2014-03-08  9:29 ` [PATCH] ax25ipd: Add support for multicast AX/UDPv4 Stuart Longland
2014-03-08 16:44 ` Multicast AX.25? David Ranch
2014-03-09 21:21   ` Stuart Longland VK4MSL
2014-03-23  7:40 ` Revised AX.25 multicast patch Stuart Longland
2014-03-23  7:40   ` [PATCH] ax25ipd: Add support for multicast AX/UDPv4 Stuart Longland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5341A229.8010902@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.