Was hoping to reply to this earlier, but this is the first chance I have had to finish my answer (so I apologize for what may now overlap Ron's answer as well).
Please consider that part of the reason your post is not on topic here is that it does not fit in this community so both the number and quality of answers you will likely get here are not what you are hoping to get. We want to steer you to ask your questions where you will get the best answers.
Guy named RonMaupin apparenty had a bad day today, and is trying to
close my question (it is "on-hold", I'm not quite sure what that
First, totally inappropriate. Second, "on-hold" is the first part of the closing process on SE sites.
I'm trying to build (i.e. engineer) the networking device, and
quite non-trivial at that. Is such a question not suited to a board
named network engineering? If so, could you please kindly point me
to a proper Stack Exchange board?
No, it is not suited to this site. This site is about engineering networks, not devices used on the network or in networking. As to which site your questions does belong, there are a number of possibilities:
- Programming/Python: Stack Overflow or possibly Software Engineering
- Raspberry Pi: Raspberry Pi
- Linux: Unix & Linux or one of the more specialized Linux sites such as Ask Ubuntu
- Electrical Engineering: Electrical Engineering - in case you are planning on building the actual device.
- Others? There are a wide variety of SE sites today covering a wide range of topics and unfortunately I am not well versed in all of them. Poke around and you may find an even better site than the ones I mentioned.
Ok, as @RonMaupin insists, and has apparently problems understanding
my question and/or board rules, let me specifically link relevant
parts from What topics can I ask about here? section:
Please read the whole section and not just the pieces of lines that you want to attempt to make fit your needs. For instance, it also does state under all those on topic points that "this is likely the correct place to ask unless it meets any of the off-topic conditions detailed below." Several of those probably do also apply to your post, but I won't make this any longer by listing the 3+ I see that appear to match your post.
Addressing the points you consider make your post on topic:
- planning or designing an enterprise / service provider network;
My case: I'm trying to design a solution for enterprise network to intercept very specific type of traffic by complex pattern analysis.
Designing a solution for enterprise network is a far cry from designing an enterprise network. Note it doesn't say designing a solution, product or concept for use in a network.
- lab scenarios involving on-topic equipment; My case: on-topic equipment is a device that I'm trying to design.
First, the equipment you list is not on topic. Nor at present is the device that you are trying to design. So in no way can you meet this requirement.
- tools used by network professionals; My case: again - I'm designing tool to manipulate network traffic.
Sure, you are designing a tool. However you skip the "used by network professionals." Let's ask if you can give me a list of at least 5 network professionals using your tool? Since you haven't even designed this tool, there is no way this can fit.
- servers operating as a router/switch/firewall; My case: my device is a server, operating as switch/bridge with traffic analysis.
This is the one that may come closest to fitting, but the intent here is that some networks make use of such boxes in an effort to reduce cost. This is about using solutions that already exist, not about developing an entirely new solution.
- design or theory of protocols used to operate a network; My case: I'm kindly requesting information (design or theory) about how
to operate a particular device in a network, to achieve particular
How do you believe your device is a protocol? It may make use of protocols, but it isn't one itself. Here we are referring to things like TCP/IP, OSPF, ICMP, ARP, etc. Protocols that are defined to allow devices to interoperate on a network.
- implementing and enforcing network security or policies; My case: I'm trying to implement and enforce network policy.
No, you are not trying to implement and enforce a network policy, you are trying to develop a solution that would allow people to implement and enforce a network policy. While the difference may be slight in regards to the wording, it is actually quite a large difference.
As you can see (unless you want to not see), there are half a
dozen subjects that qualifies the question as on-topic.
I have to apologize, but I cannot see and it has nothing to do with what I want. I think what you see has far more to do with what you want.
Again, keep in mind we would like to steer your post to where you will likely get the best answers. This is just not the section of the SE community that best fits your needs.
You nitpicking about RPi not having "paid support from manufacturer"
is laughable, to say the least. I won't even bother explaining why RPi
thing is completely irrelevant. I'm asking about Linux networking
solution, RPi was just an example one could use as development board.
We can only base our decisions on information you provide. RPi has been deemed off topic multiple times by the community here. Perhaps editing out the reference can make some posts on topic, but yours does not appear to fit that situation.
P.S.: Are there any other moderators on this site, other than
@RonMaupin? Just curious...
Yes. There are three (volunteer) moderators and the larger community (SE sites are community moderated as well). All three of us have also now posted answers to your question here and we all appear to be in agreement. Nor has any member of the community cast a reopen vote on your post showing that they may disagree with Ron's decision.