On Sat, 11 Sep 1999, Luiz Catalan wrote:
> Hello all,
>
> could someone give me a help? I've just installed and compiled
> ax25-apps-0.0.4, ax25-tools-0.0.5 and libax25-0.0.7 successfully. I can
> have man pages, call the commands, etc. Kernel is 2.2.12, distribution is
> Suse6.1 and I have an USCC board (worked ok under 2.0.36 and utils
> 2.1.42.a) version 3.0 (from the distribution, formerly I had 2.04). I
> started the config doing:
>
> - ifconfig scc0 44.174.0.1 hw ax25 pp5blu-8
After this you have an AX.25 network interface scc0 with hardware address
PP5BLU-8...
> and axports is:
>
> r0 PP5BLU-8 1200 255 2 VHF_1200
> e0 PP5BLU-5 38400 236 5 NOS_PORT
> f0 PP5BLU-3 38400 236 5 FWD_PORT
>
> - after that, the command is:
>
> kissbridge scc0 /dev/ptya0 (conforming the file scc_eng, in the doc
> directory of the z8530 utils) also works without complain.
>
> - then:
>
> kissattach /dev/ttya0 r0 44.174.0.1 and got:
> "AX.25 port r0 bound to device ax0" as expected.
...and now you just created another interface (ax0) with the same
callsign. Try typing just "ifconfig" to see if I'm right.
Two AX.25 interfaces with the same hardware addresses just isn't allowed.
I'm not 100% sure this is the cause for the DM to be sent but I strongly
suspect so.
What I don't understand is why you have the kissbridge/kissattach stuff
there in the first place. They don't do anything sensible in your
configuration. I'd suggest you just leave them out.
> The syslog shows (weird!):
> Sep 11 00:35:38 hamgate kernel: protocol 0000 is buggy, dev scc0
> Sep 11 00:35:40 hamgate kernel: protocol 0200 is buggy, dev ax0
> Sep 11 00:35:40 hamgate kernel: protocol 0000 is buggy, dev scc0
> Sep 11 00:35:48 hamgate kernel: protocol 0000 is buggy, dev scc0
> Sep 11 00:35:50 hamgate kernel: protocol 0200 is buggy, dev scc0
> Sep 11 00:36:26 hamgate kernel: protocol 0200 is buggy, dev ax0
> Sep 11 00:36:26 hamgate kernel: protocol 0000 is buggy, dev scc0
This isn't dangerous.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME Amprnet: [EMAIL PROTECTED]
