On Sat, 11 Sep 1999, Luiz Catalan wrote:
> > Two AX.25 interfaces with the same hardware addresses just isn't allowed.
> I can understand this and it sounds really strange, but I dont know how
> to bind the port r0 to the radio. If I make "call scc0 pp5xxx" I have
> nothing working, except errors like:
What binds an AX.25 network interface to an ax25-utils port is the
callsign (hardware address). That is also the reason those ports _must_
have different callsigns.
So now that you have done:
ifconfig scc0 44.174.0.1 hw ax25 pp5blu-8
and have an entry in axports that mentions PP5BLU-8, you actually have
bound the network interface to the ax25-utils port and should be all done.
Just try "call r0 pp5mpa". That should work.
> -> I intend to get tnos and gateway digi using the same radio port, and
> also in order to get fbb fwd'ing through it. How?
I'm not an expert on NOS, it's been several years since I've used any NOS
version so I'm not sure if I can help you here. Anyway I think you can
make TNOS to share the radio port simply by using the kissbridge or
kissnetd you mentioned. Just use it to bridge scc0 <-> /dev/ptyXX and then
in TNOS "attach ... /dev/ttyXX ...". Just leave kissattach outside all of
this... :-)
FBB should of course use the standard kernel AX.25 services ie. port r0 in
your case. Nothing special there.
> > > The syslog shows (weird!):
> > > Sep 11 00:36:26 hamgate kernel: protocol 0000 is buggy, dev scc0
> ...
> >
> > This isn't dangerous.
> Ok, maybe due the error in config.
No, it's actually an incompatibility between the current kernel AX.25
implementation and the rest of the kernel networking code. Someone should
fix that but in the mean time you can safely ignore the messages.
--
--... Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ...--
