开云体育

Yes, same port, with DRAGON SINGLE in the config file 73, Martin HB9AUR

That won't work. As I said, it will respond to the node call. If you want it to respond to anything else set PORTCALL in the main part of the port config (Before the CONFIG statement). 73 John

Checking the portal there is no gateway for 44.137.80.0/28, so there would not be a specific route obtained for that via RIP44. I can ping from the linux prompt to my partner node.

May I ask as to what type of modem's they are using? (e.g. AEA, KAM or SCS) Are they getting a connect but no prompts are sent?

There trying my bbs call of N3HYM?RAY N3HYM?Sent from my Verizon, Samsung Galaxy smartphone

That totally makes sense.? My neighbor is running all of his packet stuff with a low power budget (solar) nodes. And come to think of it, most of his nodes routes do not work very well -- let me

Ok, With that it should accept connections to the Node Call and pass them to the BBS. Which callsign is the user trying to connect to? 73 John

Here is my pactor port config. PORT PORTNUM=11 ID=HF PACTOR 1,2,3 DRIVER=SCSPACTOR COMPORT=6 ; # = SERIAL COM PORT SPEED=38400 ;COM Port Speed INTERLOCK=4 CONFIG APPL BBS PSKA 250 FSKA 250 DRAGON

Martin. Are you using the same port on the Dragon for Pactor and Robust Packet (with DRAGON SINGLE in the config)? 73, John

That's a configuration for ARDOP, not Pactor. What is in your Pactor port configuration? 73 John

No worries, John.? To tell you the truth, it was kind of fun playing "Sherlock Holmes". hi hi Red:? I didn't have an opportunity to check other interfaces besides KISS, so I don't know if UZ7HO's

Ray, it appears that you are mixing two different digital ports (ARDOP and SCS PACTOR) into one defined port. You need to split the two up into proper Ports deffinitions. See the BPQ docs for ARDOP

Btw, I would welcome suggestions on using SCS 7400 Dragon pactor/robust modem and RIGblaster Advantage sound-card interface I use for HF packet mode in parallel with a single HF radio. For now I use

I am just guessing ... you have defined P123 for pactor mode in your RIGCONTROL segment of a non-pactor port. On the other side, in your recent post you did not have some similar in your pactor port.

Assuming that the address of the LinBPQ machine is 192.168.1.101 this is how it should work. LinBPQ IP Gateway communicates with machines on the same LAN, including the LinBPQ host, using NAT.? On my

These are probably link validation polls which are part of the ax.25 protocol and are controlled by the T3 setting in bpq32.cfg. Although the interval could be extended a bit from the normal setting

Thanks, Sorry about this. It is a bug introduced to the Level 2 (KISS) driver when I added the port specific CTEXT. I've uploaded new versions of bpq32 and linbpq to my beta site. 73, John

I am confused with how to use the ipgateway. 192.168.1.102 is a ip-address that does not exist in my network, it is in a DMZ. The AXIP map statement to my partner node look like this. MAP PI1BDG

Hi Rick, RF ports using which driver, KISS or UZ7HO driver etc? -Red

I have found that 6.0.21.20 is good, so it appears to have started at version 6.0.21.21, John. 73 - Rick KE0GB