开云体育

Configuring DMIX and DSNOOP can be a bit complicated, especially if your soundcard does not directly support a sample rate of 12000. I'm still trying to get it to work, but I'm pretty sure others have and hopefully will post their configurations.

My -7 node is x64 bookworm and for some time now has 4 active ports on the same 40m dial frequency 7101.3 USB. These all share the same Signalink USB device at hw:0.0.

Port 5 is fx25 300b using the UZ7HO driver with QTSM port A and center adjusted +1000, 7 is QPSK V26A 600b also using the UZ7HO driver with QTSM port B and center adjusted +2000, 8 is VARA500 via wine and 9 is ARDOPC64 500MAX both at +1500 are smack dab in between FX25 and V26A. The UZ7HO driver was used for ports 5 and 7 in order to support INTERLOCK in the port definitions which last I knew was not supported with KISS.

The FX25 port handles both interactive connects and BBS forwards. The V26A port sometimes shows a few callsigns in the MH list but has so far not been used by anyone for anything other then me occasionally testing. I expected this to be busier given some of the chatter a while back about using V26A but at least for me activity is very light here in EPA. Same thing with ARDOP 500MAX. Other than my testing from the mobile in nearby parking lots and such it is hardly used but it does work. The VARA500 port has thus far been used by several for BBS forwards and works well for that. I did not expect nor has there been any interactive use of that port that I noticed.

I never had an issue with ardopc so although I saw the release notice for ardopcf I have not tried it and cannot confirm it will work with a configuration like mine. Anyway all that said a configuration like this on x64 bookworm requires a $HOME/.asoundrc file which can be complicated if unfamiliar and requires corresponding adjustments in the wine registry for VARA. It also requires a bit of CPU horsepower and although I do not use rPi devices I've been told by others that tried similar configs as above that rPi's are unable to do this much at once especially where wine is required.

Anyway following is a sample $HOME/.asoundrc that works here:

pcm.SLUSB5 {
? type hw
? card 0
? device 0
}
pcm.SLUSB5_dsnoop {
? type dsnoop
? ipc_key 50001
? ipc_key_add_uid false
? ipc_perm 0666
? slave {
??? pcm "SLUSB5"
??? channels 1
??? rate 48000
? }
}
pcm.SLUSB5_dmix {
? type dmix
? ipc_key 60001
? ipc_key_add_uid false
? ipc_perm 0666
? slave {
??? pcm "SLUSB5"
??? channels 1
??? rate 48000
? }
}
pcm.SLUSB5_asym {
? type asym
? capture.pcm "plug:SLUSB5_dsnoop"
? playback.pcm "plug:SLUSB5_dmix"
}

Note that a "rate slave" block used to be required in a .asoundrc for ardopc to work properly but a while back alsa updates enabled removing it and using "rate 48000" within the slave section of the dmix and dsnoop PCM's instead thereby simplifying the .asoundrc a little. Note also that at least in my configuration that last section for the asym required prefacing SLUSB5_dsnoop/dmix with "plug:". It did not work well without it. And for wine to share the Signalink for VARA with everything else required updating the wine registry to make the asym available for use in s/w. Here is a screenshot from the output of "wine regedit":

The ALSAInputDevices and ALSAOutputDevices must be created to specify whatever name was chosen for the asym in $HOME/.asoundrc.

The QtSoundModem.ini file required manual edit to also use the asym:
SndRXDeviceName=SLUSB5_asym
SndTXDeviceName=SLUSB5_asym

The ardopc64 specifies using SLUSB5_asym on the command line and I run it within a wrapper that restarts it when s/w decides to tell it to shutdown after using it.

And of course the Soundcard section of the VARA.ini file also specifies:
Input Device Name=In: SLUSB5_asym
Output Device Name=Out: SLUSB5_asym

As usual with stuff like this YMMV but if it helps at all this is what works for me.

73 de Rich WA3WLH

开云体育

