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' ?
why don't we just use the interface name?
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??
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
- users get _very_ confused about when to use a 'port'-identifier(axports) and
when the 'interface'-identifier(kernel)
see the original post above...
- 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 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.
What do you think about this?
What did I miss? Where am I wrong?
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] |
