Date   

Re: winlink client immediately disconnects from server

John Spoonhower
 

Basil,
thanks the problem is fixed. I appreciate your help (again...).
73, John, NX2I
p.s. a few comments below. I have no clue how the change in channels.xml occurred. Line 5 in channels.xml backups (like channels.xml.~2~) have udr1 on line 5.


On Sat, Aug 25, 2018 at 8:26 PM Basil Gunn <basil@...> wrote:

The results you have shown me all look good.  The ax25 device ax1 (udr1)
is sending & receiving packets fine.

Make sure that file: /etc/ax25/channels.xml
I believe you meant /etc/rmsgw/channels.xml
 
has an entry 5 lines from the top like this:

 <channel name="udr1" type="ax25" active="yes">

I'm guessing it will say "udr0" & it should be "udr1"

If you need to change it reboot & run rmsgw_aci.
yes, it was udr0 and I changed it. The output from rmsgw_aci still looks like:
 rmsgw_aci
status for interface ax0 unavailable

/Basil

John Spoonhower <jpspoonhower@...> writes:

> Basil,
> please see below for more responses.
> 73,
> John
>
>
>
> On Sat, Aug 25, 2018 at 5:02 PM Basil Gunn <basil@...> wrote:
>
>>
>> ax.25 is misconfigured for interface udr1
>>
>> Please show the results of
>> ifconfig
>>
>> * RESULTS: *
>
> *$ ifconfig*
> *ax0       Link encap:AMPR AX.25  HWaddr NX2I-11  *
> *          inet addr:44.24.197.66  Bcast:44.255.255.255
> Mask:255.255.255.255*
> *          UP BROADCAST RUNNING  MTU:255  Metric:1*
> *          RX packets:0 errors:0 dropped:0 overruns:0 frame:0*
>           *TX packets:9 errors:0 dropped:0 overruns:0 carrier:0*
> *          collisions:0 txqueuelen:10 *
> *          RX bytes:0 (0.0 B)  TX bytes:276 (276.0 B)*
>
> *ax1       Link encap:AMPR AX.25  HWaddr NX2I-10  *
> *          inet addr:44.24.197.67  Bcast:44.255.255.255
> Mask:255.255.255.255*
> *          UP BROADCAST RUNNING  MTU:255  Metric:1*
> *          RX packets:138 errors:0 dropped:0 overruns:0 fra*me:0
>       *    TX packets:242 errors:0 dropped:0 overruns:0 carrier:0*
> *          collisions:0 txqueuelen:10 *
> *          RX bytes:2850 (2.7 KiB)  TX bytes:9446 (9.2 KiB)*
>
>
>> and
>>
>> ax25-status
>>
> *ax25-status*
> *== failed & loaded but inactive units==*
> *0 loaded units listed.*
> *To show all installed unit files use 'systemctl list-unit-files'.*
>
> *== direwolf ==*
> *  pid: 555*
> *  ver: Dire Wolf version 1.4*
> *== /proc/sys ==*
> *ax25  core  ipv4  ipv6 netfilter  unix*
> *ax0  ax1*
>
> *== ifconfig ax0 ==*
> *ax0       Link encap:AMPR AX.25  HWaddr NX2I-11  *
> *          inet addr:44.24.197.66  Bcast:44.255.255.255
> Mask:255.255.255.255*
> *          UP BROADCAST RUNNING  MTU:255  Metric:1*
> *          RX packets:0 errors:0 dropped:0 overruns:0 frame:0*
> *          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0*
> *          collisions:0 txqueuelen:10 *
> *          RX bytes:0 (0.0 B)  TX bytes:276 (276.0 B)*
>
>
> *== status networkd services ==*
> *enabled*
> *● systemd-networkd-wait-online.service - Wait for Network to be Configured*
> *   Loaded: loaded
> (/lib/systemd/system/systemd-networkd-wait-online.service; enabled)*
> *   Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
> *     Docs: man:systemd-networkd-wait-online.service(8)*
> *  Process: 570 ExecStart=/lib/systemd/systemd-networkd-wait-online
> (code=exited, status=0/SUCCESS)*
> * Main PID: 570 (code=exited, status=0/SUCCESS)*
> *   CGroup: /system.slice/systemd-networkd-wait-online.service*
> *enabled*
> *● systemd-networkd.service - Network Service*
> *   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled)*
> *   Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago*
> *     Docs: man:systemd-networkd.service(8)*
> * Main PID: 551 (systemd-network)*
> *   Status: "Processing requests..."*
> *   CGroup: /system.slice/systemd-networkd.service*
> *           └─551 /lib/systemd/systemd-networkd*
>
> *== status direwolf service ==*
> *enabled*
> *● direwolf.service - Direwolf Daemon*
> *   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled)*
> *   Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago*
> *  Process: 435 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited,
> status=0/SUCCESS)*
> * Main PID: 555 (direwolf)*
> *   CGroup: /system.slice/direwolf.service*
> *           └─555 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p*
>
> *== status ax25 service ==*
> *disabled*
> *● ax25dev.service - AX.25 device*
> *   Loaded: loaded (/etc/systemd/system/ax25dev.service; disabled)*
> *   Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
> *  Process: 723 ExecStartPost=/bin/bash -c /usr/local/sbin/kissparms -p
> udr0 -f no -l 100 -r 32 -s 200 -t 500 (code=exited, status=0/SUCCESS)*
> *  Process: 627 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited,
> status=0/SUCCESS)*
> * Main PID: 627 (code=exited, status=0/SUCCESS)*
> *   CGroup: /system.slice/ax25dev.service*
> *           ├─689 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx*
> *           ├─701 /usr/local/sbin/kissattach /dev/pts/1 udr0 44.24.197.66*
> *           └─703 /usr/local/sbin/kissattach /dev/pts/2 udr1 44.24.197.67*
>
> *== status ax25 path ==*
> *enabled*
> *● ax25dev.path*
> *   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled)*
> *   Active: active (running) since Sat 2018-08-25 11:20:09 EDT; 7h ago*
>
> *== status ax25-mheardd ==*
> *enabled*
> *● ax25-mheardd.service - AX.25 mheard daemon*
> *   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled)*
> *   Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
> * Main PID: 738 (mheardd)*
> *   CGroup: /system.slice/ax25-mheardd.service*
> *           └─738 /usr/local/sbin/mheardd -f -n 30*
>
> *== status ax25d ==*
> *enabled*
> *● ax25d.service - General purpose AX.25 daemon*
> *   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled)*
> *   Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
> * Main PID: 737 (ax25d)*
> *   CGroup: /system.slice/ax25d.service*
> *           └─737 /usr/local/sbin/ax25d -l*
>
> *== netstat ax25 ==*
> *Active AX.25 sockets*
> *Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q*
> **          NX2I-10    ax1     LISTENING    000/000  0       0     *
> **          NX2I-12    ax0     LISTENING    000/000  0       0    *
>
>
>>
>> Check that there is an entry in /etc/ax25/axports for udr1
>>
>
> *yup:*
> * more axports*
> *# /usr/local/etc/ax25/axports*
> *#*
> *# The format of this file is:*
> *#portname callsign speed paclen window description*
> *udr0        NX2I-11         9600    255     2       Direwolf port*
> *udr1        NX2I-10            9600    255     2       Winlink port*