I've not tried it, but I suspect it needs a newer version of Qt than will run on XP.

73, John

Wo? I am going to ask a question?

when I leave my “home” command info in BPQ in a bbs that I “visit”!?

n5dat n2nov ww4bsa n9mel

is most correct to leave “my” bbs call there?

n9pno

OR

n5mdt

?my amateur operator
bbs (gate) (neighbor) (next path) that
? “gives” me my mail?

I have only one path on ip.

That is what I call my gate. That is also my first hop port. that is my only port.

At this time ip is only port active till I learn more.


it took me a lot of thinking just to ask this question.
George N9pno in Iowa

What confused me, Mark, is that your node in NJ is not shown on the BPQ Node Map so I was looking for errors and routes based on there only being one node. Apparently there is no LOCATOR or other position data for the node in NJ, so it is not shown.? And because of that manually inserting a route to you sends everything to NC.

The other thing that had me confused is the multiple HA listed for you in my WP.? When you connect to someone else' BBS it may or may not ask you for your HOMEBBS, and if you do not set it, then that BBS advertises your HOMEBBS to be that bbs.

Maybe if you allowed your NJ node to be shown on the node map it may clear up some things for a few of us.


Mark

You can run both ardopc(f) amd QtSoundModem at the same time. On Windows it is trivial, as Windows allows sharing a sound card. The Linux ALSA hw: driver does not let you share the same soundcard with multiple applications, but there are ALSA plugins DMIX and DSNOOP which will combine streams. Pulseaudo will also allow sharing, but has it own problems.

Configuring DMIX and DSNOOP can be a bit complicated, especially if your soundcard does not directly support a sample rate of 12000. I'm still trying to get it to work, but I'm pretty sure others have and hopefully will post their configurations.

73,

John

I think ARDOPCF uses "hw:1.0" and QtSoundModem does also.
May I 'unconfigure' my 'AX.25_A' modem in QtSoundModem and
configure ARDOPCF to use "hw:1,0 Channel_A" or similar in its place.
It would be very nice to be able to run AX.25, IL2P, and ARDOPCF
on one radio and 3 kHz band segment.

73, Chuck

On 6/7/24 12:06, Mark Herson, N2MH wrote:

Let me chime in? ...

Yes, I have been sending out a number of messages to myself. Yes, that's akin to having an argument with yourself. But, there's a method to the madness. And, yes, one or two of them may have been incorrectly addressed. Mainly by leaving out the NJ in the HA. That's probably what sparked this thread in the first place.

I have had a bbs for about a year now, in New Jersey. Only lately have I been serious about it. So, I have been adding forwarding partners and developing appropriate routing to them. I have found that to understand how to route traffic out of a bbs, it is helpful to know how traffic comes into a bbs. Thus, the messages to myself.

And, I have found that some routing is not so obvious. Case in point... Maryland is to my south, past Pennsylvania. So, to get to MD, I would think that I would send traffic to PA. Wrong! One message from MD went to Maine to another BBS in Maine, then to New York City and then to me. Another message from MD went to Connecticut to a bbs who is a forwarding parther of mine. So, to me, to get to MD, I have to go north? Funny stuff these forwarding routes. I could go on. The best ones are those BBS's who report that they have no forwarding route out and that the message may not be delivered.? Really ??

Finally, let me add some more confusion to the mix. Just recently, I have brought up a BBS in North Carolina, in addition to the one in NJ, also with the basic callsign of N2MH. So, as noted by some people above, there appear to be conflicting HA's for me. Well, both are accurate. Fortunately, mail for me destined for NC automatically gets forwarded to NJ where it gets forwarded to my master email account for all Ham Radio email systems: Winlink, AX25, AMPRnet, and MeshMail.

73, Mark, N2MH

Hi, Mark et alia:

I read the [@USA] bulls to see who is forwarding to whom.
If I see an option to fill in a forward destination...although it seems to be the wrong azimuth,
I ask my forwarding neighbor: "May I route <hierarchical address> through you?".
Once I get an OK, I feel comfortable that I will not be creating a loop.
I have been on 40 (dusk>dawn) or 20 meters (daylight), 2 AX.25 and 2 IL2P modems .
I can forward 2+ states away, but sometimes not to my neighbor states!
I am in Ohio and am seeking a Michigan and Kentucky RF forwarding partner.
Once the tree in the front yard gets tall enough, I plan to add 80 meters (overnight).

73, Chuck

So, to me, to get to MD, I have to go north?

In a world of RF-only forwarding, then the compass points around you
would be the best path to a destination. In the world of mostly internet
routing, the best method would be for each bbs sysop to figure out what
state or country is best served by each of their forwarding partners. I
would also dig into a forwarding partner's system to see who they would
then forward to. To willy-nilly toss messages in every direction hoping
that it arrives where it should is just plain SLOPPY. If you are going
to be a bbs sysop, then learn what it means and keep on top of things.
I just don't mean checking on your system when somebody emails you that
you are down. I check on my JNOS logs multiple times in the day, especially
when I get up at 6PM (after the overnight forwarding sessions), lunchtime,
after dinner and at midnight when I go to bed (sometimes more often if
something needs specific attention).

Bottom line? Know your forwarding and NetRom partners at least two levels
away, work out with them who they reliably can forward to, clean up your
forwarding scripts and proper hierarchical address handling, have proper
mechanisms for WhitePages handling and then educate your users how it
all works while keeping on eye on it/them. Forget the easy plug and pray
software/procedures or spray and pray networking links.

--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM


NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan

Let me chime in? ...

Yes, I have been sending out a number of messages to myself. Yes, that's akin to having an argument with yourself. But, there's a method to the madness. And, yes, one or two of them may have been incorrectly addressed. Mainly by leaving out the NJ in the HA. That's probably what sparked this thread in the first place.

I have had a bbs for about a year now, in New Jersey. Only lately have I been serious about it. So, I have been adding forwarding partners and developing appropriate routing to them. I have found that to understand how to route traffic out of a bbs, it is helpful to know how traffic comes into a bbs. Thus, the messages to myself.

And, I have found that some routing is not so obvious. Case in point... Maryland is to my south, past Pennsylvania. So, to get to MD, I would think that I would send traffic to PA. Wrong! One message from MD went to Maine to another BBS in Maine, then to New York City and then to me. Another message from MD went to Connecticut to a bbs who is a forwarding parther of mine. So, to me, to get to MD, I have to go north? Funny stuff these forwarding routes. I could go on. The best ones are those BBS's who report that they have no forwarding route out and that the message may not be delivered.? Really ??

Finally, let me add some more confusion to the mix. Just recently, I have brought up a BBS in North Carolina, in addition to the one in NJ, also with the basic callsign of N2MH. So, as noted by some people above, there appear to be conflicting HA's for me. Well, both are accurate. Fortunately, mail for me destined for NC automatically gets forwarded to NJ where it gets forwarded to my master email account for all Ham Radio email systems: Winlink, AX25, AMPRnet, and MeshMail.

73, Mark, N2MH

Wow! That is a jackpot.

Thanks for sharing
-Chris KQ6UP

On Fri, Jun 7, 2024 at 8:31?AM Steve G7TAJ via groups.io
<g7taj.uk@...> wrote:

Niels has a good archive. Not sure if what you are looking for (?) is there or not?
Https://ham.packet-radio.net/packet/g8bpq

Lots there above that directory too.

73s
Steve

On Fri, 7 Jun 2024, 15:15 Christopher Maness via groups.io, <christopher.maness@...> wrote:

Since Yahoo Groups have gone the way of the dodo bird, I am
looking for these files so that I can use WFBB with BPQ32. They
are not in the files section for this group. Anyone have an
old archive?



--
Thanks,
Chris Maness KQ6UP

--
Thanks,
Chris Maness

