diff options
| author | Cong Wang <[email protected]> | 2013-05-21 21:52:54 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2013-05-22 14:54:37 -0700 |
| commit | 1c8ad5bfa2be5025b0c81e3c2decd0574d453ab1 (patch) | |
| tree | f69ac9d37009526ae924c23940207b6531534f9f /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 4f45c40f2c018e5c278988521a74fd5ee06fb819 (diff) | |
bridge: use the bridge IP addr as source addr for querier
Quote from Adam:
"If it is believed that the use of 0.0.0.0
as the IP address is what is causing strange behaviour on other devices
then is there a good reason that a bridge rather than a router shouldn't
be the active querier? If not then using the bridge IP address and
having the querier enabled by default may be a reasonable solution
(provided that our querier obeys the election rules and shuts up if it
sees a query from a lower IP address that isn't 0.0.0.0). Just because a
device is the elected querier for IGMP doesn't appear to mean it is
required to perform any other routing functions."
And introduce a new troggle for it, as suggested by Herbert.
Suggested-by: Adam Baker <[email protected]>
Cc: Herbert Xu <[email protected]>
Cc: Stephen Hemminger <[email protected]>
Cc: "David S. Miller" <[email protected]>
Cc: Adam Baker <[email protected]>
Signed-off-by: Cong Wang <[email protected]>
Acked-by: Herbert Xu <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions