Full Bleed wrote:Hardware specific solutions could be added to an appendix in the networking FAQ, too... since that's heavily referred to on the forums (particularly when searching for connection problems.) Az maintains that, so I'll poll his interest.
Ugh. I'd be happy to add that section, but it's not likely to get updated very often. Instead, I could add some description of the issues voiced in this thread (don't do port forwarding and UPNP at the same time - I don't think that's in there yet?!) and add to the step-by-step at the end that if it's still not resolved, there may be a router/hardware-specific issue and redirect them to a thread here. And that thread would be locked so that only admins and moderators would be able to add to it (to keep it clean!). It would require that someone like aliasmask or Phergus or FB be willing to add to the list of flaky/weird hardware.
I would recommend the first post in the thread link to other, specific posts in the same thread that deal with particular routers. So when someone visits the thread, they see a list of links for various router models (by manu? and model number?), but because they're all in the same thread, anyone doing a search will find it. (Hm, they might not find the first posting, though; I suppose each post could start with a reminder to check the first one to see the most recent list of hardware with known issues?)
taustinoc wrote:0.0.0.0 is a common way of indicating "anywhere."
Yeah, that's because it's defined as the INADDR_ANY constant in the IP standards.
They're slightly misusing it if they're filtering inbound packets on it, but I suppose that was easy to implement...