Re: IP Addresses on 44.x.x.x. Was: [udrc] winlink client immediately disconnects from server

Basil Gunn
 

kissattach requires a dummy ip address that is not used and that's what
those 44net addresses are for. Also the 44Net ip addresses are on an RF
interface so there shouldn't be a problem.

John S. is using those dummy addresses for a Winlink gateway only.
If John H. could recommend a better dummy address that be good.

/Basil n7nix

John D Hays - K7VE <@john_hays> writes:

Hi John -

I am the coordinator for 44.24.x.x IP address space in Western Washington.

The addresses you are using are not registered at https://portal.ampr.org -
you may want to go to this site and register addresses that are for your
area (Florida - https://portal.ampr.org/networks.php?a=region&id=198) --
this is the network 44.98.x.x and you have the choice of IPIP tunnels (
https://portal.ampr.org/gateways_index.php), HamWAN (Orlando/Tampa area
http://flscg.org/hamwan/), or VPN (https://groups.io/g/net-44-vpn/wiki/home)
for connection to the rest of AMPRnet.

If you are not connecting to any IP networks using those addresses
44.24.197.x -- it is likely not creating any problems, but you might just
want to have *official* addresses.

Basil is the expert on the configuration you are sorting out, so you are in
good hands. I just observed the addresses and they caught my eye as the
coordinator.



On Sat, Aug 25, 2018 at 3:29 PM, John Spoonhower <jpspoonhower@...>
wrote:

Basil,
please see below for more responses.
73,
John



On Sat, Aug 25, 2018 at 5:02 PM Basil Gunn <@basil860> wrote:


*$ ifconfig*
*ax0 Link encap:AMPR AX.25 HWaddr NX2I-11 *
* inet addr:44.24.197.66 Bcast:44.255.255.255
Mask:255.255.255.255*
* UP BROADCAST RUNNING MTU:255 Metric:1*
* RX packets:0 errors:0 dropped:0 overruns:0 frame:0*
*TX packets:9 errors:0 dropped:0 overruns:0 carrier:0*
* collisions:0 txqueuelen:10 *
* RX bytes:0 (0.0 B) TX bytes:276 (276.0 B)*

*ax1 Link encap:AMPR AX.25 HWaddr NX2I-10 *
* inet addr:44.24.197.67 Bcast:44.255.255.255
Mask:255.255.255.255*
* UP BROADCAST RUNNING MTU:255 Metric:1*
* RX packets:138 errors:0 dropped:0 overruns:0 fra*me:0
* TX packets:242 errors:0 dropped:0 overruns:0 carrier:0*
* collisions:0 txqueuelen:10 *
* RX bytes:2850 (2.7 KiB) TX bytes:9446 (9.2 KiB)*



Re: winlink client immediately disconnects from server

Basil Gunn
 

The results you have shown me all look good. The ax25 device ax1 (udr1)
is sending & receiving packets fine.

Make sure that file: /etc/ax25/channels.xml
has an entry 5 lines from the top like this:

<channel name="udr1" type="ax25" active="yes">

I'm guessing it will say "udr0" & it should be "udr1"

If you need to change it reboot & run rmsgw_aci.
/Basil

John Spoonhower <jpspoonhower@...> writes:

Basil,
please see below for more responses.
73,
John



On Sat, Aug 25, 2018 at 5:02 PM Basil Gunn <@basil860> wrote:


ax.25 is misconfigured for interface udr1

Please show the results of
ifconfig

* RESULTS: *
*$ ifconfig*
*ax0 Link encap:AMPR AX.25 HWaddr NX2I-11 *
* inet addr:44.24.197.66 Bcast:44.255.255.255
Mask:255.255.255.255*
* UP BROADCAST RUNNING MTU:255 Metric:1*
* RX packets:0 errors:0 dropped:0 overruns:0 frame:0*
*TX packets:9 errors:0 dropped:0 overruns:0 carrier:0*
* collisions:0 txqueuelen:10 *
* RX bytes:0 (0.0 B) TX bytes:276 (276.0 B)*

*ax1 Link encap:AMPR AX.25 HWaddr NX2I-10 *
* inet addr:44.24.197.67 Bcast:44.255.255.255
Mask:255.255.255.255*
* UP BROADCAST RUNNING MTU:255 Metric:1*
* RX packets:138 errors:0 dropped:0 overruns:0 fra*me:0
* TX packets:242 errors:0 dropped:0 overruns:0 carrier:0*
* collisions:0 txqueuelen:10 *
* RX bytes:2850 (2.7 KiB) TX bytes:9446 (9.2 KiB)*


and

ax25-status
*ax25-status*
*== failed & loaded but inactive units==*
*0 loaded units listed.*
*To show all installed unit files use 'systemctl list-unit-files'.*

*== direwolf ==*
* pid: 555*
* ver: Dire Wolf version 1.4*
*== /proc/sys ==*
*ax25 core ipv4 ipv6 netfilter unix*
*ax0 ax1*

*== ifconfig ax0 ==*
*ax0 Link encap:AMPR AX.25 HWaddr NX2I-11 *
* inet addr:44.24.197.66 Bcast:44.255.255.255
Mask:255.255.255.255*
* UP BROADCAST RUNNING MTU:255 Metric:1*
* RX packets:0 errors:0 dropped:0 overruns:0 frame:0*
* TX packets:9 errors:0 dropped:0 overruns:0 carrier:0*
* collisions:0 txqueuelen:10 *
* RX bytes:0 (0.0 B) TX bytes:276 (276.0 B)*


*== status networkd services ==*
*enabled*
*● systemd-networkd-wait-online.service - Wait for Network to be Configured*
* Loaded: loaded
(/lib/systemd/system/systemd-networkd-wait-online.service; enabled)*
* Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
* Docs: man:systemd-networkd-wait-online.service(8)*
* Process: 570 ExecStart=/lib/systemd/systemd-networkd-wait-online
(code=exited, status=0/SUCCESS)*
* Main PID: 570 (code=exited, status=0/SUCCESS)*
* CGroup: /system.slice/systemd-networkd-wait-online.service*
*enabled*
*● systemd-networkd.service - Network Service*
* Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled)*
* Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago*
* Docs: man:systemd-networkd.service(8)*
* Main PID: 551 (systemd-network)*
* Status: "Processing requests..."*
* CGroup: /system.slice/systemd-networkd.service*
* └─551 /lib/systemd/systemd-networkd*

*== status direwolf service ==*
*enabled*
*● direwolf.service - Direwolf Daemon*
* Loaded: loaded (/etc/systemd/system/direwolf.service; enabled)*
* Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago*
* Process: 435 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited,
status=0/SUCCESS)*
* Main PID: 555 (direwolf)*
* CGroup: /system.slice/direwolf.service*
* └─555 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p*

