[arm-allstar] RX receive only on a permanent transceive link after power fail

Wed Aug 2 15:30:34 EST 2017

Sorry for the long post but I am trying to post all pertinent data for 
my problem.

I have a hub (node 41741) with a couple of other full duplex repeater 
nodes connected to it full time.
One of the full duplex repeaters (node 41859) will transmit audio from 
the hub, the hub is not receiving any audio or key-up status from node 
41859. It is like node 41859 is in receive only mode.  The repeater on 
node 41859 works correctly.
This happened last night after a power failure.

I have Supermon running on the hub.  It is at www.nearlug.org.  It shows 
all connected nodes to be in transceive mode.  It shows that the hub has 
never received anything from node 41859.

The other 2 full duplex repeaters (nodes 41855 and 47857) work ok 
(transcieve mode).

I have not rebooted any nodes yet as I would like to find out why this 
happened.  It has happened in the past a couple of times.

*Here is some of the hub's rpt.conf file.*
/[nodes]//
//; Note, if you are using automatic updates for allstar link nodes,//
//; no allstar link nodes should be defined here. Only place a definition//
//; for your local (within your LAN) nodes, and private (off of allstar//
//; link) nodes here.//
//
//;41741 = radio at 127.0.0.1/41741,NONE//
//1999 = radio at 127.0.0.1/1999,NONE//
//41741 = radio at 96.43.56.40/41741,NONE   ; This hub//
//41855 = radio at 96.43.56.211/41855,NONE  ; 146.835//
//41856 = radio at 96.43.59.15/41856,NONE   ; 444.525//
//41857 = radio at 96.43.56.43/41857,NONE   ; 147.240//
//41858 = radio at 96.43.56.30/41858,NONE   ; 146.955//
//41859 = radio at 96.43.56.30/41859,NONE   ; 443.500//
//45421 = radio at 96.43.56.42/45421,NONE   ; 146.610

/

*Here is some of the repeater node's (41859) rpt.conf file.*
/[nodes]
; Note, if you are using automatic updates for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your local (within your LAN) nodes, and private (off of allstar
; link) nodes here.

41859 = radio at 127.0.0.1/41859,NONE
1999 = radio at 127.0.0.1/1999,NONE
41741 = radio at 96.43.56.40/41741,NONE

/*This is the startup macro to connect 41859 to the hub (41741).*
/startup_macro = *7341741

/
*Tcpdump from the hub shows traffic between it and node 41859.**
*
/[root at k5tw-41741 http]# tcpdump -i eth0 -vv host 96.43.56.30
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
262144 bytes
13:11:30.265911 IP (tos 0x1e,ECT(0), ttl 64, id 55826, offset 0, flags 
[none], proto UDP (17), length 40)
     www.nearlug.org.iax > 96.43.56.30.iax: [bad udp cksum 0x30c2 -> 
0x59ab!] UDP, length 12
13:11:30.266703 IP (tos 0x1e,ECT(0), ttl 64, id 36616, offset 0, flags 
[none], proto UDP (17), length 40)
     96.43.56.30.iax > www.nearlug.org.iax: [udp sum ok] UDP, length 12
13:11:30.267109 IP (tos 0x1e,ECT(0), ttl 64, id 55827, offset 0, flags 
[none], proto UDP (17), length 40)
     www.nearlug.org.iax > 96.43.56.30.iax: [bad udp cksum 0x30c2 -> 
0x58b1!] UDP, length 12

/*Tcpdump from node 41859 shows traffic between it and the hub node 41471.*

/[root at ni5a-41859 asterisk]# tcpdump -i eth0 -vv host 96.43.56.40
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
262144 bytes
13:24:57.840625 IP (tos 0x1e,ECT(0), ttl 64, id 12091, offset 0, flags 
[none], proto UDP (17), length 43)
     ni5a-41859.iax > www.nearlug.org.iax: [bad udp cksum 0x30c5 -> 
0x450c!] UDP, length 15
13:24:57.841352 IP (tos 0x1e,ECT(0), ttl 64, id 31450, offset 0, flags 
[none], proto UDP (17), length 40)
     www.nearlug.org.iax > ni5a-41859.iax: [udp sum ok] UDP, length 12
13:24:58.051310 IP (tos 0x1e,ECT(0), ttl 64, id 12109, offset 0, flags 
[none], proto UDP (17), length 40)
     ni5a-41859.iax > www.nearlug.org.iax: [bad udp cksum 0x30c2 -> 
0x9054!] UDP, length 12
13:24:58.052087 IP (tos 0x1e,ECT(0), ttl 64, id 31469, offset 0, flags 
[none], proto UDP (17), length 40)
     www.nearlug.org.iax > ni5a-41859.iax: [udp sum ok] UDP, length 12
13:24:58.052590 IP (tos 0x1e,ECT(0), ttl 64, id 12110, offset 0, flags 
[none], proto UDP (17), length 40)

/*Core show channels from the hub shows
*/k5tw-41741*CLI> core show channels
Channel              Location             State Application(Data)
DAHDI/pseudo-3157682 s at default:1          Rsrvd   (None)
IAX2/96.43.56.211:45 41741 at radio-secure:1 Up      (None)
DAHDI/pseudo-1205868 s at default:1          Rsrvd   (None)
IAX2/173.218.128.149 41741 at radio-secure:1 Up      (None)
DAHDI/pseudo-2063236 s at default:1          Rsrvd   (None)
IAX2/96.43.56.30:456 41741 at radio-secure:1 Up      (None)
DAHDI/pseudo-9198138 s at default:1          Rsrvd   (None)/
*
Core show channels from node 41859 shows
*/ni5a-41859*CLI> core show channels
Channel              Location             State Application(Data)
DAHDI/pseudo-9258142 s at default:1          Rsrvd   (None)
IAX2/96.43.56.40:456 (None)               Up      Apprpt((Remote Rx))
DAHDI/pseudo-2495954 s at default:1          Rsrvd   (None)

/

In posting the above excerpts from rpt.conf for node 41859, I noticed 
that the ip address is still set to the loopback address.
Could this be a possible cause?  It has been working.

Also, the configuration for node 41859 and the hub node 41741 is a new 
build (3 weeks old) of the latest V1.5.  I know they have been rebooted 
since the initial install with no problems.

The tcpdump data shows traffic between the nodes but it also shows bad 
checksums with the data.
I think the bad checksum may not be related as the same tcpdump between 
the hub and one of the nodes that works also shows bad checksum data.

In looking at CLI> core show channels, it looks like node 41589 is 
actually RX only.  Don't know how that would happen since the startup 
macro does a *7341741 which should be a permanent transceive link.

LaRoy K5TW

//

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus