> Yes, use the correct argument in the axparms command.
>
> The axparms command takes as its first argument after 'route add'
> the ax25 PORT name, not the kernel network device name. The PORT
> name is what is specified as the first argument in the /etc/ax25/axports
> file.
>
> pi0a is not an ax.25 port.
pi0a is an AX.25 port. I have it specified as the first argument in the
/etc/ax25/axports, I am using it with 'axparms -assoc', 'axparms -route',
call, listen,... and everything works great.
The problem is, becasue I can't specify AX.25 route for pi0a:0, which is
indeed not an AX.25 port. Also kernel does not follow AX.25 routing
specified for port pi0a, if IP packet is routed through device pi0a:0.
I think that more logical solution would be, if kernel would follow AX.25
routing specifiad for AX.25 port also for all "aliased" network devices
which are "connected" to this AX.25 port not just for "master" network
device.
Regard,
Ales
-- Ales Casar | InterNet: terhi.victor@logonet.com, lbsfhtdq@megawebservers.com, Faculty of EE & CS | qoqh.qrqdjmei@napnet.hu University of Maribor | DECnet: RCUM::ALES SLOVENIA | WWW: http://www.el.feri.uni-mb.si/~ales/