I love how Coding agents allow me to implement the crazy ideas in my head! Checkout my TUI (Terminal UI) client for APRS. It now supports #digirig #mobilinkd and #direwolf. Check it out https://github.com/eusef/eusef-aprs-tui.
#amateurradio #emcomm #ham #hamradio #tui #terminalui #mapscii #
This faetouched direwolf will be part of a diorama I am preparing for the #bembelminiaturecup26 🤫 that's why it has no base!
It will be my first ever competition and to say I'm not nervous would be a big lie 😅 only two weeks left! But I'm just in it for the fun and meeting people with the same hobby! I think it's a great possibility to connect. So: will anybody here also be at the Bembel mini cup?
Would love to hear from you!
Can't get #DireWolf to actually transmit the packet audio burst via my FT-991a. I have this config setting:
Phil
monniatures
Neil E. HodgesADEVICE plughw:CODEC,0 VID PID Product Sound ADEVICE ADEVICE HID [ptt]
--- --- ------- ----- ------- ------- ---------
08bb 29b3 USB Audio CODEC /dev/snd/controlC0 /dev/hidraw0
08bb 29b3 USB Audio CODEC /dev/snd/pcmC0D0c plughw:0,0 plughw:CODEC,0 /dev/hidraw0
08bb 29b3 USB Audio CODEC /dev/snd/pcmC0D0p plughw:0,0 plughw:CODEC,0 /dev/hidraw0Bus 001 Device 017: ID 08bb:29b3 Texas Instruments PCM2903B Audio CODECI'm listening in on 144.390 MHz on my handheld while my FT-991a is transmitting, but all I get is the transmission starting and ending with no audio inside it. Any suggestions?
Can't get #DireWolf to actually transmit the packet audio burst via my FT-991a. I have this config setting:
Doughnut Lollipop 【記録係】
ADEVICE plughw:CODEC,0
Which corresponds to these devices:
VID PID Product Sound ADEVICE ADEVICE HID [ptt]
--- --- ------- ----- ------- ------- ---------
08bb 29b3 USB Audio CODEC /dev/snd/controlC0 /dev/hidraw0
08bb 29b3 USB Audio CODEC /dev/snd/pcmC0D0c plughw:0,0 plughw:CODEC,0 /dev/hidraw0
08bb 29b3 USB Audio CODEC /dev/snd/pcmC0D0p plughw:0,0 plughw:CODEC,0 /dev/hidraw0
Bus 001 Device 017: ID 08bb:29b3 Texas Instruments PCM2903B Audio CODEC
I'm listening in on 144.390 MHz on my handheld while my FT-991a is transmitting, but all I get is the transmission starting and ending with no audio inside it. Any suggestions?
Anyone know why #DireWolf is hellbent on using /dev/ttyS0 with hamlib? I have this in direwolf.conf, which should force it to use /dev/ttyUSB1:
PTT RIG 1035 /dev/ttyUSB1 38400
But it refuses:
Dire Wolf version 1.7
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:0,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 38400.
User configuration overriding hamlib CAT control speed to 38400.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
^C
QRT
Hamlib Error: rig_set_ptt command for channel 0 PTT
rig.c(947):rig_open entered
rig_settings_get_path: path=.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error
rig.c(947):rig_open entered
rig_settings_get_path: path=.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error
rig_set_ptt: rig or rig->caps is null
Invalid parameter
?WATCH={"enable":false,"json":false};
If I make /dev/ttyS0 a symlink to /dev/ttyUSB1, it works flawlessly. What gives? 
Anyone know why #DireWolf is hellbent on using /dev/ttyS0 with hamlib? I have this in direwolf.conf, which should force it to use /dev/ttyUSB1:
PTT RIG 1035 /dev/ttyUSB1 38400Dire Wolf version 1.7
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:0,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 38400.
User configuration overriding hamlib CAT control speed to 38400.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
^C
QRT
Hamlib Error: rig_set_ptt command for channel 0 PTT
rig.c(947):rig_open entered
rig_settings_get_path: path=.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error
rig.c(947):rig_open entered
rig_settings_get_path: path=.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_open(335): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig.c(1178):rig_open returning2(-6) IO error
rig_set_ptt: rig or rig->caps is null
Invalid parameter
?WATCH={"enable":false,"json":false};/dev/ttyS0 a symlink to /dev/ttyUSB1, it works flawlessly. What gives? :/
[DIREWOLF] - Ransomware Victim: Perdana Petroleum Berhad - https://www.redpacketsecurity.com/direwolf-ransomware-victim-perdana-petroleum-berhad/
#direwolf #dark_web #data_breach #OSINT #ransomware #threatintel #tor
adingbatponder 
👾
RedPacket Security