Hay,
I have important question for configuring Ruter by OpenWRT 18 with LuCi
Is an exam task!! I have 1 month for teach pupils how it config:
What is/are the question(s) ?
Also, isn't this cheating ?
Hallo,
just starting with OpenWRT
I can click on LuCi and log in via Telnet.
I can throw screens from my LuCi here, I can show the config.
I need a how to manual for the problem shown, or a config file save for my router for V-lan routing.
I showed a starting example because then it is easier to relate to the topic.
Grzegorz
you haven't showed us any problem, which is a problem, too
there's just a network drawing, there's no description of a problem
indeed, if there's additional (uselful) information attached to it.
again, what's the question.
OK
problem: how to configure Route in OpenWRT for above schema?
I must to solve the routing problem between vlan10 and vlan 20. I made v-lans on the switch but.. how to configure interfaces in ruter?
so it is cheating
you can start here ....
START IS OK BUT.. NEXT STEPS? ok .. for 1/2 h ..rest
and thank You
Dear colleague, as I wrote, the problem is the limited amount of time to resolve this issue. The review of the given material did not help in a quick solution.
I know the general rules, I will read the details further. Unfortunately, there are no solutions in LuCi.
I have already received a hint on another forum: this is done like a guest network or: read about V-lan.
I can read - unfortunately - there is a lot of possibility here and I do not have an algorithm for clicking on solutions.
I believe he is the teacher. However I don't get the point of teaching something you obviously have no clue about and asking in forums.
Apart from that, if we presume that the OpenWrt is the 1941 Router1 and you want to do intervlan routing, then you only need to create a vlan 2 in the switch page of Luci, then make it tagged for the CPU and the lan port that connects to the switches. Also make lan port that connects to the switches tagged for vlan 1. Add a new interface under network/interfaces, assign it to eth1.2 physical interface, add static IP/mask, and assign it to lan firewall zone.That's all.
And this is the first concrete answer in a month :).
I'd like to add that if I had other support, I wouldn't ask advanced users on forums.
I also have no choice - I only have the equipment I have.
I noticed that forum members often consider the forum a place to show off their level of knowledge.
I have searched quite a lot of internet resources and found no simple guide.
for example, such as this one to r. CISCO:
I will try to implement the recommendations and, if I do not do it correctly myself, I will write.
based on your previous posts in this thread, it was probably because it took you more than a month to actually form a question ...
and you again about it ... - read - I did not write to you here. First, I looked for other sources. Maybe it was a mistake - but the problem of routing, typical of teaching, has not been described anywhere so far. Neither on YT nor on other forums and sites I found a specific manual.
I've been concerned with the subject for so long that its details escape me.
I implement my colleague's recommendations, trendy, and I see that I have not provided what is in the CISCO listing, i.e. the subnets to which the v-lans belong.
In this situation (vlan 20 >> 10.0.20.0, vlan10 >> 10.0.10.0
the solution is perhaps a little more complex?
This forum doesn't specialize in teaching. Sure you can find some material here, but the scope is to show how to implement something and troubleshoot problems, not to teach what is this and what is that.
It doesn't make much difference. It's an example and you can use whatever you wish as addresses for the interfaces.
As I wrote - I turned to you at the end, because other sources have failed.
At the end, can I ask for a hint on how to finally proceed? I will not even insert a nano into my router. It remains LuCI.
I added vlan 2 in the settings as recommended. tagging is enabled. now you need to configure subinterfaces for LAN layer 3. Any hint?
First off the "router on a stick" use case has WAN packets entering the router and LAN packets leaving on the same port, but with different VLANs. Your diagram doesn't show any WAN connection to the Internet at all so it is not clear if that is the case.
On that TP-Link, the eth0 port is the blue WAN port on the back of the router. It is a direct connection to the CPU which bypasses the switch. So you can instantiate VLANs on that port simply with the notation eth0.10 or eth0.20 as the physical setting for a network. Those VLAN tags will appear on the cable without any switch configuration, since the eth0 port does not involve the switch.
The eth1 port does go through the switch to the yellow LAN ports on the back, so VLANs there are a two-step process. First go to the switch page and click the Add button to make some additional VLANs. Number them as needed(*). Make them all tagged to the CPU and tagged on the port which will be connected to the Cisco switch. Mixing tagged and untagged on the same cable is an advanced topic and not recommended, so set to off in VLANs that you aren't using. Then use eth1.X for your networks. If the number X exists in the switch, the packets will pass through to the cable(s) that are selected. If the cable port is set to tagged, a tagged packet will be sent out, and if set to untagged, the VLAN tag will be removed to be compatible with non-VLAN aware devices, which is equivalent to the Cisco switchport mode access.
(*) Certain hardware with an Atheros internal 10/100 switch cannot directly handle VLAN numbers higher than 16. That is likely the case with the WR-841. The cheat would be to modify the network so all VLAN numbers are 15 or lower. It is possible to use VLAN numbers higher than 16 on that hardware but it requires CLI configuration not LuCI.
I do not know if wan will be slow in the test task, so rather you need to practice configuring LAN ports.
I know the internal layout. It is similar to the Asus from the VLAN guide cited earlier.
vlan numbers are not relevant to the job.
I will also add that I am not using the cisco switch - this is just an example of a schematic. I have tp-lik sg105e at my disposal - simple and realizes 802.1Q with port tagging.
I'll practice after class. We'll see what we can do.
