Re: KISSPORT #### does not override 8001
|
In addition, I connected both TCP ports using APRSIS32
[0L] KB8RCO-2>APWW11,WIDE1-1,WIDE2-1:@173559h4209.35N/08346.30W1 EXPERIMENTATION [1L] KB8RCO-2>APWW11,WIDE1-1,WIDE2-1:@173559h4209.35N/08346.30W1 EXPERIMENTATION
[0L] KB8RCO-2>APWW11,WIDE1-1,WIDE2-1:@173559h4209.35N/08346.30W1 EXPERIMENTATION
I enabled 3 RF ports (8001, 8010, 8011) and opened log files for each. There is a delay between 8001 opening and 8010 and 8011 opening - which implies my theory is correct.
Although it opens a TCP port and the port is there (available), APRSIS32 does not appear to do anything with 8001.
When APRSIS32 beacons, there appears 2x the message for [0L] implying it sends on 8001 and then again on 8010.
On Thursday, July 8, 2021, 1:01:28 PM EDT, Rob Giuliano <kb8rco@...> wrote:
I just compiled V1.7 and tried to change the TCP KISS port. As stated, the 'default' port does not change, however when specifying a port, it looked like this: Dire Wolf DEVELOPMENT version 1.7 A (Jul? 8 2021)
Ready to accept KISS TCP client application 0 on port 8001 ...
Ready to accept AGW client application 0 on port 8010 ...
Ready to accept KISS TCP client application 0 on port 8011 (radio channel 0) ...
So it appears you can assign the new port by radio channel. Both appeared to be active, so it appears the issue is with the generic port being set to the default and not re-assigned.
So I went with
? KISSPORT 8010 0
? KISSPORT 8011 1 And 3 KISS TCP ports were open: Ready to accept KISS TCP client application 0 on port 8001
Ready to accept AGW client application 0 on port 8000
Ready to accept KISS TCP client application 0 on port 8010 (radio channel 0)
Ready to accept KISS TCP client application 0 on port 8011 (radio channel 1)
So it looks to me like the default KISS TCP port is being opened before the config file is read with the information needed to open it, so a default port is always opened.
On Wednesday, July 7, 2021, 9:29:55 PM EDT, Roger <roger@...> wrote:
Thanks, David
I did revert to 1.6 stable version and all is well.? Just thought
I'd give the new beta a spin-
Appreciate your reply and confirmation.
Roger,
N1XP
On 7/7/21 1:49 PM, David Ranch wrote:
Hello Roger,
I just tested it and I see what you're seeing.? Ultimately, this
seems to be a bug with v1.7 so unless you specifically need the
BETA v1.7 release, please use the released v1.6 version.
--
$ sudo direwolf -t 0 -d o -a 100 -c /etc/ax25/direwolf.conf
Dire Wolf DEVELOPMENT version 1.7 A (Jul? 7 2021)
Includes optional support for:? gpsd cm108-ptt
Reading config file /etc/ax25/direwolf.conf
Audio device for both receive and transmit: plughw:1,0? (channel
0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample
rate / 3.
Ready to accept AGW client application 0 on port 8003 ...
Ready to accept KISS TCP client application 0 on port 8001 ...?
<---------------------------------
Ready to accept KISS TCP client application 0 on port 8004 ...
--
Here is a confirmation of the open ports:
--
$ sudo lsof -nPi | grep direwolf
direwolf? 792?? root??? 3u? IPv4? 18033????? 0t0? TCP *:8003
(LISTEN)
direwolf? 792?? root??? 7u? IPv4? 20010????? 0t0? TCP *:8001
(LISTEN)? <----------------
direwolf? 792?? root??? 9u? IPv4? 18035????? 0t0? TCP *:8004
(LISTEN)?
--
This seems like this is a bug introduced in Direwolf v1.7 as I
don't see this behavior with Direwolf v1.6:
--
$ sudo direwolf -t 0 -d o -a 100 -c /etc/ax25/direwolf.conf
Dire Wolf version 1.6
Includes optional support for:? gpsd cm108-ptt
Reading config file /etc/ax25/direwolf.conf
Audio device for both receive and transmit: plughw:1,0? (channel
0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample
rate / 3.
Ready to accept AGW client application 0 on port 8003 ...
Ready to accept KISS TCP client application 0 on port 8004 ...?
<--------------------
--
--David
KI6ZHD
On 07/05/2021 06:28 AM, Roger wrote:
New install of Direwolf dev1.7 does not allow changing
KISSPORT? FROM 8001.
My CONF file, direwolf.conf:
? ADEVICE plughw:1,0
? ACHANNELS 1
? CHANNEL 0
? MYCALL N1XP
? MODEM 1200
? AGWPORT 8003
? KISSPORT 8004
When direwolf is executed the following appears:
Dire Wolf DEVELOPMENT version 1.7 A (Jul? 4 2021)
Includes optional support for:? cm108-ptt
Reading config file dwuhf.conf
Audio device for both receive and transmit: plughw:1,0?
(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100
sample rate / 3.
Note: PTT not configured for channel 0. (Ignore this if using
VOX.)
Ready to accept AGW client application 0 on port 8005 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Ready to accept KISS TCP client application 0 on port 8004 ...
Why is KISSPORT 8001 still appearing??? It seems that 8001 is
hard coded into the binary - or am I doing something wrong?
Suggestions and help, please
Roger, N1XP
|
