| |
KQ6UP > FBB 13.04.23 14:33l 41 Lines 1174 Bytes #999 (0) @ WW
BID : 30011_AB6MV
Read: GUEST
Subj: Re: (2) Route to Europe not working?
Path: IZ3LSV<I0OJJ<N6RME<KE6JJJ<KQ6UP<AB6MV
Sent: 230413/1140Z 3006@AB6MV.#SCA.CA.USA.NOAM LinBPQ6.0.23
>From kq6up%ab6mv.#sca.ca.usa.noam@kq6up.ampr.org Thu Apr 13 06:11:58 2023
Received: from kq6up.ampr.org by kq6up.ampr.org (JNOS2.0o) with SMTP
id AA6871 ; Thu, 13 Apr 2023 06:11:58 PDT
Message-Id: <30011_AB6MV@ab6mv.bbs>
>From: kq6up@ab6mv.#sca.ca.usa.noam
X-JNOS-User-Port: Circuit (MVBBS:AB6MV-1 AB6MV-1) -> Sending message
>
>
> On Wed, 12 Apr 2023 20:46:00 0100
> KQ6UP (Chris) <KQ6UP@W6TJ.#SCA.CA.USA.NOAM> wrote:
>
> -snip-
>
> Almost forgot, you will also need to add
>
> H *.GBR.EU*
>
> to the H list
>
>
> PE1RRR <PE1RRR@PE1RRR.#NBW.NLD.EURO>
>
>
>
Some clarification to add:
It is not "my" BBS per se. It is a neighbor BBS for whom I am the sysop. So the KQ6UP is
appropriate, but I do think the line above is appropriate and will fix the problem. I am
curious as to why I have to add the *GBR bit. Is it because it is out of my own HR root
area "USA"? That behavior is a little different than BPQ (at least as I am experiencing
it in Linux). I have to run BPQ in Windows because of VaraHF now, and I still have some
minor issues to sort with that (it does not seem to behave the same as the Linux version).
Thanks again, Chris KQ6UP
Read previous mail | Read next mail
| |