*== status ax25 service ==*
*disabled*
*● ax25dev.service - AX.25 device*
* Loaded: loaded (/etc/systemd/system/ax25dev.service; disabled)*
* Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
* Process: 723 ExecStartPost=/bin/bash -c /usr/local/sbin/kissparms -p
udr0 -f no -l 100 -r 32 -s 200 -t 500 (code=exited, status=0/SUCCESS)*
* Process: 627 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited,
status=0/SUCCESS)*
* Main PID: 627 (code=exited, status=0/SUCCESS)*
* CGroup: /system.slice/ax25dev.service*
* ├─689 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx*
* ├─701 /usr/local/sbin/kissattach /dev/pts/1 udr0 44.24.197.66*
* └─703 /usr/local/sbin/kissattach /dev/pts/2 udr1 44.24.197.67*

*== status ax25 path ==*
*enabled*
*● ax25dev.path*
* Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled)*
* Active: active (running) since Sat 2018-08-25 11:20:09 EDT; 7h ago*

*== status ax25-mheardd ==*
*enabled*
*● ax25-mheardd.service - AX.25 mheard daemon*
* Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled)*
* Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
* Main PID: 738 (mheardd)*
* CGroup: /system.slice/ax25-mheardd.service*
* └─738 /usr/local/sbin/mheardd -f -n 30*

*== status ax25d ==*
*enabled*
*● ax25d.service - General purpose AX.25 daemon*
* Loaded: loaded (/etc/systemd/system/ax25d.service; enabled)*
* Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago*
* Main PID: 737 (ax25d)*
* CGroup: /system.slice/ax25d.service*
* └─737 /usr/local/sbin/ax25d -l*

*== netstat ax25 ==*
*Active AX.25 sockets*
*Dest Source Device State Vr/Vs Send-Q Recv-Q*
** NX2I-10 ax1 LISTENING 000/000 0 0 *
** NX2I-12 ax0 LISTENING 000/000 0 0 *



Check that there is an entry in /etc/ax25/axports for udr1
*yup:*
* more axports*
*# /usr/local/etc/ax25/axports*
*#*
*# The format of this file is:*
*#portname callsign speed paclen window description*
*udr0 NX2I-11 9600 255 2 Direwolf port*
*udr1 NX2I-10 9600 255 2 Winlink port*


IP Addresses on 44.x.x.x. Was: [udrc] winlink client immediately disconnects from server

 

Hi John - 

I am the coordinator for 44.24.x.x IP address space in Western Washington.

The addresses you are using are not registered at https://portal.ampr.org - you may want to go to this site and register addresses that are for your area (Florida - https://portal.ampr.org/networks.php?a=region&id=198)  -- this is the network 44.98.x.x and you have the choice of IPIP tunnels (https://portal.ampr.org/gateways_index.php), HamWAN (Orlando/Tampa area http://flscg.org/hamwan/), or VPN (https://groups.io/g/net-44-vpn/wiki/home) for connection to the rest of AMPRnet.

If you are not connecting to any IP networks using those addresses 44.24.197.x -- it is likely not creating any problems, but you might just want to have *official* addresses.

Basil is the expert on the configuration you are sorting out, so you are in good hands.  I just observed the addresses and they caught my eye as the coordinator.



On Sat, Aug 25, 2018 at 3:29 PM, John Spoonhower <jpspoonhower@...> wrote:
Basil,
please see below for more responses.
73,
John



On Sat, Aug 25, 2018 at 5:02 PM Basil Gunn <basil@...> wrote:

$ ifconfig
ax0       Link encap:AMPR AX.25  HWaddr NX2I-11  
          inet addr:44.24.197.66  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:0 (0.0 B)  TX bytes:276 (276.0 B)

ax1       Link encap:AMPR AX.25  HWaddr NX2I-10  
          inet addr:44.24.197.67  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:138 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:2850 (2.7 KiB)  TX bytes:9446 (9.2 KiB)



--


John D. Hays
Director

  


Re: winlink client immediately disconnects from server

John Spoonhower
 

Basil,
please see below for more responses.
73,
John



On Sat, Aug 25, 2018 at 5:02 PM Basil Gunn <basil@...> wrote:

ax.25 is misconfigured for interface udr1

Please show the results of
ifconfig
RESULTS: 
$ ifconfig
ax0       Link encap:AMPR AX.25  HWaddr NX2I-11  
          inet addr:44.24.197.66  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:0 (0.0 B)  TX bytes:276 (276.0 B)

ax1       Link encap:AMPR AX.25  HWaddr NX2I-10  
          inet addr:44.24.197.67  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:138 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:2850 (2.7 KiB)  TX bytes:9446 (9.2 KiB)

eth0      Link encap:Ethernet  HWaddr b8:27:eb:95:38:66  
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::a48:5d96:63fc:d728/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:64914 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57029 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5161172 (4.9 MiB)  TX bytes:23216826 (22.1 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:
 
Virtru protection is ON
Virtru protection is OFF
 
Disable Forwarding
Expires in: minutes hours days weeks months years
Saturday, August 25, 2018 6:24 PM
PDF Watermarking
 
 
Virtru protection is OFF
 
 
Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:294 errors:0 dropped:0 overruns:0 frame:0
          TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:28575 (27.9 KiB)  TX bytes:28575 (27.9 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:c0:6d:33  
          inet6 addr: fe80::45c9:aab:b7dc:3749/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:5807 errors:0 dropped:187 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1956980 (1.8 MiB)  TX bytes:0 (0.0 B)

 
and

ax25-status
ax25-status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

== direwolf ==
  pid: 555
  ver: Dire Wolf version 1.4
== /proc/sys ==
ax25  core  ipv4  ipv6 netfilter  unix
ax0  ax1

== ifconfig ax0 ==
ax0       Link encap:AMPR AX.25  HWaddr NX2I-11  
          inet addr:44.24.197.66  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:0 (0.0 B)  TX bytes:276 (276.0 B)


== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled)
   Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago
     Docs: man:systemd-networkd-wait-online.service(8)
  Process: 570 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
 Main PID: 570 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-networkd-wait-online.service
enabled
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled)
   Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 551 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─551 /lib/systemd/systemd-networkd

== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled)
   Active: active (running) since Sat 2018-08-25 11:20:10 EDT; 7h ago
  Process: 435 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
 Main PID: 555 (direwolf)
   CGroup: /system.slice/direwolf.service
           └─555 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p

== status ax25 service ==
disabled
● ax25dev.service - AX.25 device
   Loaded: loaded (/etc/systemd/system/ax25dev.service; disabled)
   Active: active (exited) since Sat 2018-08-25 11:20:11 EDT; 7h ago
  Process: 723 ExecStartPost=/bin/bash -c /usr/local/sbin/kissparms -p udr0 -f no -l 100 -r 32 -s 200 -t 500 (code=exited, status=0/SUCCESS)
  Process: 627 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited, status=0/SUCCESS)
 Main PID: 627 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/ax25dev.service
           ├─689 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
           ├─701 /usr/local/sbin/kissattach /dev/pts/1 udr0 44.24.197.66
           └─703 /usr/local/sbin/kissattach /dev/pts/2 udr1 44.24.197.67

== status ax25 path ==
enabled
● ax25dev.path
   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled)
   Active: active (running) since Sat 2018-08-25 11:20:09 EDT; 7h ago

== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled)
   Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago
 Main PID: 738 (mheardd)
   CGroup: /system.slice/ax25-mheardd.service
           └─738 /usr/local/sbin/mheardd -f -n 30

== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled)
   Active: active (running) since Sat 2018-08-25 11:20:11 EDT; 7h ago
 Main PID: 737 (ax25d)
   CGroup: /system.slice/ax25d.service
           └─737 /usr/local/sbin/ax25d -l

== netstat ax25 ==
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          NX2I-10    ax1     LISTENING    000/000  0       0     
*          NX2I-12    ax0     LISTENING    000/000  0       0    
 

Check that there is an entry in /etc/ax25/axports for udr1

yup:
 more axports
# /usr/local/etc/ax25/axports
#
# The format of this file is:
#portname callsign speed paclen window description
udr0        NX2I-11         9600    255     2       Direwolf port
udr1        NX2I-10            9600    255     2       Winlink port


Until you can run rmsgw_aci without any errors your gateway will not
work. Also once rmsgw_aci runs properly you will appear in Winlink RMS
Gateway list & on the Winlink packet Gateway map.

/Basil

John Spoonhower <jpspoonhower@...> writes:

> Hi Basil,
> please see below for responses. 73, John
>
>
> On Sat, Aug 25, 2018 at 1:29 PM Basil Gunn <basil@...> wrote:
>
>>
>> After your RMS Gateway displays your banner:
>> "NX2I-10 Linux RMS Gateway 2.4, The Villages, FL"
>> you should see a "<Connected" message.
>>
>> Since you don't, it most likely means you have a CMS login problem (wrong
>> password) or you have an Internet connection problem.
>>
>> In your /etc/rmsgw/gateway.conf file set
>> LOGMASK=DEBUG
>> and check your /var/log/syslog file after trying to connect.
>>
>
> *Here's what I see:*
>
>
>
>> *Aug 25 15:10:40 compass-winlinkrms ax25d[2132]: AX.25 NX2I (udr1) rmsgw*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: getopt saw '-P'*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]:      optarg = udr1*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfilearg = (null)*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfile =
>>> /etc/rmsgw/gateway.conf*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using config file
>>> /etc/rmsgw/gateway.conf*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using version file
>>> /etc/rmsgw/.version_info*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: #012NX2I-10 - Linux RMS
>>> Gateway 2.4.0 May  2 2018 (EL88xv)*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: ERROR: no channel data
>>> for port udr1, call NX2I-10*
>>
>> *Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: FATAL ERROR: session
>>> startup not possible*
>>
>> Since I am not seeing NX2I-10 in the "Winlink RMS List" I am assuming your
>> RMS Gateway isn't quite configured properly yet.
>>
>> What do you see when you run:
>> rmsgw_aci
>>
> *I get this:*
>
> * pi@compass-winlinkrms:~ $ sudo rmsgw_aci*
> *status for interface ax0 unavailable*




Re: winlink client immediately disconnects from server

Basil Gunn
 

ax.25 is misconfigured for interface udr1

Please show the results of
ifconfig

and

ax25-status

Check that there is an entry in /etc/ax25/axports for udr1

