VLAN... How it works?

based on your screenshot, and this information about removing the switch, and the information about how the TV data comes in, I think you should have things set up "correctly" so if it isn't working, then it may be that some of the assumptions are incorrect. for example what if the VLAN tag isn't 100 and is something else?

What should be happening from your config as of right now is that any packet tagged vlan 100 should flow between port 1 and port 4, back and forth as if the LEDE box were a simple wire. If your TV is connected to port 4, and the modem to port 1, then if it doesn't work, it's because it's not sufficient to send packets on VLAN 100 back and forth between the modem and the TV without anyone in between. OR perhaps the switch you have isn't a pure hardware switch and the CPU needs to get involved?? I don't know about your device.

So perhaps you need to figure out if there's an alternative VLAN tag being used in your situation? Your wireshark shows your laptop trying to ARP but nothing else, that suggests no-one is receiving the ARPs, so maybe the modem isn't actually listening on vlan 100?

Hi Thanks for your confirmations, I will continue digging in this.
As you said, maybe I missed something regarding the configuration (these VLAN are undocumented by ISP, I only find some forum discussions and howto's).

I'll share if I find something interesting.

On the other hand, I was wondering: is it possible to completely disable VLANs on my device ?
I don't need them, it may help if I make my device more dummy than it is (a simple switch).

I tried the following before:

  • untick "Enable VLAN functionality" in network / switch
  • in interface/LAN, physical settings, I tried untick "switch vlan eth0.1" and tick instead "ethernet switch eth0"
    here:
    Screenshot_20180414-195516

This has bricked my device, no more ssh or Luci access (I had to reset to "factory")

I had a switch, which refused to set a port to tagged+untagged at the same time. You can check the real configuration by running swconfig list to get the device name (the one on the left) and then run swconfig dev XXX show (XXX is the device name). Please show the output - in this way it should be possible to check how the switch sees your configuration.

Please note that the ports shown by swconfig are taken from the hardware, not the port numbers you see on the case. The mapping from HW number to number on the case (used to initialize your device config) is stored in /etc/board.json.

Hi !

Here are the outputs:

root@LEDE:~# swconfig list
Found: switch0 - eth0
root@LEDE:~# swconfig dev switch0 show
Global attributes:
	enable_vlan: 1
Port 0:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:0 link:up speed:1000baseT full-duplex auto
Port 1:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:1 link:up speed:1000baseT full-duplex auto
Port 2:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:2 link:up speed:100baseT full-duplex auto
Port 3:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:3 link:down
Port 4:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:4 link:up speed:1000baseT full-duplex auto
Port 5:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:5 link:up speed:1000baseT full-duplex auto
Port 6:
	uvr: 0
	vsr: 0
	vinr: 0
	tvm: 0
	pvid: 1
	link: port:6 link:up speed:1000baseT full-duplex auto
VLAN 1:
	vid: 1
	enable: 1
	ports: 0 1 2 4 5 6t 
VLAN 2:
	vid: 100
	enable: 1
	ports: 1t 4t 
root@LEDE:~# 

the board.json:

root@LEDE:~# cat /etc/board.json 
{
	"model": {
		"id": "BTHOMEHUBV5A",
		"name": "BT Home Hub 5A"
	},
	"led": {
		"wifi": {
			"name": "wifi",
			"type": "trigger",
			"sysfs": "bthomehubv5a:blue:wireless",
			"trigger": "phy0tpt"
		},
		"internet": {
			"name": "internet",
			"type": "netdev",
			"sysfs": "bthomehubv5a:blue:broadband",
			"device": "ptm0",
			"mode": "link tx rx"
		},
		"dimmed": {
			"name": "dimmed",
			"sysfs": "dimmed",
			"default": "0"
		}
	},
	"switch": {
		"switch0": {
			"enable": true,
			"reset": true,
			"ports": [
				{
					"num": 0,
					"role": "lan",
					"index": 3
				},
				{
					"num": 1,
					"role": "lan",
					"index": 4
				},
				{
					"num": 2,
					"role": "lan",
					"index": 2
				},
				{
					"num": 4,
					"role": "lan",
					"index": 1
				},
				{
					"num": 5,
					"role": "wan",
					"index": 5
				},
				{
					"num": 6,
					"device": "eth0",
					"need_tag": true,
					"want_untag": false
				}
			],
			"roles": [
				{
					"role": "lan",
					"ports": "0 1 2 4 6t",
					"device": "eth0.1"
				},
				{
					"role": "wan",
					"ports": "5 6t",
					"device": "eth0.2"
				}
			]
		}
	},
	"network": {
		"lan": {
			"ifname": "eth0.1",
			"protocol": "static",
			"macaddr": "84:a4:23:13:6e:f4"
		},
		"wan": {
			"ifname": "ptm0",
			"protocol": "pppoe",
			"macaddr": "84:a4:23:13:6e:f5"
		}
	},
	"dsl": {
		"atmbridge": {
			"vpi": 1,
			"vci": 32,
			"encaps": "llc",
			"payload": "bridged"
		},
		"modem": {
			"type": "vdsl",
			"annex": "a",
			"tone": "av",
			"xfer_mode": "ptm"
		}
	}
}
root@LEDE:~# 

Hi gentlemen !!

Today, I was dealing with other kind of troubleshooting...my well pump was not working (in my garden).
While trying to understand what's wrong here, the pump triggered the differential circuit breaker, cutting the power of my LEDE device and everything around (TV box etc...)....
I'm not sure if something here needed a reboot...but it seems to have solved the issue. at least my TV is working fine currently !!

I will check around if everything is working, but it's already a good news !

In the mean time, thank you for all advices and help !! my 1st step is LEDE is not super-easy, but issues help to learn!

The configuration that you shown looks exactly how I would expect it to be, so yes, restart could fix the issue :slight_smile: