Potential Bug in IGD when specifying the --local-ip Option (qp2p 0.9.22)

[Scorch-Dev]

Describe the bug

As described in this thread on the forum, a few community members are running into an issue with igd.

[sn_node] INFO [src\endpoint.rs:242] IGD request failed: Could not find the gateway device for IGD - IgdSearch(IoError(Custom { kind: TimedOut, error: "search timed out" }))
Cannot start node due to error: Routing(Network(IgdNotSupported))
[sn_node] ERROR [src/bin/sn_node.rs:118] Cannot start node due to error: Routing(Network(IgdNotSupported))

At first we thought it was being produced by incompatible CLI arguments, but once I got the full log output, on further inspection is seems to be caused by a failure in igd timing out when calling search_gateway() with the default arguments. This is something that worked in the past for me and others, but no longer does.

Perhaps it was caused by the igd version bump? Or maybe the documentation on the usage of --local-ip needs rewording, but in any case, a few people are seeing the same thing it seems

To Reproduce

sn_node --first --local-ip <non local-host local-ip>

Expected behavior
The node should start as expected and not error out.

Desktop (please complete the following information where applicable):

• OS: Windows 10, but also observed on Manjaro Linux
• Shell: Powershell
• quic-p2p crate version: sn_node 0.28.0 built with qp2p 0.9.22