Until you can run rmsgw_aci without any errors your gateway will not
work. Also once rmsgw_aci runs properly you will appear in Winlink RMS
Gateway list & on the Winlink packet Gateway map.

/Basil

John Spoonhower <jpspoonhower@...> writes:

Hi Basil,
please see below for responses. 73, John


On Sat, Aug 25, 2018 at 1:29 PM Basil Gunn <@basil860> wrote:


After your RMS Gateway displays your banner:
"NX2I-10 Linux RMS Gateway 2.4, The Villages, FL"
you should see a "<Connected" message.

Since you don't, it most likely means you have a CMS login problem (wrong
password) or you have an Internet connection problem.

In your /etc/rmsgw/gateway.conf file set
LOGMASK=DEBUG
and check your /var/log/syslog file after trying to connect.
*Here's what I see:*



*Aug 25 15:10:40 compass-winlinkrms ax25d[2132]: AX.25 NX2I (udr1) rmsgw*

*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: getopt saw '-P'*

*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: optarg = udr1*

*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfilearg = (null)*

*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfile =
/etc/rmsgw/gateway.conf*
*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using config file
/etc/rmsgw/gateway.conf*
*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using version file
/etc/rmsgw/.version_info*
*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: #012NX2I-10 - Linux RMS
Gateway 2.4.0 May 2 2018 (EL88xv)*
*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: ERROR: no channel data
for port udr1, call NX2I-10*
*Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: FATAL ERROR: session
startup not possible*
Since I am not seeing NX2I-10 in the "Winlink RMS List" I am assuming your
RMS Gateway isn't quite configured properly yet.

What do you see when you run:
rmsgw_aci
*I get this:*

* pi@compass-winlinkrms:~ $ sudo rmsgw_aci*
*status for interface ax0 unavailable*


Re: winlink client immediately disconnects from server

John Spoonhower
 

Hi Basil,
please see below for responses. 73, John


On Sat, Aug 25, 2018 at 1:29 PM Basil Gunn <basil@...> wrote:

After your RMS Gateway displays your banner:
"NX2I-10 Linux RMS Gateway 2.4, The Villages, FL"
you should see a "<Connected" message.

Since you don't, it most likely means you have a CMS login problem (wrong
password) or you have an Internet connection problem.

In your /etc/rmsgw/gateway.conf file set
LOGMASK=DEBUG
and check your /var/log/syslog file after trying to connect.

Here's what I see:

 
Aug 25 15:10:40 compass-winlinkrms ax25d[2132]: AX.25 NX2I (udr1) rmsgw
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: getopt saw '-P'
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]:      optarg = udr1
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfilearg = (null)
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: configfile = /etc/rmsgw/gateway.conf
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using config file /etc/rmsgw/gateway.conf
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: using version file /etc/rmsgw/.version_info
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: #012NX2I-10 - Linux RMS Gateway 2.4.0 May  2 2018 (EL88xv)
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: ERROR: no channel data for port udr1, call NX2I-10
Aug 25 15:10:40 compass-winlinkrms rmsgw[2132]: FATAL ERROR: session startup not possible
Aug 25 15:10:46 compass-winlinkrms ax25d[2133]: AX.25 NX2I (udr1) rmsgw
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: getopt saw '-P'
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]:      optarg = udr1
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: configfilearg = (null)
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: configfile = /etc/rmsgw/gateway.conf
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: using config file /etc/rmsgw/gateway.conf
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: using version file /etc/rmsgw/.version_info
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: #012NX2I-10 - Linux RMS Gateway 2.4.0 May  2 2018 (EL88xv)
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: ERROR: no channel data for port udr1, call NX2I-10
Aug 25 15:10:46 compass-winlinkrms rmsgw[2133]: FATAL ERROR: session startup not possible

Since I am not seeing NX2I-10 in the "Winlink RMS List" I am assuming your
RMS Gateway isn't quite configured properly yet.

What do you see when you run:
rmsgw_aci
I get this:
 pi@compass-winlinkrms:~ $ sudo rmsgw_aci
status for interface ax0 unavailable


/Basil

John Spoonhower <jpspoonhower@...> writes:

> I am having an ongoing problem with the Winlink RMS. Multiple users
> report getting immediate disconnects. The server worked well for
> months, but has not survived a power loss/reboot cycle. I have checked
> a few configuration items but I am currently at a loss regarding what
> to try next. The direwolf log is shown below; to me, it's not too
> informative.  73, John, NX2I
>
> Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1.6] NX2I>NX2I-10:(SABM cmd, p=1)
> Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(UA res, f=1)
> Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)<0x0a>NX2I-10 - Linux RMS Gateway 2.4.0 May 2 2018 (EL88xv)<0x0a><0x0a>
> Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0)NX2I-10 Linux RMS Gateway 2.4, The Villages, FL<0x0a>
> Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(DISC cmd, p=1)




Re: winlink client immediately disconnects from server

Basil Gunn
 

