I'm new to the community and of course openWRT.
I know this is the LEDE community but I really hope that someone has experience enough to solve my current problem.
Long story short. I have no idea that I've bought a router not compatible for my ISP.
But in theory, it can be done by editing the SSH. I have no experience in networking
in my life that's why I'm here to ask for advice.
This router has the simplest webUI and VLAN cannot be set to get internet and IPTV.
I have no LEDE firmware flashed to my WRT32X. I am only using puTTy to input values in.
I have been searching for solutions to solve and was able to get my internet working.
My ISP needs VLAN 10 for internet connection and VLAN 20 for IPTV to work.
in this setting I was able to get my internet working for lan ports 1, 2, 3 and 4 on the router.
My next step is to add settings my router port 4 to vlan 20 and received untagged packets as follow:
config interface 'IPTV'
option ifname 'eth0.20'
option proto 'dhcp'
option disabled '0'
option device 'switch0'
option vlan '20'
option ports '0 4t 5t' #i have notice that port 0 is actually my physical port 4 on the router
option ports '0'
option pvid '20'
After all the settings are done, I was still unable to get my IPTV to work. So I search the web for more solutions and came upon setting CoS "802.1p Priority 4" on port 4 to work so I did.
ip link set eth0.20 type vlan egress 0:4
(Was helped by a fellow mate in Linksys community and he helped alot)
after all the settings I was still unable to get IPTV to work. I have been trying for almost a week now and I still cannot get it to work.
Hope this community can help me to solve the problem.
Automatically yes, however packets for a different vlan can still be received by specifying the vlan tag for the different vlan on the client.
Essentially, pvid automates vlan packet tagging for a specified interface, whereas vid will set the vlan tag, but not automate the tagging (i.e. the tag would have to be manually set on the client, something some clients do not have the ability to do)
Also, your tagging is wrong for switch0, as 4t is WAN, and that should not be bridged with LAN port 0 or the LAN CPU port eth1 (5t)
I've never configured a router for use with IPTV, however that seems sketchy to me
You're effectively disabling the router's WAN side firewall for that port , and, if my understanding of how traffic is routed from the CPU ports is correct (it could very well not be), that would allow WAN side traffic access to the LAN side CPU port, and thus to any LAN traffic, since it [eth1] is tagged.
Checking the, albeit dated, IPTV Wiki, it doesn't state anywhere to bridge WAN with a LAN side port or the LAN CPU port.
@tmomas, are your familiar with IPTV setup scenarios and whether my understanding of traffic routing is correct or not?
Extra info: The stock firmware is an Openwrt distro. You can treat it much the same as any other Openwrt. I think it is kernel 4.9 based and based off the old “DD branch” (the unbranched master of archived openwrt). Obviously there are some Linksys specific patches and packages installed.
I personally always flash via serial since I installed the 3.5mm jack for the USB-TTL Audio Jack cable. I find it's more convenient, especially since you can monitor the boot log for any issues that might have occurred to prevent the image from booting.
I switched to flashing via serial only after the NAND error that occurred ~2yrs ago, and since it was quite convenient, continued doing so because it was faster for me to do so via serial than SSH or through the WebUI. I know this way isn't for everyone, but once the required Uboot commands are memorized, it's second nature.
Anyone who chooses this route needs to ensure they build BusyBox with the resize program enabled, otherwise you're stuck with an extremely small terminal once at the shell.