> 1. The interface metric is ignored.
It is worth to note, that it never was used. 8)
Certainly, it is not used in 2.2 too.
> 2. It is not possible to change the BROADCAST and POINTTOPOINT
> flags on an interface.
These flags reflect not your personal preference, but physical
media characteristics. Ethernet is broadcast, even only two hosts
sit on wire, ppp is pointopoint by defintion.
BTW these flags were/are absolutely not essential, when choosing routes
to destination.
> the p-t-p link over the main net interface. Metric again?
Neither this, not this. Metric on routes is real solution with existing
software. But it is not desired. Kernel is not appropriate place
to store information, which it need not.
> 3. I don't know how to set a metric on a route with "ip". Nor does
> "ip" appear to display route metrics on routes created with "route"
> although "netstat" does.
ip route add 10.3.3.0/24 dev dummy metric 20
Probably, you have some old version of iproute2.
> 10.1.254.1 dev ippp0 proto kernel scope link src 172.16.1.8
> default dev ippp0 scope link
>
> Packets routed *through* the local host are fine (as expected).
> Packets originating *from* the local host are sent on ippp0
> correctly but have a source address of 0.0.0.0 (as reported
> by the remote host).
It is really interesting! What ifconfig ippp0 and ip addr ls dev ippp0
show?
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/