After your RMS Gateway displays your banner:
"NX2I-10 Linux RMS Gateway 2.4, The Villages, FL"
you should see a "<Connected" message.

Since you don't, it most likely means you have a CMS login problem (wrong
password) or you have an Internet connection problem.

In your /etc/rmsgw/gateway.conf file set
LOGMASK=DEBUG
and check your /var/log/syslog file after trying to connect.

Since I am not seeing NX2I-10 in the "Winlink RMS List" I am assuming your
RMS Gateway isn't quite configured properly yet.

What do you see when you run:
rmsgw_aci

/Basil

John Spoonhower <jpspoonhower@...> writes:

I am having an ongoing problem with the Winlink RMS. Multiple users
report getting immediate disconnects. The server worked well for
months, but has not survived a power loss/reboot cycle. I have checked
a few configuration items but I am currently at a loss regarding what
to try next. The direwolf log is shown below; to me, it's not too
informative. 73, John, NX2I

Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1.6] NX2I>NX2I-10:(SABM cmd, p=1)
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(UA res, f=1)
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)<0x0a>NX2I-10 - Linux RMS Gateway 2.4.0 May 2 2018 (EL88xv)<0x0a><0x0a>
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0)NX2I-10 Linux RMS Gateway 2.4, The Villages, FL<0x0a>
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(DISC cmd, p=1)


winlink client immediately disconnects from server

John Spoonhower
 

I am having an ongoing problem with the Winlink RMS. Multiple users report getting immediate disconnects. The server worked well for months, ut has not survived a power loss/reboot cycle. I have checked a few configuration items but I am currently at a loss regarding what to try next. The direwolf log is shown below; to me, it's not too informative.
73, John, NX2I

Aug 25 12:49:30 compass-winlinkrms direwolf[555]: NX2I audio level = 58(26/13)   [NONE]   ____|||||
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1.6] NX2I>NX2I-10:(SABM cmd, p=1)
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(UA res, f=1)
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)<0x0a>NX2I-10 - Linux RMS Gateway 2.4.0 May  2 2018 (EL88xv)<0x0a><0x0a>
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0)NX2I-10 Linux RMS Gateway 2.4, The Villages, FL<0x0a>
Aug 25 12:49:30 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(DISC cmd, p=1)
Aug 25 12:49:33 compass-winlinkrms direwolf[555]: NX2I audio level = 57(26/13)   [NONE]   __|||||||
Aug 25 12:49:33 compass-winlinkrms direwolf[555]: [1.5] NX2I>NX2I-10:(RR res, n(r)=2, f=1)
Aug 25 12:49:34 compass-winlinkrms direwolf[555]: NX2I audio level = 58(26/13)   [NONE]   __|||||||
Aug 25 12:49:34 compass-winlinkrms direwolf[555]: [1.5] NX2I>NX2I-10:(UA res, f=1)
Aug 25 12:49:35 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(DISC cmd, p=1)
Aug 25 12:49:35 compass-winlinkrms direwolf[555]: [1L] NX2I-10>NX2I:(DM res, f=1)
 


Re: direwolf packet monitor

Stuart Longland VK4MSL
 

On 25/08/18 01:00, Basil Gunn wrote:
tail -f /var/log/direwolf/direwolf.log

Since this file is automatically rotated so as not to get too large you
will have to restart the tail command once a day.
If you want to avoid having to re-start tail, then use:

tail -F /var/log/direwolf/direwolf.log

This is a GNU extension, so not portable with BSD's `tail`, but `-F`
means to follow the file name rather than the inode, so when it gets
replaced with another file, `tail` will close the old file and open the
new one before resuming the tail.
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.


Re: direwolf packet monitor

Basil Gunn
 

thanks for your note. The tail command you suggest works well for me.
According to the direwolf output the audio level from my FT-857 can/should
be increased a little. Which of the UDRC-II audio controls should be
adjusted using alsamixer ( or the set-udrc-din6) script?
If you are talking about output ie. transmit deviation then:

LO Drive Gain is the analog control (use this first)
PCM is the digital control

If you are talking about input:

ADC level is the digital control

You may need to identify the script that sets these values to maintain
them across RPi boot up.

Also note that depending on which connector you are using will determine
which audio channel you should adjust.

HD15 is on the right audio channel, Direwolf chan 0
mDin6 is on the left audio channel, Direwolf chan 1

If you are only using one connector then it is safe to adjust both audio
channels together.

/Basil n7nix


Re: direwolf packet monitor

John Spoonhower
 

Hi Basil,
thanks for your note. The tail command you suggest works well for me.
According to the direwolf output the audio level from my FT-857 can/should be increased a little. Which of the UDRC-II audio controls should be adjusted using alsamixer ( or the set-udrc-din6) script?

73, John, NX2I


On Fri, Aug 24, 2018 at 11:00 AM Basil Gunn <basil@...> wrote:

