mikioh/ssdp: redirector.go; 3 LoC

Found a possible issue in [mikioh/ssdp](https://www.github.com/mikioh/ssdp) at [redirector.go](https://github.com/mikioh/ssdp/blob/1d63d0f561f3e46ece231429c88747e7cc3bb474/redirector.go#L125-L127)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/mikioh/ssdp/blob/1d63d0f561f3e46ece231429c88747e7cc3bb474/redirector.go#L125-L127)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, ifi := range rdr.mifs {
rdr.LeaveGroup(&ifi, rdr.group)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {LeaveGroup 2} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 1d63d0f561f3e46ece231429c88747e7cc3bb474

Start with redirector.go lines 125-127 and inspect the LeaveGroup call in the linked commit context. Determine whether passing &ifi from the range loop can cause incorrect behavior, then classify the finding as Bug, Mitigated, or Desirable Behavior as requested.

Written by the indexing model from the issue text.