> I recreated the problem you describe last night, and I think you're right.
> There is something not finished there. You're right, any ax.25 route
> created for the 'master' ax.25 device should be relevant to the aliases
> as well (they do have the same AX.25 address so clearly they are meant to
> represent the same datalink entity).
I am glad I've managed to convince you that something really is wrong
here.
> It looks like a small amount of kernel work in the area of ARP lookups
> for AX.25.
How does it look like now? Can we expect this to be corrected in next
release of ax25-module (or wherever this should made)? When is it
scheduled to be issued?
Best regards,
Ales, S56SAC
P.S.: Sorry for very delayed answer. I've been on holidays, got a lot of
mails in this time...
-- Ales Casar | InterNet: alyt@mx.dy.fi, nrrtvlq@sifo.no, Faculty of EE & CS | noe.hdhllepv@karlstad.se University of Maribor | DECnet: RCUM::ALES SLOVENIA | WWW: http://www.el.feri.uni-mb.si/~ales/