Today the error is showing when I have listen -at running. Usually its in the terminal of whatever client program I'm using. Below is the output of listen -at and the output of? easyterm
I did adjust the tcp ports to match but port #4 isn't the issue right now. Good catch though.
I sent an email to double check I'm still a sysop, that may be the majority of the issue.
?
$ sudo listen -at
udr0: fm K4SPB to K4SPB-10 ctl SABM+
udr0: fm K4SPB-10 to K4SPB ctl UA-
udr0: fm K4SPB-10 to K4SPB ctl I00^ pid=F0(Text) len 60
0000 ?FATAL: Incomplete/incorrect gateway configuration (N0CALL)..
udr0: fm K4SPB-10 to K4SPB ctl DISC+
udr0: fm K4SPB-10 to K4SPB ctl DISC+
udr0: fm K4SPB to K4SPB-10 ctl DM-
udr0: fm K4SPB to K4SPB-10 ctl SABM+
udr0: fm K4SPB-10 to K4SPB ctl UA-
udr0: fm K4SPB-10 to K4SPB ctl I00^ pid=F0(Text) len 60
0000 ?FATAL: Incomplete/incorrect gateway configuration (N0CALL)..
udr0: fm K4SPB-10 to K4SPB ctl DISC+
udr0: fm K4SPB-10 to K4SPB ctl DISC+
udr0: fm K4SPB to K4SPB-10 ctl DM-
?
?
?
?
?
?1:Fm K4SPB To K4SPB-10 <SABM P>[16:45:12]
?1:Fm K4SPB-10 To K4SPB <DISC P>[16:45:14]
?1:Fm K4SPB-10 To K4SPB <UA F >[16:45:14]
?1:Fm K4SPB-10 To K4SPB <I P R0 S0 pid=F0 Len=48 >[16:45:15]
Trying ec2-52-23-12-135.compute-1.amazonaws.com
?1:Fm K4SPB To K4SPB-10 <DM F >[16:45:15]
?1:Fm K4SPB To K4SPB-10 <SABM P>[16:46:04]
?1:Fm K4SPB-10 To K4SPB <DISC P>[16:46:05]
?1:Fm K4SPB-10 To K4SPB <UA F >[16:46:06]
?1:Fm K4SPB-10 To K4SPB <I P R0 S0 pid=F0 Len=49 >[16:46:07]
Trying ec2-54-161-98-167.compute-1.amazonaws.com
?1:Fm K4SPB To K4SPB-10 <DM F >[16:46:07]
?1:Fm K4SPB To K4SPB-10 <SABM P>[16:49:17]
?1:Fm K4SPB-10 To K4SPB <DISC P>[16:49:19]
?1:Fm K4SPB-10 To K4SPB <UA F >[16:49:19]
?1:Fm K4SPB-10 To K4SPB <I P R0 S0 pid=F0 Len=48 >[16:49:20]
Trying ec2-52-23-12-135.compute-1.amazonaws.com
?1:Fm K4SPB To K4SPB-10 <DM F >[16:49:20]
?1:Fm K4SPB-10 To K4SPB <RR P/F R0 >[16:49:25]
?1:Fm K4SPB To K4SPB-10 <DM F >[16:49:25]
?1:Fm K4SPB-7 To ID <UI pid=F0 Len=0 >[16:51:42]
?
