SSDP NOTIFY before SSDP M-SEARCH to avoid miniupnp ignoring 169.254.0.0/16 failing dhcp?

Only checked this out once (pcap) because it only does this every 30 minutes.

Problem example, Xbox connected standby on wifi (using one x this time) is disassociated, and a few seconds later authenticated, and then associated again on AP.

Now it's connected to wifi, but doesn't have an ip4/ip6 address. ARP probes the local 168.254.0.0/16 ip4 address it is using, starts the ip6 router solicitation, advertisement, mdns, llmnr, and then SSDP M-SEARCH *

miniupnp sees the broadcast SSDP from 169.254.0.0/16, and it ignores it being from another network. miniupnpd: SSDP packet sender 169.254.190.163:49941 not from a LAN, ignoring. This repeats every half an hour

Now we power on the Xbox which is still associated but has the 169.254.0.0/16.

SSDP NOTIFY * with NTS: ssdp:alive SSDP M-SEARCH * with ssdp:discover

dhcp discover, offer, request, ack happens now and it's good to go.

Yes, the above is mostly simplified but hopefully clear enough that miniupnp ignores the local link address (169.254) if the SSDP M-SEARCH is done without a SSDP NOTIFY alive first.

Why insider post? Keep my games and apps up to date, and keep my console up to date won't/don't work if the xbox falls offline and doesn't get back online until you start it up. Reporting it through the xbox report a problem when you're online I assume would be likely to show everything is fine, you're online and have pending updates etc and maybe had no internet as to why the updates weren't done.

Maybe try a notify before m-search quirk fix/test for everyone that keeps saying auto update never works for them?

submitted by /u/smegg
[link] [comments]