Posts by seemebreakthis

Quote from chewitt

Experiment with the connmanctl move-before/move-after options, as this will change interface priority and influence the routing table.

Yes, that did it. Thanks again for helping, exactly what I needed.

The concept turns out to be using connmanctl to move the wifi connection AFTER ethernet, before connecting your VPN.

Manually experimented and made it work, then entered the following in /storage/.config/system.d/wireguard.service :

[Unit]
Description=WireGuard VPN Service
After=network-online.target nss-lookup.target connman-vpn.service time-sync.target
Wants=network-online.target nss-lookup.target connman-vpn.service time-sync.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sleep 5
ExecStart=/usr/bin/connmanctl move-after wifi_dca6329dc6c1_4c43985729083470239573469a_managed_psk ethernet_dca6329dc6c0_cable
ExecStart=/bin/sleep 5
ExecStart=/usr/bin/connmanctl connect vpn_my_vpn_service
ExecStop=/usr/bin/connmanctl disconnect vpn_my_vpn_service

[Install]
WantedBy=multi-user.target

All worked out. Marking this post as solved.

Note: I needed to add a couple of "sleep" lines before everything works without manual intervention. Don't know 100% if both of these sleep lines are needed, but as long as it works, I am not spending more time to make adjustments.

Quote from chewitt

Experiment with the connmanctl move-before/move-after options, as this will change interface priority and influence the routing table.

Thanks ! Will try.

Thanks elonesna , but my question below you will not be able to answer since you are not setting up Wireguard right within libreelec.

To others: If anyone could shed some light on a way to configure Wireguard in libreelec to steer the connection to eth0, or to allow for insertion of postup commands into Wireguard in libreelec, I'd appreciate it very much.

If anyone can shed some light on how to configure Wireguard in libreelec to steer the connection to eth0 (when both eth0 and wlan0 are active) I'd appreciate it very much.

Right now I can think of using a cron job to monitor ip route then adjust accordingly at regular intervals, but I am sure there are better and cleaner ways of doing it.

Thanks for your reply.

How can you not use connman? Does libreelec have "wg-quick"?

Also doesn't connman have the advantage of letting you see the wireguard config on the Kodi UI, so you can more easily connect / disconnect...?

I have successfully setup my wireguard client. And if wireless interface is turned off, no problem. My wireguard connection works perfectly routing through eth0 to the outside world.

But when both eth0 and wlan0 are connected (these interfaces are on two different networks with two totally separate internet gateways), it seems libreelec has a preference to set up the iproute table so that wg0 endpoint will route through wlan0 and not eth0.

Normally I would think of "postup" in wireguard config file as a way to solve this issue, by adding appropriate iproute commands in "postup" to set up routing table properly. But with libreelec using connman, I don't know of a way to add the "postup" section.

So now this is what I see when I type in "ip route":

LibreELEC:~/.config # ip route
default dev wg0 scope link
10.64.0.1 dev wg0 scope link
103.125.233.3 via 192.168.1.9 dev wlan0
192.168.1.0/24 dev wlan0 scope link  src 192.168.1.5
192.168.1.9 dev wlan0 scope link
218.252.0.24 via 222.167.31.1 dev eth0
218.252.0.25 via 222.167.31.1 dev eth0
222.167.31.0/24 dev eth0 scope link  src 222.167.31.87
222.167.31.1 dev eth0 scope link

where 103.125.233.3 is my Wireguard endpoint. So basically I'd like to see

103.125.233.3 via 222.167.31.1 dev eth0

instead of

103.122.233.3 via 192.168.1.9 dev wlan0

when everything is connected.

Any help appreciated !!

Quote from chewitt

For kicks .. force the wireless regulatory domain to the same as the router as "5GHz" is only one of 20+ radio properties, e.g.

Code

 echo "options cfg80211 ieee80211_regdom=US” > /storage/.config/modprobe.d/cfg80211.conf

and reboot to effect the change

I know this has been a while, but my 5GHz connection was unstable and I realized it was a 40MHz channel width connection. With this change the channel with became 80MHz, and the connection was quicker and more stable. Thanks !!

I downloaded it through the Raspberry Pi Imager but yeah honestly I don't know weather that's the official image. I only assumed it was back then as it was from an official channel (not LibreELEC's official channel, but official nevertheless).

So yes maybe this is the reason. Thanks.

First post here and my only experience with LibreELEC is on my Raspberry Pi 4, so not sure if this is the case for other LibreELEC builds as well.

Was troubleshooting some streaming stability issues and tweaking the parameters in advancedsettings.xml when I noticed the lines that come with the installation contain something obsolete according to the official KODI wiki:

Since I have already deleted those 3 lines, I don't even remember what the exact names were, but I had to add the following manually as a replacement:

<cache>

<memorysize>xxxxxxxxx</memorysize>

<buffermode>yyyyyyyyyy</buffermode>

<readfactor>zzz</readfactor>

</cache>

And the 3 lines I removed were inside the <network> tag. And they served the same purpose, but should no longer be there as they should now exist in <cache> instead, again according to the KODI wiki pages.

So I am just posting the info here to see if the official LibreELEC build will eventually have updated advancedsettings.xml.

Cheers.