Closed Keksstar closed 1 year ago
Please use the template when you open an issue. What is the downloaded image exactly ? version, file,...
Sorry for that!
File from the OpenMPTCProuter page: openmptcprouter-v0.59.1-5.4-r0+16594-ce92de8c8c-bcm27xx-bcm2711-rpi-4-ext4-factory.img.gz
Used balenaEtcher to copy the file. The 32-bit for the Pi 4B works fine, it´s just the 64-bit that isn´t working.
Did you check checksum ? Did you try the squashfs version ?
Checksum is fine. squashfs is working! So maybe an bug in the ext4 image? Can you re-compile it?
Recently I've tried many times to install OMR on the rpi4 B and not have any success to make it work , neither with openmptcprouter-v0.59.1-5.4-r0+16594-ce92de8c8c-bcm27xx-bcm2711-rpi-4-ext4-factory.img.gz nor with the beta v.0.59.2 alpha 5.4. A month ago it worked, and soon after some weeks on the boot up it couldn't connect to the server, and neither surf the web in standalone mode without the bonding... Still wonder why. Furthermoroe there's still the problem with the network interfaces that has to settle the "force link" to not go on dhcp loop when dhcp is enabled on the wan... I really hope to try a new version release as soon as possible. Thanks for your work @Ysurac , I'm looking forward for something new and stable to update both the multilan pc and the rpi 4. It's really something I can't understand on the routing side of the thing... the OMR has a DHCP pool in the 192.168.100.1/24 network; let's presume I attach an USB to LAN adapter on the rpi USB port, attach an FTTH line with 192.168.1.1/24 network... The pc connected to the lan of the Pi take the IP address 192.168.100.187 255.255.255.0 and the gateway ofc 192.168.100.1 ... well in this way the pi won't have internet access, but, if I force the DNS on my pc to be the gateway of the WAN1 connection so 192.168.1.1 I can have internet access ... Now I really don't understand why the LAN segment seems not to be natted and use the WANs gateway as NAT transaltion automatically... This is something really weird and it's the first time it happen to me with OMR. And still not using the bonding feature; just using it as a simple mod openwrt router... Really would like to understand this thing... Even if I force gogole DNS on the pc it works, so I'm just wonder why the LAN segment gateway (192.168.100.1) simply don't allow the pc to surf the web, I've never done something like that...
It's not related to initial issue... Use default gateway should be disabled everywhere. You are using alpha release, did you update also the VPS script ? Can you take a screenshot of the status page ?
It's not related to initial issue... Use default gateway should be disabled everywhere. You are using alpha release, did you update also the VPS script ? Can you take a screenshot of the status page ?
I'm using the alpha release, the server had of course been updated ( actually was a fresh install with the beta release ) at the time. You said the default gateway should be disabled everywhere, but all the times I've installed the OMR on the pi the lan comes with the flagged use default gateway, so I don't know if the alpha on the latest release of 23 July ( https://snapshots.openmptcprouter.com/5.4/rpi4/targets/bcm27xx/bcm2711/openmptcprouter-v0.59.2alpha-5.4-r0+16819-1b6e9b3f64-bcm27xx-bcm2711-rpi-4-ext4-factory.img.gz ) got some diffrences from the one you were suggested to use months ago, but turns out that the OMR itself wasn't functional neither without the bonding activated. First of all whenever I start the OMR I always settle every WAN interfaces, test all works and than connect to the VPS server, you know just to be sure everything is fine. I've tried both balena etcher and raspberrypi imager, because for some stupid reason i thought the software wasn't copied in the correct way on the pi, but it isn't seems something like that unfortunately. Even if on the lan I uncheck the use default gateway in the dashboard of OMR I don't have any connection, just using WAN 1 with an FTTH connected in DHCP... I don't know why
I still need screenshot of system->OpenMPTCProuter status page.
I still need screenshot of system->OpenMPTCProuter status page.
Ysurac at the time beeing there's nothing in the OpenMPTCProuter status page, because as I said I don't have connected the OMR router to the VPS , if you wish I'll try and sent you the screenshot, but as I said I'm worried that neither as a standalone router it works as it should...
here's the terminal of the OMR on the pi you can see the wan got ip address, and now as you've suggested I've disabled the "use default gateway on the lan"
OpenMPTCProuter login: root
BusyBox v1.33.2 (2023-01-06 16:34:46 UTC) built-in shell (ash)
PACKAGE: openmptcprouter VERSION: v0.59.2alpha TARGET: rpi4 ARCH: aarch64_cortex-a72
root@OpenMPTCProuter:~# ifconfig
eth0 Link encap:Ethernet HWaddr DC:A6:32:DC:D1:BD
inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10805 errors:0 dropped:0 overruns:0 frame:0
TX packets:15768 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:2000
RX bytes:1928772 (1.8 MiB) TX bytes:14006702 (13.3 MiB)
eth1 Link encap:Ethernet HWaddr 00:E0:4C:39:69:3C
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:61869 errors:0 dropped:0 overruns:0 frame:0
TX packets:55826 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14499006 (13.8 MiB) TX bytes:4645367 (4.4 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:7819 errors:0 dropped:0 overruns:0 frame:0
TX packets:7819 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:518641 (506.4 KiB) TX bytes:518641 (506.4 KiB)
root@OpenMPTCProuter:~#
What is the result of ip r
?
What is the result of
ip r
?
I've tried to connect to the server with the WAN1 but this is the screenshot of the status
and this is what I got from the terminal running the comand you told me
root@OpenMPTCProuter:~# ip r default via 192.168.1.1 dev eth1 metric 1 default via 192.168.1.1 dev eth1 metric 3 initcwnd 10 initrwnd 10 5.249.148.148 via 192.168.1.1 dev eth1 metric 1 127.0.0.0/8 dev lo proto static scope link metric 5 192.168.1.0/24 dev eth1 scope link metric 3 initcwnd 10 initrwnd 10
Can you try ping -c 1 1.1.1.1
and curl 1.1.1.1
via SSH from the router to check internet connectivity ?
Can you also check Status->System Logs
Can you try
ping -c 1 1.1.1.1
andcurl 1.1.1.1
via SSH from the router to check internet connectivity ? Can you also check Status->System Logs
root@OpenMPTCProuter:~# ping -c 1 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=7.83 ms
--- 1.1.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 7.832/7.832/7.832/0.000 ms root@OpenMPTCProuter:~# curl 1.1.1.1
root@OpenMPTCProuter:~#
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using only locally-known addresses for domain local
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using only locally-known addresses for domain invalid
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using only locally-known addresses for domain bind
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using only locally-known addresses for domain use-application-dns.net
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using only locally-known addresses for domain lan
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using nameserver 127.0.0.1#5353
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: using 1 more local addresses
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: read /etc/hosts - 4 addresses
Jul 25 22:56:55 OpenMPTCProuter daemon.info dnsmasq[2547]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Jul 25 22:56:56 OpenMPTCProuter authpriv.info dropbear[2707]: Not backgrounding
Jul 25 22:56:56 OpenMPTCProuter user.notice firewall.omr-server: Firewall reload, set server part firewall reloading
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Failed to connect to ubus
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Section 'zone_lan' cannot resolve device of network 'lan'
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Section 'zone_wan' cannot resolve device of network 'wan1'
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Section 'zone_wan' cannot resolve device of network 'wan2'
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Section 'zone_vpn' cannot resolve device of network 'omrvpn'
Jul 25 22:56:56 OpenMPTCProuter daemon.notice procd: /etc/rc.d/S19firewall: Warning: Section 'zone_vpn' cannot resolve device of network 'omr6in4'
Jul 25 22:56:56 OpenMPTCProuter daemon.notice wpa_supplicant[3080]: Successfully initialized wpa_supplicant
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: 8021ad
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: 8021q
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: macvlan
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: veth
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: bridge
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: Network device
Jul 25 22:56:56 OpenMPTCProuter user.notice : Added device handler type: tunnel
Jul 25 22:56:57 OpenMPTCProuter daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'lan' is enabled
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'lan' is setting up now
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'lan' is now up
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'loopback' is enabled
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'loopback' is setting up now
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'loopback' is now up
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'wan1' is enabled
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Network device 'eth0' link is up
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'lan' has link connectivity
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Network device 'lo' link is up
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'loopback' has link connectivity
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Network device 'eth1' link is up
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'wan1' has link connectivity
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: Interface 'wan1' is setting up now
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: wan1 (4056): udhcpc: started, v1.33.2
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: wan1 (4056): udhcpc: sending discover
Jul 25 22:56:57 OpenMPTCProuter user.notice firewall: Reloading firewall due to ifup of lan (eth0)
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: wan1 (4056): udhcpc: sending select for 192.168.1.15
Jul 25 22:56:57 OpenMPTCProuter daemon.notice netifd: wan1 (4056): udhcpc: lease of 192.168.1.15 obtained, lease time 4294967295
Jul 25 22:56:58 OpenMPTCProuter daemon.notice netifd: Interface 'wan1' is now up
Jul 25 22:56:58 OpenMPTCProuter user.notice firewall.omr-server: Firewall reload, set server part firewall reloading
Jul 25 22:56:58 OpenMPTCProuter user.notice mptcp: Reloading mptcp config due to ifup of lan (eth0)
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[2547]: exiting on receipt of SIGTERM
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: started, version 2.85 cachesize 150
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: DNS service limited to local subnets
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq-dhcp[4843]: DHCP, IP range 192.168.100.150 -- 192.168.100.254, lease time 12h
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain test
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain onion
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain localhost
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain local
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain invalid
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain bind
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain use-application-dns.net
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using only locally-known addresses for domain lan
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using nameserver 127.0.0.1#5353
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: using 1 more local addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: read /etc/hosts - 4 addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq-dhcp[4843]: read /etc/ethers - 0 addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: read /etc/hosts - 4 addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq[4843]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Jul 25 22:56:58 OpenMPTCProuter daemon.info dnsmasq-dhcp[4843]: read /etc/ethers - 0 addresses
Jul 25 22:56:58 OpenMPTCProuter user.notice mptcp: Reloading mptcp config due to ifup of loopback (lo)
Jul 25 22:56:59 OpenMPTCProuter user.notice firewall: Reloading firewall due to ifup of wan1 (eth1)
Jul 25 22:56:59 OpenMPTCProuter user.notice firewall.omr-server: Firewall reload, set server part firewall reloading
Jul 25 22:56:59 OpenMPTCProuter user.notice mptcp: Reloading mptcp config due to ifup of wan1 (eth1)
Jul 25 22:57:00 OpenMPTCProuter daemon.info vnstatd[5800]: Info: vnStat daemon 2.9 started. (pid:5800 uid:0 gid:0 64-bit)
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/glorytun
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/glorytun-udp
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dsvpn
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/mptcpovervpn
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/omr6in4
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/omr-quota
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/omr-tracker
Jul 25 22:57:00 OpenMPTCProuter user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/openmptcprouter
Jul 25 22:57:00 OpenMPTCProuter daemon.info [5915]:
Seems like if v2ray and shadowsocks are both running... Did you change default proxy ?
Seems like if v2ray and shadowsocks are both running... Did you change default proxy ?
I've always used V2ray without VPN on the server side, because I need both SRT and WebRTC and that settings seems only the one which works... I can try reboot the VPS, I'll do now!
The problem is on router side here, with both proxy running. How did you enabled V2Ray ?
What is the result of uci show shadowsocks-libev
and uci show openmptcprouter
?
The problem is on router side here, with both proxy running. How did you enabled V2Ray ? What is the result of
uci show shadowsocks-libev
anduci show openmptcprouter
?
here's the results
root@OpenMPTCProuter:~# root@OpenMPTCProuter:~# root@OpenMPTCProuter:~# uci show shadowsocks-libev shadowsocks-libev.hi1=ss_redir shadowsocks-libev.hi1.server='sss0' shadowsocks-libev.hi1.local_address='::' shadowsocks-libev.hi1.local_port='1100' shadowsocks-libev.hi1.mode='tcp_and_udp' shadowsocks-libev.hi1.timeout='1000' shadowsocks-libev.hi1.fast_open='1' shadowsocks-libev.hi1.verbose='0' shadowsocks-libev.hi1.syslog='1' shadowsocks-libev.hi1.reuse_port='1' shadowsocks-libev.hi1.mptcp='1' shadowsocks-libev.hi1.ipv6_first='1' shadowsocks-libev.hi1.no_delay='1' shadowsocks-libev.hi1.ebpf='0' shadowsocks-libev.hi2=ss_redir shadowsocks-libev.hi2.local_port='1100' shadowsocks-libev.hi2.mode='tcp_and_udp' shadowsocks-libev.hi2.timeout='1000' shadowsocks-libev.hi2.fast_open='1' shadowsocks-libev.hi2.verbose='0' shadowsocks-libev.hi2.syslog='1' shadowsocks-libev.hi2.reuse_port='1' shadowsocks-libev.hi2.mptcp='1' shadowsocks-libev.hi2.ipv6_first='1' shadowsocks-libev.hi2.no_delay='1' shadowsocks-libev.hi2.local_address='::' shadowsocks-libev.hi2.server='sss1' shadowsocks-libev.hi2.ebpf='0' shadowsocks-libev.ss_rules=ss_rules shadowsocks-libev.ss_rules.disabled='0' shadowsocks-libev.ss_rules.src_default='forward' shadowsocks-libev.ss_rules.dst_default='forward' shadowsocks-libev.ss_rules.local_default='forward' shadowsocks-libev.ss_rules.server='sss0' shadowsocks-libev.ss_rules.redir_tcp='all' shadowsocks-libev.sss0=server shadowsocks-libev.sss0.server_port='65101' shadowsocks-libev.sss0.obfs='0' shadowsocks-libev.sss0.server='5.249.148.148' shadowsocks-libev.sss0.key='oXpWicXttKU0dmpuWV2iAOd/EoIvGlneaw7JWGAD+jY=' shadowsocks-libev.sss0.method='aes-256-gcm' shadowsocks-libev.sss0.disabled='0' shadowsocks-libev.sss0.obfs_host='host148-148-249-5.serverdedicati.aruba.it' shadowsocks-libev.dns=ss_tunnel shadowsocks-libev.dns.disabled='1' shadowsocks-libev.dns.mode='tcp_and_udp' shadowsocks-libev.dns.server='sss0' shadowsocks-libev.dns.local_port='5353' shadowsocks-libev.dns.tunnel_address='8.8.8.8:53' shadowsocks-libev.hi3=ss_redir shadowsocks-libev.hi3.server='sss0' shadowsocks-libev.hi3.local_address='0.0.0.0' shadowsocks-libev.hi3.local_port='1101' shadowsocks-libev.hi3.mode='tcp_and_udp' shadowsocks-libev.hi3.timeout='1000' shadowsocks-libev.hi3.fast_open='1' shadowsocks-libev.hi3.reuse_port='1' shadowsocks-libev.hi3.syslog='1' shadowsocks-libev.hi3.mptcp='1' shadowsocks-libev.hi3.no_delay='1' shadowsocks-libev.hi3.verbose='0' shadowsocks-libev.hi3.ebpf='0' shadowsocks-libev.hi4=ss_redir shadowsocks-libev.hi4.local_port='1101' shadowsocks-libev.hi4.mode='tcp_and_udp' shadowsocks-libev.hi4.timeout='1000' shadowsocks-libev.hi4.fast_open='1' shadowsocks-libev.hi4.reuse_port='1' shadowsocks-libev.hi4.syslog='1' shadowsocks-libev.hi4.mptcp='1' shadowsocks-libev.hi4.no_delay='1' shadowsocks-libev.hi4.verbose='0' shadowsocks-libev.hi4.local_address='::' shadowsocks-libev.hi4.server='sss1' shadowsocks-libev.hi4.ebpf='0' shadowsocks-libev.sss1=server shadowsocks-libev.sss1.server_port='65101' shadowsocks-libev.sss1.obfs='0' shadowsocks-libev.sss1.disabled='1' shadowsocks-libev.sss1.key='oXpWicXttKU0dmpuWV2iAOd/EoIvGlneaw7JWGAD+jY=' shadowsocks-libev.sss1.method='aes-256-gcm' shadowsocks-libev.sss1.obfs_host='host148-148-249-5.serverdedicati.aruba.it' shadowsocks-libev.sss1.server='5.249.148.148' shadowsocks-libev.tracker_sss0=ss_local shadowsocks-libev.tracker_sss0.server='sss0' shadowsocks-libev.tracker_sss0.local_address='127.0.0.1' shadowsocks-libev.tracker_sss0.local_port='1111' shadowsocks-libev.tracker_sss0.mode='tcp_and_udp' shadowsocks-libev.tracker_sss0.timeout='600' shadowsocks-libev.tracker_sss0.fast_open='1' shadowsocks-libev.tracker_sss0.syslog='0' shadowsocks-libev.tracker_sss0.reuse_port='1' shadowsocks-libev.tracker_sss0.mptcp='1' shadowsocks-libev.tracker_sss0.verbose='0' root@OpenMPTCProuter:~# root@OpenMPTCProuter:~# root@OpenMPTCProuter:~# uci show openmptcprouter openmptcprouter.settings=settings openmptcprouter.settings.enabled='1' openmptcprouter.settings.sipalg='1' openmptcprouter.settings.scaling_min_freq='1500000' openmptcprouter.settings.scaling_max_freq='1500000' openmptcprouter.settings.scaling_governor='performance' openmptcprouter.settings.master='balancing' openmptcprouter.settings.disable_ipv6='1' openmptcprouter.settings.check_ipv4_website='http://ip.openmptcprouter.com' openmptcprouter.settings.check_ipv6_website='http://ipv6.openmptcprouter.com' openmptcprouter.settings.status_vps_timeout='1' openmptcprouter.settings.status_getip_timeout='1' openmptcprouter.settings.enable_nodelay='1' openmptcprouter.settings.menu='OpenMPTCProuter' openmptcprouter.settings.disableintfrename='1' openmptcprouter.settings.tracebox='0' openmptcprouter.settings.version='0.59.2alpha-5.4' openmptcprouter.settings.allmptcpovervpn='0' openmptcprouter.settings.serial='100000009b72f8c1' openmptcprouter.settings.mptcpovervpn='wireguard' openmptcprouter.settings.dns64='0' openmptcprouter.settings.proxy='v2ray' openmptcprouter.settings.ha='0' openmptcprouter.settings.vpn='none' openmptcprouter.settings.firstboot='0' openmptcprouter.settings.apilc='1690329476' openmptcprouter.vps=server openmptcprouter.vps.username='openmptcprouter' openmptcprouter.vps.master='1' openmptcprouter.vps.backup='0' openmptcprouter.vps.port='65500' openmptcprouter.vps.current='1' openmptcprouter.vps.password='9FAE7DC782DFB53293992434B7550A139A9053091108969881E19EEBA3E62377' openmptcprouter.vps.ip='5.249.148.148' openmptcprouter.vps.redirect_ports='0' openmptcprouter.vps.wgkey='TiPKhgzEKzhMnvg0YUg/t9VIbuz2uBAzvIVkhxQ69ik=' openmptcprouter.vps.available_vpn='glorytun_tcp' 'glorytun_udp' 'dsvpn' 'openvpn' 'openvpn_bonding' 'mlvpn' openmptcprouter.vps.get_config='0' openmptcprouter.vps.pihole='0' openmptcprouter.vps.kernel='5.4.207-mptcp' openmptcprouter.vps.machine='x86_64' openmptcprouter.vps.omr_version='0.1028' openmptcprouter.vps.token_error='1' openmptcprouter.vps.admin_error='0' openmptcprouter.vps.lastchange='1690331930' openmptcprouter.vps.set_firewall='0' openmptcprouter.vps.token='eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJvcGVubXB0Y3Byb3V0ZXIiLCJleHAiOjE2OTA0NjE0ODB9.z8xbuMsTDX8m-VSSpXWMeALIYx1Topfqy9lTHQlc4AQ' openmptcprouter.omr=router openmptcprouter.omr.ss_sss0='up' openmptcprouter.wan1=interface openmptcprouter.wan1.metric='3' openmptcprouter.wan1.multipath='master' openmptcprouter.wan1.publicip='93.65.56.102' openmptcprouter.wan1.asn='VODAFONE-IT' openmptcprouter.wan1.state='up' openmptcprouter.wan1.multipathvpn='0' openmptcprouter.wan1.mtu='1492' openmptcprouter.wan1.mptcp_status='MPTCP enabled' openmptcprouter.wan1.lc='1690329476' openmptcprouter.wan1.latency='16' openmptcprouter.wan1.latency_previous='16' openmptcprouter.loopback=interface openmptcprouter.loopback.multipath='off' openmptcprouter.loopback.metric='5' openmptcprouter.lan=interface openmptcprouter.lan.multipath='off' openmptcprouter.lan.metric='6' openmptcprouter.lan.multipathvpn='0' openmptcprouter.omrvpn=interface openmptcprouter.omrvpn.multipath='off' openmptcprouter.omrvpn.metric='1200' openmptcprouter.omr6in4=interface openmptcprouter.omr6in4.multipath='off' openmptcprouter.omr6in4.metric='1201' openmptcprouter.latest_versions=latest_versions openmptcprouter.latest_versions.omr='0.59.1-5.4' openmptcprouter.latest_versions.vps='0.1028' openmptcprouter.latest_versions.lc='1690321869' root@OpenMPTCProuter:~#
uci set shadowsocks-libev.sss0.disabled=1 && uci commit && reboot
Well, this didn´t help with the not-working image.... As it´s an complete different topic.
So, what else to try?
You said it was working with squashfs image, it's not the case ?
It seems to work in my eyes, but as you can see in the log of #2907 it seems to have errors? So, how can we get this image up and running? After a lot of reading here, I shouldn´t be the only one with this problem...
If you have issue with both image, the issue is not the image. Check your SD card and check the power supply.
Reflashed the SD card with Rufus instead of BalenaEtcher. Now EXT4 is working. Thanks!
Hi!
Downloaded the 64 bit Raspberry Pi 4B Image. Sadly it´s not running and the Pi stucks on the first image where it shows colors... The 32bit works fine.
How to fix this?