Could not open the axparms, Guess I dont have the correct decoding.
73, John

Jose Angel Amador Fundora wrote:

> On 11 Jun 99 at 14:36, Ronnie Hale wrote:
>
> > Now it is set as a kiss link, and can be configured just as the
> > radio ports are.  Works great.  I must say that I use Jnos to run
> > the radio (serial) ports, as it is more stable, and configurable on
> > the fly, AND, the parameters don't change by themselves.  After
> > using jnos/tnos I'm sure you notice that the nos is considerably
> > more reliable.  I am really not favorably impressed with the
> > ax25/kernel handling of radio ports through the serial ports.  But
> > then... I've been spoiled, and my expectations are set high!
>
> My two cents: I am running FBB/JNOS/DXNET/node, and there is a
> problem with JNOS upfront : You must digi thru JNOS, and it works
> well, but when I used BPQ and forwarded to another FBB via JNOS, BPQ
> assumed that both hops were 300 baud, not one 300 and another 38400
> on my fwd. partner system. So I try to avoid digiing whenever
> possible. So I did when I jumped from MSDOS/DesqView and
> FBB5.15c/JNOS/PackClus via BPQ. So far all software I know assumes
> that all digies are working at the same 'radio' speed, and it does
> not always applies.
>
> Linux ax25 still needs the ax maxwait and tcp maxwait that works so
> well with JNOS.
>
> Regarding configuring on the fly, I am using three scripts I found in
> John Ackermann's site. I write the params to /etc/ax25/ and then to
> the dir's ax0, ax1, ax2 . When I have to change any, just go, edit
> and run axsetparms. Here it goes, as I have it today:
>
>               Name: axparms
>    axparms    Type: unspecified type (application/octet-stream)
>           Encoding: x-uuencode
>
> 73 de Jose, CO2JA
> ---
>
>  Ing. Jose A. Amador          | Telf: (537) 20-7814
>  Depto de Telecomunicaciones  | E-Mail: [EMAIL PROTECTED]
>  ISPJAE                       |

Reply via email to