Forward lan connection to tv

My RPi with osmc is living happy behind the tv, with a eth cable plugged into it. For home automation I like to be able to send turn on packets to my tv, and this only works when the tv also is connected via eth cable and not by wifi. So up until now I have had a small network switch also behind the tv to split my single lan cable into both the RPi and the tv.

Recently I bought a usb-eth dongle, and I would like to be able to plug the tv into this and get rid of the network switch.

Has anyone done something like this, that could help me in how to set up my network/IP-TABLES rules to get this to work?

My idea was to do something along with:

# init
ip link add name br0 type bridge
ip link set dev br0 up
ip address add 192.168.0.4/24 dev br0
ip route append default via 192.168.0.1 dev br0

# up bridge
ip link set eth0 master br0
ip address del 192.168.0.4/24 dev eth0

ip link set eth1 up
ip link set eth1 master br0

After setting this bridge up, I also get an IP by connecting my computer to eth1, but something goes very wrong with the net routing it seems. The speed is suuuuper slow, I can connect to it on 192.168.0.4 like normal, but loose half packets when pinging my local server:

$ ping 192.168.0.5
PING 192.168.0.5 (192.168.0.5): 56 data bytes
64 bytes from 192.168.0.5: seq=0 ttl=64 time=3.761 ms
64 bytes from 192.168.0.5: seq=7 ttl=64 time=664.513 ms
64 bytes from 192.168.0.5: seq=8 ttl=64 time=26.624 ms
64 bytes from 192.168.0.5: seq=9 ttl=64 time=5.048 ms
64 bytes from 192.168.0.5: seq=10 ttl=64 time=27.030 ms
64 bytes from 192.168.0.5: seq=11 ttl=64 time=1501.874 ms
64 bytes from 192.168.0.5: seq=14 ttl=64 time=481.012 ms
64 bytes from 192.168.0.5: seq=15 ttl=64 time=75.748 ms
^C
--- 192.168.0.5 ping statistics ---
16 packets transmitted, 8 packets received, 50% packet loss

and even iperf fails completely to my local server. What am I doing wrong here?

You might be able to do WiFi on the Pi and tether it to Ethernet port for the TV

That’s exactly what I do between two veros. Connman can do the tethering but it doesn’t have a notion of tethering between two interfaces with the same technology. ethernet and wifi will be on different subnets and I think I had to massage the routing somewhere and edit resolv.conf, which might be difficult on your TV.