bugfix: ARP respond on all devices
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
"Carlos Velasco" <[email protected]> writes:
Hello Carlos,
Quoted 8 lines
Quoted 4 lines
I don't deny that it fixes your problem, that is not what we're talking about. We're talking about how one should fix the problem, and I'm trying to show you why "hidden" patch is not the answer to that.
Yes, and I'm trying to tell you that it's not the only way to solve it, but it is the simpliest way to do it. As I'm sure most of linux users that have steped into this "behaviour" think about it.
I can only speak for me, but I think the same.
I'd also like to constate, that not only I see the hidden patch as the better and easier way, I also think it should not only be in the standard kernel but also enabled by default.
For the majority of all cases, why should I want the current standard behaviour? If I have two network cards but each of them on different segments, I only want the machine to respond to the IP address attached to the network card on the corresponding segment. If I want both network cards with different IP adresses on the same segment (for whatever reason, maybe load balancing), I'll put them both on the same segment.
There may be reasons why someone wants the current behaviour in special cases, but I think those cases are so special that you should need additional configuration tweaks to enable the kernel doing so. *Not* the other way round.
Regards,
Julien