Since Yahoo Groups have gone the way of the dodo bird, I am
looking for these files so that I can use WFBB with BPQ32. They
are not in the files section for this group. Anyone have an
old archive?



--
Thanks,
Chris Maness KQ6UP

IT WORKS!! Nice, thanks!

-Chris KQ6UP

On Fri, Jun 7, 2024 at 5:24?AM Christopher Maness via groups.io
<christopher.maness@...> wrote:

I am using Qemu. I will set this explicitly and see what happens. I
have it running on a Raspberry Pi now too. DOSFBB is too much for
full emulation on a Raspberry Pi, but no problem to use mubay terminal
to connect through direwolf.

Enjoy your sailing trip.

-VY 73 de Chris KQ6UP

On Thu, Jun 6, 2024 at 11:10?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case
with BPQCODE. I'm away sailing at the moment so can't easily check so I
suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial
ports working with BPQCODE/DOSBOX but again as I'm away from home I
can't check, and it is a while since I tried on it.

73, John

On 06/06/2024 21:14, Christopher Maness wrote:

On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.

Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.

The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John

What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP

--
Thanks,
Chris Maness

--
Thanks,
Chris Maness

I am using Qemu. I will set this explicitly and see what happens. I
have it running on a Raspberry Pi now too. DOSFBB is too much for
full emulation on a Raspberry Pi, but no problem to use mubay terminal
to connect through direwolf.

Enjoy your sailing trip.

-VY 73 de Chris KQ6UP

On Thu, Jun 6, 2024 at 11:10?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case
with BPQCODE. I'm away sailing at the moment so can't easily check so I
suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial
ports working with BPQCODE/DOSBOX but again as I'm away from home I
can't check, and it is a while since I tried on it.

73, John

On 06/06/2024 21:14, Christopher Maness wrote:

On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.

Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.

The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John

What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP

--
Thanks,
Chris Maness

On 6/6/24 15:09, John G8BPQ wrote:

Rich,

The message was addressed N2MH.#NNJ.USA.NOAM but before you said that N3FUD and N3MEL nodes have #NNJ.NJ.USA.NOAM(an extra .NJ). If this is correct then only the USA.NOAM match. CX2SA has CEAM in in routing list but because there is no general agreement whether to use 2 character or 4 character continent code BPQ accepts both but converts 4 char code to the corresponding 2 char code, and CEAM converts to NA. NOAM also converts to NA, so the message gets sent to CX2SA, as that is the first match found.

The message should probably have used #NNJ.NJ.USA.NOAM, but if you include both #NNJ.USA.NOAM and #NNJ.NJ.USA.NOAM in your routing config it should work.

73, John

Great read following this thread.

John G8BPQ:

Would making 'CEAM converts to NA' a true|false setting in bpq32.cfg make sense?

SIMPLE or default could continue to include the conversion, but have an option:
CEAM_converts_to_NA=0/1
option to be used by those in .NOAM/.NA.

I am in .NOAM/.NA, thus I do not have a route to .NOAM.

Following:
In BPQ, Is there an internal conversion to or from .USA.?

73, Chuck

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case with BPQCODE. I'm away sailing at the moment so can't easily check so I suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial ports working with BPQCODE/DOSBOX but again as I'm away from home I can't check, and it is a while since I tried on it.

73, John

Ah... I would expect the 4-to-2 conversion to end up using NA for NOAM but I was not aware that CEAM would also convert to NA hence my confusion with the CX2SA routing.

It is unclear to me if N2MH sent the initial message to himself at N2MH.#NNJ.USA.NOAM or if the WW6Q BBS added #NNJ.USA.NOAM to an unqualified dest of N2MH before routing to me. If the WW6Q BBS did so it should be corrected there but is easy enough to work around by adding #NNJ.USA.NOAM in my routing as you suggest. I'll also see what I might adjust CEAM to in the CX2SA routing so as not to send anything destined for NA to SA.

Thanks John.

73 de Rich WA3WLH