Interesting. Did SOME IT studying years ago, but not current.
Didn’t know implicit P2P networking is a thing. I just always put a switch betw devices.
PS, I used to actually have a “cross-over” cable (labelled as such). I’ve moved a lot since then, no longer have same “workshop” / stash.
I.e. dedicated p2p link between High availability router setups
Actually, I find LLMs to be a great tool for learning. Rather than treating the LLM as an authority, ask it to explain the syntax and terms used in whatever you’re parsing. Supplement it with reading actual manuals and wiki articles, and it’ll be quite useful.
I have by now to deal with younger colleagues who think the same and create such a mess that in 90% we can through away their assign tasks and start from scratch.
I think it depends heavily on the topic. But sys admin and networking task are really no strength of these chatbots. Even when basic tasks are explicit covered in the documentation or manuals the LLM will come up with obvious bullshit it has found on stackoverflow. It's just sad.
Edit. Typos
In my experience it might be useful for asking factual/encyclopedic questions (e.g. what is difference between L2 and L3 or explain OSI model.
But for specific configuration is really, really bad. Especially for OpenWrt.
It simply makes shit up, it told me to set values in /etc/config/* that simply do not exist.
I read the instruction for network configuration and it is very helpful. I would very much like additional information.
The answer to my question "What constitutes the building blocks to network" is (partly) found in the network configuration guide you linked:
" A minimal network configuration for a router usually consists of at least two interfaces (lan and wan) and their associated devices (br-lan and eth0), as well as a switch section if applicable.".
I am not sure either "Interface", "Device", "Protocol" are self explanatory to a layperson. Not to me anyway. I found some limited information in the guide Clarifying the term "Interface"
To have a chance to understand these concepts I think I would need additional guides on
I appreciate the great work that has been done in the documentations department but as it is it is virtually un-accessible to me. The parts that are explanatory on my level is very fragmented or non-existing.
Where do I start? I do not even know if this is the correct sub-forum to ask this question in.
This was an important detail, thanks. So you're attempting to learn basic networking and OpenWrt.
Usually the forum just handles learning OpenWrt. I can provide URLs to more Wiki pages. 
Are you referring to a general networking context?
TBH, this is such a basic (computer science) term, it's unclear if you're asking in a technical context, or asking in regards to OpenWrt and if so, are you only asking about the term appearing in the network file (or another file)?
Again, this is a well known computer science concept - I'm honestly unsure if you're asking for the OpenWrt manual, or a cursory description of the computer science term. Here's the firewall Wiki:
Edit:
Please provide a description of any section of the quote that needs more clarification or elaboration, and in turn, I'll do my best to offer.
Also:
Is there a reason a layperson has taken on the task of configuring a router firmware that's generally considered needing advanced skill (or at least a solid understanding of concepts from another platform, etc.)?
I would like to understand how to make simple networks with openwrt. I had the understanding that openwrt was like set of LEGO for networking - I can follow simple recipes to do what I want. Ideally I also want to understand how the LEGOs go together to not blindly just put something potentially dangerous in my router.
One piece of LEGO was explained in the Clarifying the term "Interface" - guide:
An “Interface” in the OpenWrt configuration must not be mixed up with a physical interface.
...
To clarify things (hopefully) let's avoid the term interface and replace it with something more neutral. What we actually configure in OpenWrt could be named a “Connector”. The configuration of a “Connector” combines all properties that are required to attach the device running OpenWrt to a network.
I am not a conputer-scientist, so I need a to map concepts and mechanisms to things that I can relate to in my world.
So in essence what I need is something similiar for devices, protocols and firewall. It might look something like this:
(Made up introduction to "devices" in openwrt)
A "Device" in the OpenWrt configuration must not be mixed up with a physical device.To clarify things the function of "device" in OpenWrt is more akin to...
Looking up Communication protocol on wikipedia is also way too abstract to relate to, ie:
A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any variation of a physical quantity. The protocol defines the rules, syntax, semantics, and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both
That's basically what I was going to attempt to describe. Since you have to use or select protocols to perform the successful connection or communication, it obviously depends on what context you inquire (as I previously alluded to). The context matters even in computer terms (hence why I inquired which config file you're asking about).
Perhaps it's best to understand the basic recipe that the default OpenWrt configuration provides, then alter it after increased understanding.
?
But it generally is physical (or used like one). I don't understand your usage of the word "physical" in your example, I assume this is because you're applying a layperson's definition to the terminology?
It is not a definition it is a made up example of how to explain a concept - Hence the
(Made up introduction to "devices" in OpenWrt).
I really have no idea what a "device" is in OpenWrt. Please explain it in a way a layman may understand.
edit: Ideally these explanations would be here:
Network basics
Really. To be clear, that URL links to the same Wiki I posted above.
Why would the explanation go in an OpenWrt Wiki?
A "device in OpenWrt" is the same as any Linux "device" (assuming you're only referring to the term "network devices"). Again, a quite ubiquitous term whose meaning differs on context.
"Linux network device" information:
Your questions and expectations quite differ from normal user inquiries, and their ability to web search.
Edit:
To be clear, this is why I asked the following to direct the conversation:
If you have additional questions, it may help if you explain what was missed in the statement you quoted regarding 'devices' (after reviewing basic computer networking educational material).
Purchase an off the shelf router/AP and run their stock firmware.
My observation is this:
If one must still come to understand the concept of a "firewall" - it's unclear how they can predetermine that "strange firewall rules" exist.
Lastly, I previously noted that the firewall rules in Post No. 1 are inactive (and far from "strange"). Lest we remain off topic, this conversation has definitely expanded beyond that.
Edit:
Also, I really must highlight this.
Users kept telling you to read the manual because that's where the developers included very important and detailed information regarding those firewall rules. Imagine that.
Let me try to explain.
I was going through the configuration files with a LLM. I now understand that this is strongly discouraged. I noticed some firewall rules that seems to me to allow traffic from wan to the router.
Afraid that these rules might be malicious in nature I commented them out.
I made this thread asking about the rules.
Early in the thread _bernd clarified that the firewall rules I had commented out was in fact neccesary for the plug and play functionality of the router.
(I have now marked his answer as solution)
I removed the # in the configuration files.
I lamented the lack of documentation in the "Basic networking" guide (the guide is there but it is empty) in the openwrt documentation.
You offered to help and I took it in the general sense of understanding basic networking. Given that the answer to the specific question was answered earlier (_bernds answer).
Sorry I was not explicit about this when the thread veered of topic. I am not used to forum protocol as I largely grew up just consuming youtube and social media in general.
I hope this clarifies the weird twists and turns.
P.S. I do have a slight notion of what a firewall is in general. But I do not know how it is configured, ie what input, output and forward actually mean in a openwrt context.
BTW - again, this is the same in any Linux system. So justification by adding "in an OpenWrt context" each time is still a weak premise.
Hang around and lurk here. And maybe subscribe to some Mailinglist to get a feeling.
And as a personal note: try to reduce learning by video. It's the worst of all media for learning.
Play around and ask if you have issues. But try to nail down your questions.
Don't worry, as long as people stay polite you will get polite and helpful answers.
Thank you both (_bern and lleachii).
I will try and find some written resource on networking on Linux and then try to reset and configure my router using the basic setup guide.
If I need some explanation for the configuration of the simple setup which forum or sub-forum would be the correct one to ask in?
I should just add this link to my signature.
https://book.systemsapproach.org/ it's free and good.
Usually this one here.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.