On Sat, 11 Sep 1999, Tomi Manninen wrote:
Hello Tomi, tks for the answer.
[...]
> > - 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...
Ok.
[...]
> > - 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.
Yes, you are right, they are the very same. Ifconfig shows:
ax0 Link encap:AMPR AX.25 HWaddr PP5BLU-8
inet addr:44.174.0.1 Mask:255.0.0.0
UP RUNNING MTU:255 Metric:1
......
and
scc0 Link encap:AMPR AX.25 HWaddr PP5BLU-8
inet addr:44.174.0.1 Mask:255.0.0.0
UP RUNNING MTU:256 Metric:1
......
> 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:
<hamgate> /root $ call scc0 pp5mpa
axconfig: port p0 not active
axconfig: port e0 not active
axconfig: port f0 not active
nrconfig: unable to open nrports file
rsconfig: unable to open rsports file
call: invalid port setting
So, now the questions are (surely dumb ones, but I dont know the answer):
-> how to have the radio working when ifconfig'ed the network interface
scc0?
-> 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 100% sure this is the cause for the DM to be sent but I strongly
> suspect so.
I didn't realize I had two ifaces with the same callsign. I'll try change
them to another ones and have the same kissbridge/kissattach to the
remaining ports, but with different callsigns.
> 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.
Just because I was not able to get a radio connection only with scc0
(sorry, it's the first time that I use the network device replacing a
kiss port emulator) and I was unable to find how to do that in the z8530
docs, except the way I've told. So the questions above.
> > 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.
Many thanks Tomi, your first observation made a light in the way. I'll
try other options, but would I still have to deal with kissattach due the
other ports that I need?
Best 73 de Luiz - PP5AQ
sysop PP5BLU
> --
> Tomi Manninen Internet: [EMAIL PROTECTED]
> OH2BNS AX.25: [EMAIL PROTECTED]
> KP20ME Amprnet: [EMAIL PROTECTED]
