Moderator

@MK

@MK Take a look at this link that explains how file systems work on OpenWrt and pay particular attention to how the overlay partition works.

https://openwrt.org/docs/techref/flash.layout#explanations

@SpiderKenny in your user home directory there is a hidden directory ".ssh" , inside that directory is a file named "config". If these do not exist then you can create them. Inside the config file add an entry for each host you need to access, like this:

Host 192.168.1.175
HostKeyAlgorithms +ssh-rsa

Host 192.168.1.176
HostKeyAlgorithms +ssh-rsa

I created a FAQ for this some time ago:

https://community.onion.io/topic/4825/ubuntu-22-ssh-error

@Alexandr-Didenko You need kmod-macvlan loaded then you can configure multiple virtual devices with separate IPs.

@drmoeder I can't speak for Onion as I don't work for them. The reason Warp Core was developed was due to reliability and performance issues with the standard OpenWrt Mediatek driver and it has served its purpose well. As times passed some companies made significant investments into improving the Mediatek driver to the point that Warp Core is no longer needed. I think many of us have switched to the standard Mediatek driver for various reasons, one important reason for me is that I want to disable the AP but still use the STA, Warp Core can't do that, the Mediatek driver can.

I'm using OpenWrt 22 these days and the Mediatek driver.

@drmoeder I doubt this ill get fixed, the Warp Core stuff is closed source and the issues it was developed to address were resolved in the later releases of OpenWrt 18 and no longer are an issue in OpenWrt 19,20,21,22 and the current release 23.

@drmoeder I've done some more testing and have concluded the issue is in the Warp Core driver(s). The solution is to switch to the standard OpenWrt wifi system but I'm not sure if that is something you are interested in pursuing. You'd need to learn to use the standard OpenWrt wifi configuration tools which are not as nice as the Onion tools.

Good catch @matiaslao !

@drmoeder It seems that the routing configurations are not being read by the wifi system. I tried it on OpenWrt 22 and it works fine by placing routing entries in /etc/config/network. My guess is the issue is in the Warp driver but it;s closed source so it's just an assumption.

The hotplug script I provided earlier is adding the route, but it's getting cleared out after network finishes loading.

I found a workaround that works, but I'm not in love with it, it creates the required default route when you restart the device, but if you just restart the network the route is removed.

Here is my entry in /etc/config/network, set your own ip's:

config interface 'wwan'
option ifname 'apcli0'
option proto 'static'
option ipaddr '192.168.1.85'
option netmask '255.255.255.0'
option gateway '192.168.1.1'
option hostname 'Omega-1FE3'

Then you need to add 2 lines to /etc/rc.local:

sleep 15
/sbin/ip route add default via 192.168.5.254 dev apcli0

Another options may be to use dhcp but set an IP reservation on your router (if you can),

@drmoeder

logread | grep -i route | less

@drmoeder hmmm not sure why this is not updating the routing table, perhaps someone else has an idea. But here is a workaround for you as I'm going to be offline for the next 24 hours so this will fix the issue for you.

Put this script in /etc/hotplug.d/iface/40-wwan-up-route:

#!/bin/sh
TARGET_INTERFACE="wwan"

logger -t route "Starting interface hotplug device: ${DEVICE} Action: ${ACTION} Interface: ${INTERFACE}"
if [ "$ACTION" = "ifup" -a "$INTERFACE" = "$TARGET_INTERFACE" ]; then
logger -t route "IFUP ${DEVICE}"
/sbin/ip route add default via 192.168.5.254 dev "${DEVICE}" >/dev/null

fi

This scripts runs whenever the interface comes up and adds the route. I just wrote this for you based on another of my scripts so give it a test and let me know how you go. As you can see it logs the activity so if you have any issues post those log entries.