Hi,

As far as I know it is. I haven't really had time to look into it in 
more detail,
though I do have a hunch where to look.... the traffic counters may be quite
a good hint.

Come to think of it, I wonder if the behaviour is correct at all: pinging
a local physical interface generates trafic on localhost, which I think it
shouldn't, and /without INET6/ one of the physical interfaces is 
unreachable.

with kind regards,
Theo

Timo Schöler wrote:

> hi,
>
> is the problem still unresolved?
>
> timo
>
> :x!
>
> This life is a test.  It is only a test.  Had this been an actual life,
> you would have received further instructions as to what to do and where
> to go.


<snip>

>>>>> The machine in question has three network interfaces, two connected
>>>>> to the *same subnet* (public IP), the third connected to a different
>>>>> (private IP) subnet. One of the two public interfaces serves as the
>>>>> default gateway, the other is just there to catch incoming traffic.
>>>>> (The organization I work for insists on having one IP per switch 
>>>>> port,
>>>>> so the only way to have multiple IP's on the same machine (even when
>>>>> these IPs are in the same subnet) is by having multiple network 
>>>>> interfaces.)
>>>>>
>>>>> Normally I could ping all three interfaces. With a current(ish) 2.0
>>>>> kernel without INET6 I can no longer ping the non-default-gateway-
>>>>> public-IP-network-interface. For all practical purposes this 
>>>>> interface
>>>>> is dead (from the inside and outside), while the other two interfaces
>>>>> are working properly.
>>>>
</snip>