> 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.
Ales,
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).
It looks like a small amount of kernel work in the area of ARP lookups
for AX.25.
Terry