According to Thorsten Kranzkowski: While burning my CPU.
>
> Hello !
>
> > On Sun, May 09, 1999 at 04:09:50PM +0200, cybersake wrote:
> > > But when I try:
> > > #call bcsf0 PA3ESF
> > > I get:
> > > no AX.25 port data configured.
> > > bcsf0 is the baycom modem device
> > > Any tips what is causing this message?
> > > How do I configure AX.25 port data?
> > > Many Thanks in advance,
> > > 73 Sake PE1MNF
> >
> > Have you entered valid line in axports file, and if you did have you
> > made ifconfig bcsf0 with the same callsign as in axports ?
> > Do exactly as stated in AX25 HOWTO file and you will have no problem
> > getting it started.
> >
> > GL 73 de 9A3TY
> >
> >
>
> I have a fundamental question about this:
> For what purpose do we have the 'axports' file? What is the reason for
> which I have to bind a 'port' to a 'callsign' ?
kissattach needs it.
>
> why don't we just use the interface name?
Why not help kissattach by defining the names of ax ports as ax0 as the
first, after all when one names a port abcdef it will still be ax0 when its
attached and the scond port be it whatever name will be ax1.
>
> Example:
> # /etc/ax25/axports
> # name callsign speed paclen window description
> abcdef DL8BCU 4800 256 7 438.475- DB0HSK 70cm port
>
> marvin:~$ /usr/sbin/axparms -assoc df0pt th
> marvin:~$ call abcdef db0hsk
>
> that is: make a call on the interface that has the configured callsign DL8BCU
> and actually use a totally different callsign (df0pt) for that
> connection!
> How does that make sense??
That has no relavance to the question on hand, but i think you need to read
'man axparms' as what you say is not what you mean or even think.
The example above means, assign the callsign df0pt to the user account "tk"
Only root can do that so where's the problem.?.
>
> I think all the information in axports is superfluous:
> name: that's what I want to get rid of
> callsign: set with ifconfig (on the interface name ....:-) )
> speed: set with sethdlc (also on the interface name)
> paclen: set in /proc/sys/net/ax25/bcsf0/maximum_packet_length
> ----- also the interface name
> window: set in /proc/sys/net/ax25/bcsf0/standard_window_size
> description: well, _very_ important when you have only one interface .....
> and if you have more than one you should know what you are
> doing.
>
> Disadvantages of axports usage:
> - axutils stop working when you assign the same call to two or more
> interfaces
Not true or at least you can have the same callsign on every port, however
NOT in axports as such, use the VIA option in ax25d.conf when using ax25d.
> - users get _very_ confused about when to use a 'port'-identifier(axports) and
> when the 'interface'-identifier(kernel)
> see the original post above...
Same here use ax25d to have ONE AX25 call + ssid the same one listning on
every port.
> - you have to keep axports exactly up to date with the real interface
> situation - very annoying when you temporarily add a second interface for
> testing purposes etc.
I dont quite see the argument here.
When one adds a new port then one enters a new line and callsign + ssid.
Its up to the user to configure ax25d to listen on that port as well with
whatever callsign + ssid as well.
>
> I don't know about netrom or rose but guessing from the manpages the same
> arguments apply. You can use nr0 or rose0 to access these interfaces.
> By the way - one should drop "-i inetaddr" and "-m mtu" from nrattach and
> rsattach - that's ifconfig functionality.
O no, if you do that, you will have many more problems that you think,
espesaly with 2.2.x kernels.
>
>
> What do you think about this?
> What did I miss? Where am I wrong?
Possably ax25d and the use thereof.
>
> 73 Thorsten, DL8BCU
>
> --
> | Thorsten Kranzkowski Snail: Niemannsweg 30, 49201 Dissen, Germany |
> | Mobile: ++49 161 7210230 Inet: [EMAIL PROTECTED] |
> | Ampr: dl8bcu@db0nei.#nrw.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
>
--
Regards Richard.
[EMAIL PROTECTED]
