Not quite sure what you mean, but here's the setup that my axparms
scripts use.
The parameters for each interface are stored in the proc filesystem,
under /proc/sys/net/ax25, with one directory for each AX.25 device.
Each directory contains a set of what appear to be text files which
hold the value of a given parameter. To change the value of a parameter
you copy the new value into the appropriate file. You can't use an editor
to permanently change the file, because it's not a real disk file, but
rather an interface to a kernel table. So, you need to do something like
echoing a value into the file rather than text editing the file.
The scripts I wrote copy the /proc files into a set of real files that
you can edit and change permanently. Then, at boot time you can copy the
changed values back into the /proc filesystem (and thus into the kernel).
The setup is pretty much this:
1. Create a set of directories under /etc/ax25/parms, one for each device.
2. Run "axgetparms" to populate those directories with the files from
/proc/sys/net/ax25.
3. Edit the files you want to change from their default values.
4. At runtime, execute "axsetparms" to change the kernel values to match
what's in /etc/ax25/parms.
You can also use axdispparms to show the current values of the kernel AX.25
parameters.
That's all there is to it. You can do the same thing with a set of echo
commands in your ax25 startup script, but these programs are (to me at least)
a little easier to manage.
Hope this helps.
73,
John N8UR
[EMAIL PROTECTED]
http://www.febo.com
In message <[EMAIL PROTECTED]>, John Feist writes:
>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 |