> Is there a way to have direwolf (running on a Raspberry Pi with the
> UDRC-II) open a window and show the packet traffic. I am running a
> Winlink RMS and wish to monitor the strength of the received
> packets. I see the traffic using "listen -cart", but there's
> additional information available in the direwolf console.

If you used the N7NIX scripts to install direwolf then the rotated log file
exists in /var/log/direwolf/direwolf.log

To continuously watch that file execute this:

tail -f /var/log/direwolf/direwolf.log

Since this file is automatically rotated so as not to get too large you
will have to restart the tail command once a day.

Otherwise just start direwolf manually in a console window.

/Basil n7nix




Re: direwolf packet monitor

Basil Gunn
 

Is there a way to have direwolf (running on a Raspberry Pi with the
UDRC-II) open a window and show the packet traffic. I am running a
Winlink RMS and wish to monitor the strength of the received
packets. I see the traffic using "listen -cart", but there's
additional information available in the direwolf console.
If you used the N7NIX scripts to install direwolf then the rotated log file
exists in /var/log/direwolf/direwolf.log

To continuously watch that file execute this:

tail -f /var/log/direwolf/direwolf.log

Since this file is automatically rotated so as not to get too large you
will have to restart the tail command once a day.

Otherwise just start direwolf manually in a console window.

/Basil n7nix


direwolf packet monitor

John Spoonhower
 

Is there a way to have direwolf (running on a Raspberry Pi with the UDRC-II) open a window and show the packet traffic. I am running a Winlink RMS and wish to monitor the strength of the received packets. I see the traffic using "listen -cart", but there's additional information available in the direwolf console.
Thanks and 73,
John, NX2I


Re: Pi 3b to 3b+?

Art - KC7SDA
 

well... i tried to install the udrc-dkms module and got this:
DKMS: install completed.
Processing triggers for man-db (2.7.6.1-2) ...
Setting up linux-kbuild-3.6 (3.6-1~experimental.1+rpi2+b2) ...
Setting up udrc-support (1.0) ...
Setting up linux-headers-3.6-trunk-rpi (3.6.9-1~experimental.1+rpi7) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
however I rebooted and it now appears to work... i guess... i'm still experimenting but changing the version manually apparently did the trick!

Art


Re: Pi 3b to 3b+?

Art - KC7SDA
 

Ok, so that worked, my wifi is back now....

HOWEVER... new(ish) problem: the udrc isn't recognized as a sound card, I'm going to play around with it for a bit... i think that the driver might have gotten uninstalled or left behind during the upgrade.

for the record here is the output from running ./sysver.sh:

----- /proc/version
Linux version 4.14.62-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1134 SMP Tue Aug 14 17:10:10 BST 2018
----- /etc/*version
9.4
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
----- lsb_release
No LSB modules are available.
Distributor ID:    Raspbian
Description:    Raspbian GNU/Linux 9.4 (stretch)
Release:    9.4
Codename:    stretch
---- systemd
   Static hostname: KC7SDA
         Icon name: computer
        Machine ID: (you guys don't need to see that)
           Boot ID: (you guys don't need to see that)
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.14.62-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4


Re: Pi 3b to 3b+?

Art - KC7SDA
 

this is my orginal install I did a long time ago, I've been patching and updating it as I'm only one of a small few in my area really knowlegable in linux and have the time to go searching for answers and work-arounds for issues... I'm also developing a script for my group that updates and patches any issues we find or crop up and allows the members to build the FLDIGI suite from the source whenever a new one comes out.


Re: Pi 3b to 3b+?

Art - KC7SDA
 

I'll give those a try, i figured i had to increment the distro at some point but usually my xubuntu rig would do it for me... maybe future feature for compass?


Re: Pi 3b to 3b+?

Annaliese McDermond
 

You are on the wrong distro on both Compass and Rasbian. These are very rough instructions, but should work okay.

1) In /etc/apt/sources.list.d/raspi.list, change the word “jessie” to “stretch” wherever you see it.
2) In /etc/apt/sources.list, change the word “jessie” to “stretch” wherever you see it.
3) In /etc/apt/sources.list.d/compass.list change the word “alder” to “cedar”
4) Remove the file /etc/apt/preferences.d/compass
5) Execute the command “apt-get update”
6) Execute the command “apt-get dist-upgrade”

This should update your older distro to the newest Stretch based image that will have the proper firmware to boot a Raspberry Pi 3B+. Note that I have *not* tested this and that this procedure is from memory.

--
Annaliese McDermond (NH6Z)
Xenotropic Systems
mcdermj@...


Re: Pi 3b to 3b+?

Bernard f6bvp / ai7bg
 

Did you download and install Compas Linux ?
It includes now an automatic update of UDRC driver that works great with Direwolf after apt-get upgrade RPi-update that are now accepted and doing fine.

73 de Bernard f6bvp

Envoyé de mon iPhone

Le 19 août 2018 à 19:32, Art - KC7SDA <nouse4anick@...> a écrit :

well i confirmed that its not a defective pi....just did a new image of raspbian and it works.... so I'll do a bit more research