Posts by elonesna

  • Acess point with ip_forward causes problem to the ethernet

    Your device has the address 192.168.0.194 on the eth0 interface whose domain matches the router.

    Your device also has the address 192.168.1.1 on the tether interface.

    Your device knows that the exit route to the internet is 192.168.0.1 because the router told it through dhcp or you told it with the manual address assignment.

    For a device 192.168.1.2 in the 192.168.1.0/24 domain to know how to go to the internet, it will be necessary to establish a route to 192.168.1.1. This is done by manually setting the tether connection parameters (gateway = 192.168.1.1) for the device 192.168.1.2. But this is not enough because it is also necessary to bridge 192.168.1.1. For example like this in the 192.168.1.1 device:

    # bridge tether <-> eth0

    echo 1 > /proc/sys/net/ipv4/ip_forward

    echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter

    iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

    iptables -A FORWARD -i eth0 -o tether -j ACCEPT

    iptables -A FORWARD -i tether -o eth0 -j ACCEPT

  • Acess point with ip_forward causes problem to the ethernet

    I have not seen sensitive information. You have a lot of interfaces which is normal when docker is installed. That there is more than one gateway is also normal but there will only be one gateway that has an Internet connection, it will be the router.

    If you want to establish a route to the internet for unresolved IP addresses you can write:

    route add -net 0.0.0.0 netmask 0.0.0.0 gw <router-ip>

    Another thing: The interfaces of a device (which can be many) do not see each other, to do this you have to establish forwarding rules (iptables commands). If you want the rules to be absolutely bidirectional you have to remove "iptables -A FORWARD -m conntrack --ctstate RELATED, ESTABLISHED -j ACCEPT" and put instead "iptables -A FORWARD -i eth0 -o <interface> -j ACCEPT ".

    If you have problems with docker services, they can be solved very easily by adding the parameter "--net=host" during the creation of the container, in this case the listening ports of the service can interfere with those of LE.

    More examples:

    Suppose device 192.168.10.12 wants to access device 192.168.20.45. Both domains 192.168.10.0/24 and 192.168.20.0/24 join in a third device with two interfaces and addresses 192.168.10.88 and 192.168.20.98.

    In the device 192.168.10.12, a routing rule must be established "route add -net 192.168.20.0 netmask 255.255.255.0 gw 192.168.10.88". And in the device 192.168.10.88 and 192.168.20.98 we will have to establish forwarding rules to create a bridge between domains.

  • Acess point with ip_forward causes problem to the ethernet

    I understand your complaint but you do not provide any information to diagnose the problem. The analysis of ifconfig and route SSH commands can help you find the solution to your problem. Everything works fine for me and when a target (special IP address) is not reachable I add routing rules (route command), everything is very easy. Remember that forwarding and routing rules remain active until the next reboot. If you write two contradictory rules in the same session, it will never work.

  • Acess point with ip_forward causes problem to the ethernet

    Try this in /storage/.config/autostart.sh (I use it to connect the zerotier interface with the ethernet interface), it works very well for me.

    You will have to find out the name of your hotspot interface (use the ifconfig command) and substitute it in <interface>. If eth0 has another name, change it too.

    Code
    # bridge <interface> >>> eth0
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i <interface> -o eth0 -j ACCEPT

  • Chrome Addon missing Video Acceleration Information

    I have installed the Chrome addon and initially it worked fine on LE x86_64, now it no longer works, I have uninstalled it and replaced it with the headless jlesage/firefox docker (*) which works great via VNC on port 5900 (I have moved the VNC server LibreELEC addon to port 9900).

    The command I have used to install it is:

    The command I use in /storage/.config/autostart.sh to start the firefox service is:

    Code
    docker start firefox

    Note (*) .- The use of my LE x86_64 is double, on the one hand it is a Kodi client for family TV and multimedia use (an on-screen web browser looks very small and is not usable), and on the other hand they are running multiple headless servers for remote use (tvheadend, firefox for remote smartphone-tablet-pc use, pi-hole as firewall and private DNS, samba for read-only users, ftp for read-write users, sftp-ssh-vnc for remote management , syncthing for backup of smarphones, double-commander as an alternative to mc, xupnp2 to distribute TV to Smart-TVs, kodi upnp server to distribute multimedia to Smart-TVs, and zerotier-one to allow remote access to devices outside the home network.

  • I can't ssh to Raspi when VPN is connected - Firewall issue?

    Quote from departy

    Raspberry Pi 4 connects with VPN Manager to LAN 1.

    I cannot SSH to my raspi from LAN2.

    I think that what happens to you is normal and it has always happened to me. If the VPN server is installed on the router then it only supports incoming connections from the internet. If the VPN server is installed on a home network device then it can only be accessed from the internet using nat on the router or from the home network using the home network address for the server device.

    I have not used VPN servers for more than a year, now I use zerotier from a CG-NAT operator network that is difficult to access from the internet, that is, if you ask me what my public IP address is, I will answer that I do not have any because it is always very temporary, but everything works thanks to zerotier, within the home network and also from anywhere. I could say that I have a domain that works at home (home network 192.168.0.0) and another virtual domain (10.10.0.0) that works from anywhere on the internet, within LibreELEC. At LibreELEC startup I establish the interconnection forwarding rules between subnets with simple 'iptables' commands.

    With another device connected to zerotier from anywhere, including my home, my LibreELEC server address is always the same 10.10.182.35, and I don't need any DDNS service.

    This would also be valid for your case, sharing the zerotier virtual domain with a device located in your parents' house.

  • There is no HDMI output when TV turns on later than LibreELEC

    Solved

    During the LibreELEC installation I used the HDMI2 port of the PC. LibreELEC configured itself to boot on this port. A few days later I switched to the HDMI1 port and thereafter LibreELEC was unable to activate the TV when it was turned on later than LibreELEC.

    Conclusion: LibreELEC configures itself to turn on the TV during the installation process.

    More informationfor for x86_64 processors here EDID - LibreELEC.wiki.

  • There is no HDMI output when TV turns on later than LibreELEC

    Quote from Klojum

    Turn on the TV first, then the RPi... LibreELEC needs to do a HDMI-handshake, which isn't possible when the TV is off.

    Also, read here: "No signal" on TV with Raspberry Pi 4, after LibreELEC logo.

    "Turn on the TV first" - Not possible, the PC works 24/7. It is a TV server (tvheadend), multimedia server (Samba and FTP) and automatic smartphones backup server (syncthing) for my house and the houses of my relatives (zerotier-one). It reboot at dawn when all the TVs are off.

    "then the RPi ..." - It is not an RPi, it is an x86-64 PC, the solutions in the link do not work.

    Note.- When the LibreELEC server starts up with the TV turned off, a VNC session (tigerVNC) can be started but always in "virtual screen" 1024x768p60Hz mode and no other resolution can be chosen. When the TV is on and LibreELEC is working fine, then multiple resolutions can be chosen. I manage all LibreELEC and CoreELEC devices from my smartphone. With CoreELEC and ARM Amlogic processors as a server I never had any problems.

    The command

    Code
    /usr/bin/xrandr --output HDMI1 --mode 1920x1080 --rate 25

    works inside SSH but not inside crontab.

  • There is no HDMI output when TV turns on later than LibreELEC

    If my TV is off when LibreELEC starts up then there is no HDMI signal when I turn on the TV.

    I have not been able to solve the problem, only assign a key on the remote control to restart the mini PC with the TV on.

    Does anyone know how to solve this problem other than restarting the mini PC with the TV on?


    Notes:

    - Mini PC with Intel i5-5257U hardware (and with Iris Graphics 6100) and two HDMI outputs.

    - LibreELEC stable 9.2.6 running 24/7 as a server with daily scheduled restart. Running services: SSH, SFTP, SAMBA (read-only services), FTP, TigerVNC, tvheadend, zerotier-one, syncthing, oscam, portainer, and docker.