4

For what it's worth I think Ron does a great job keeping the signal-to-noise ratio managed. The reason you see so many closed questions is that there is a lot of noise - a seemingly never-ending stream of people who don't understand subnetting, students copying and pasting homework questions, etc. My observation is that there tends to be observations like ...


4

You're mixing 'questions about consumer grade devices and home networking' with 'requests for product recommendations' in your examples. The latter is off topic for any network, consumer or professional. Other than that, 'network engineering' is a term commonly used for professional networking, not for home networking. There's a clear help text explaining ...


3

Your question was closed because it it clearly off topic here, as was mentioned by Ron Maupin in a comment and as is explained on https://networkengineering.stackexchange.com/help/on-topic. A suggestion where you can ask your question was provided as well. I don't see any reason to reopen the question here, because this question is clearly about host ...


2

The site name is not "Networking". The "Engineering" in the name implies it is for professionals. There is no real engineering in home networking. There are several SE sites for professionals, such as Server Fault where the names really do not imply professional, and that is why SE has a Tour, a What topics can I ask about here?, etc. ...


2

There's nothing we can do here. There's very little information about what exactly is being done. (custom application, and "raw tcp") As the problem doesn't happen through other ISPs, a VPN, or other transport mechanisms, it would, on the surface, appear to be an issue with that ISP. But we aren't the ISP, so we can't even begin to guess what might ...


2

Thanks for taking the time to make this site better! Please suggest improvements on tag descriptions. As described in this post on meta.stackexchange.com, links to external resources can be included. That post contains some nice hints on how to write good tag descriptions, so it's worth checking that before starting.


2

Short answer: things are marked off-topic because they're off-topic. The fact that people won't read the FAQ -- or understand what's there -- isn't something we can control. A great many people are absolutely certain their question is on-topic, and should be immediately answered. Instead of (again) reading the closure message, and asking their question in a ...


1

If you go to the main page of Network Engineering the majority of the questions are always closed as off-topic. That is because they are off-topic. Should we just ignore the site rules? It was closed because there's no paid support from the upstream vendor. That's sad. We all know that Mikrotik is heavily used on enterprise networks, and it's very big on ...


1

As was mentioned in a comment, you could try asking this on https://www.serverfault.com for a business network, although I'm not sure if it's a good fit there. You should check their help center to see what type of questions are on topic there.


1

My question was closed saying "not business professional" -- but my question pertains to my work. No, that is not true. The reason given for closure is: Unfortunately, questions about hosts/servers, applications, and protocols above OSI layer-4 are off-topic here. As pointed out in the comment, you could try to ask your question on Server Fault ...


1

Your question was about network cabling in a house. Residential/home networking is explicitly off-topic for Network Engineering, and you were correctly pointed to Super User, where home networking, including cabling in a house are on-topic. Even the picture in your question is a picture of a residential cable panel (the displayed terminations cannot handle ...


Only top voted, non community-wiki answers of a minimum length are eligible