开云体育

loopback

Lev All Messages By This Member #10567 I started to develop a connection oriented BBS. Things on the AX.25 side started to work, but I want to have extensive testing. I use paracon as my terminal using the AGWPE interface. My question if it is possible to loop back my BBS and paracon without getting on air? My obvious solution would be to run two direwolf instances and somehow route the audio back and forth, but I'm very lazy doing that. I tried connecting to direwolf from my BBS and paracon, but they did not find each other. Thanks, HA5OGL Lev -- Levente Kovacs Senior Electronic Engineer W:
David Ranch All Messages By This Member #10568 开云体育 Hello Lev, Sounds interesting?? What is the BBS software going to be named?? Also curious, what language is it being written in? Anyway, they way I do this testing is to run two different Direwolf instances where each instance has it's own unique sound device configured in it's unique direwolf.conf file.? From there, I have audio cables cross-connected across to the other sound device.? You could also do this in VMs with a virtual sound device and then use Pipewire/PulseAudio to virtually route the audio to the other virtual sound device. --David KI6ZHD On 05/21/2025 11:32 AM, Lev via groups.io wrote: toggle quoted message Show quoted text I started to develop a connection oriented BBS. Things on the AX.25 side started to work, but I want to have extensive testing. I use paracon as my terminal using the AGWPE interface. My question if it is possible to loop back my BBS and paracon without getting on air? My obvious solution would be to run two direwolf instances and somehow route the audio back and forth, but I'm very lazy doing that. I tried connecting to direwolf from my BBS and paracon, but they did not find each other. Thanks, HA5OGL Lev
Martin Cooper All Messages By This Member #10569 On Wed, May 21, 2025 at 11:32?AM Lev via <leventelist=[email protected]> wrote: My question if it is possible to loop back my BBS and paracon without getting on air? My obvious solution would be to run two direwolf instances and somehow route the audio back and forth, but I'm very lazy doing that. Me too, but it's actually very easy if you're on Linux, no cables necessary. If you do this: $ sudo modprobe snd-aloop this will create new loopback devices (which you can see if you then run 'aplay -l', for example). Next you simply set up two instances of Direwolf to use a pair of these loopback devices. For example, in your config files: Direwolf #1: ADEVICE plughw:1,0 Direwolf #2: ADEVICE plughw:1,1 It's been a while since I did this, and I forget what I configured for PTT, but this solution works well. Martin. KD6YAM ? Thanks, HA5OGL Lev -- Levente Kovacs Senior Electronic Engineer W:
Lev All Messages By This Member #10570 On 5/21/25 20:45, David Ranch via groups.io wrote: Sounds interesting?? What is the BBS software going to be named? Also curious, what language is it being written in? It will be called OGLBBS (de HA5OGL), and it is written in Python. It uses pyham_pe. I'm going to put it to Github as soon as I have something useful. Anyway, they way I do this testing is to run two different Direwolf instances where each instance has it's own unique sound device configured in it's unique direwolf.conf file.? From there, I have audio cables cross-connected across to the other sound device.? You could also do this in VMs with a virtual sound device and then use Pipewire/ PulseAudio to virtually route the audio to the other virtual sound device. This is what I want to avoid. :-) Anyways, thanks for your curiosity. 73s -- Levente Kovacs Senior Electronic Engineer W:
Lev All Messages By This Member #10571 On 5/21/25 22:25, Martin Cooper via groups.io wrote: Direwolf #1: ADEVICE plughw:1,0 Direwolf #2: ADEVICE plughw:1,1 Do you mean you have one DW instance and have two ports, or 2 DW instance with one port each? Do you have one or two loopback alsa device? It's been a while since I did this, and I forget what I configured for PTT, but this solution works well. Well, I have no clue, but I'll try. -- Levente Kovacs Senior Electronic Engineer W:
Martin Cooper All Messages By This Member #10572 On Wed, May 21, 2025 at 1:33?PM Lev via <leventelist=[email protected]> wrote: On 5/21/25 22:25, Martin Cooper via wrote: > Direwolf #1: ADEVICE plughw:1,0 > Direwolf #2: ADEVICE plughw:1,1 Do you mean you have one DW instance and have two ports, or 2 DW instance with one port each? Two Direwolf instances (hence my Direwolf #1 and Direwolf #2 in the above) with one device configured in each. Do you have one or two loopback alsa device? You run snd-aloop once and it gives you a set of loopback devices that you can use in pairs like this. Have a look at the output from 'aplay -l' after you start snd-aloop. Martin. KD6YAM ? -- Levente Kovacs Senior Electronic Engineer W:
Marc Champagne - W1MJC All Messages By This Member #10573 On Wed, May 21, 2025 at 04:32 PM, Lev wrote: Anyway, they way I do this testing is to run two different Direwolf instances where each instance has it's own unique sound device configured in it's unique direwolf.conf file.? From there, I have audio cables cross-connected across to the other sound device.? You could also do this in VMs with a virtual sound device and then use Pipewire/ PulseAudio to virtually route the audio to the other virtual sound device. This is what I want to avoid. :-) Are you running them in kiss mode?? ?Are you creating ax[01] devices visible with ifconfig?? ?? If so.....maybe just set the default gw for each interface to the other?? ?(? since I have only one APRS linux 'interface device', so have never tried this.)
Lev All Messages By This Member #10574 On 5/21/25 23:11, Marc Champagne - W1MJC via groups.io wrote: Are you running them in kiss mode?? ?Are you creating ax[01] devices visible with ifconfig? If so.....maybe just set the default gw for each interface to the other?? ?(? since I have only one APRS linux 'interface device', so have never tried this.) I'm using the AGWPE interface. -- Levente Kovacs Senior Electronic Engineer W:

Previous Topic Next Topic