Posts made by crispyoz

@DocHardinger I'm currently travelling so haven't completed my testing since I don't carry a Windoze machine with me. However what I found thus far is that if I slow down iwinfo by ~200ms each probe, the windows machine does not disconnect.

The question I want to answer, is whether this tiny delay simply reduces the load on the Omega2p so it can respond to the network requests in a more timely manner. If this is the case, then my earlier hypothesis that windoze is simply less tolerant of response time variations than lesser systems, would appear to be true.

But I am not yet prepared to make that conclusion until I have done more testing, but if this were the case then we just create a patch to add this functionality.

@eng_Ahmed So this is where you need to do bit of hacking. Since both luci and OnionOS want to use the same directory, we need to backup the /www directory to some place else:

cd /
mv www www2

Which moves the current www directory and it's content to a new directory named www2.

Now force opkg to install luci, ignoring the perceived conflict:

opkg --force <luci package name>

Now you'll have both packages installed, you just need to configure lighttpd to find luci the www directory and OnionOS in the www2 directory.

One thing buzzing around in the back of my head is that I seem to recall (but may be wrong) there was some hardcoded /www references in the OnionOS stuff, so you may need to do the reverse and put OnionOS in /www and Luci in /www2. Just juggle them like this:

cd /
mv www www3
mv www2 www
mv www3 www2

Those directory names are abitrary, you could call them something like www_luci and www_onion you just have to tell lighttpd where to find them.

@eng_Ahmed Take a look in /etc/opkg/distfeeds.conf, I don't have one available to me right now but you can uncomment lines 2 and 5 and then run opkg update, then try installing again. Otherwise post your distfeeds.conf here so I can see. My internet is like a yoyo right now (thanks to the earthquake on Thursday) but I login when I can.

@Alberto-Brosich Try this configuration of network and wireless and tell me how you go ,just change only the client parameters (nothing secret in mine):

/etc/config/network:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'
        option disabled '0'

config globals 'globals'
        option ula_prefix 'fd80:3b06:c6c7::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'

config interface 'wlan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.3.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option disabled '0'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '0'

config interface 'wwan'
        option proto 'dhcp'
        option device 'apcli0'
        option disabled '0'

config  interface 'lan'
        option device 'eth0'
        option proto 'static'
        option netmask '255.255.255.0'
        option ipaddr '192.168.4.1'

/etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/10300000.wmac'
        option channel '11'
        option band '2g'
        option htmode 'HT20'
        option disabled '0'
        option country 'ID'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'wlan'
        option mode 'ap'
        option ssid 'dash'
        option encryption 'psk2'
        option key 'gnkdsjhfksfksgf;isyuf'
        option hidden '0'
        option disabled '1'

config wifi-iface 'client'
        option device 'radio0'
        option network 'wwan'
        option mode 'sta'
        option ssid 'MarriottBonvoy'
        option key ''
        option encryption 'none'
        option ifname 'apcli0'
        option disabled '0'
        option disassoc_low_ack '0'

@Alberto-Brosich your ssid key in your post is only 5 characters in both the sta and ap, perhaps you masked them out for the post, but if not then this will cause the issue ifup issue. Since you have selected psk2 encryption, your keys need to be between 8 and 63 characters.

@eng_Ahmed OnionOS OOTB uses Lighttpd as does Luci, so both can run on a bare bones web server. The main issue is how they can both coexist on the same server and how your browser request gets directed to the correct site.

I should note that I haven't tried this specific configuration, but I do use a multisite configuration on my devices, Lighttpd is amazingly functional for such a small footprint and includes conditional processing of requests.

Take a look at the configuration tutorial, you can see it is possible to create virtual hosts using the conditional url parsing.

@DocHardinger Here they are: OpenWrt Archive

@DocHardinger Oops yes you are correct. Let me see if any of the other slow mirrors I found previously have it. Otherwise we can always build it.

@Alberto-Brosich can you post the output of the command uci show network

@DocHardinger These are some of the reasons I build my own firmware

Their log indicates some issue with missing rust compiler.

Report the issue on openwrt forum, some of the devs haunt that place so you might get noticed, it's broken on 24.10 as well so it'll get some attention.

Here is a link to a mirror of the openwrt repo that seems to sync every few days, I just checked and the ipks you need are still there so you can grab them ASAP.

@DocHardinger It looks like those packages are not in the openwrt.org repos, I can see them in 22 but not in 23 or 24. If you look in your openwrt-imagebuilder-wrapper/openwrt-imagebuilder/repositories.conf you can see the openwrt repos.

@DocHardinger I believe I identified the cause yesterday, once I have finished testing I'll update the forum.

@eng_Ahmed While I'm happy to assist with specific issues if you get stuck, I finished doing homework about 25 years ago

The OpenWrt docs are pretty good these days, take a look the olsrd docs here, it includes a how to on setting up a mesh.

@shoresup Glad you got that sorted, sometimes it just needs a second pair of eyes. We've all been there.

Iperf is testing the max performance through the device, but file transfer utilities have several overheads, so for example if I use sftp, we have several steps:

1. read data chunk
2. encrypt data
3. transmit data
4. wait for ack
   repeat

sftp (for example) packet size can impact on performance, depending on your network driver (either wifi/ethernet et al), you may get better performance by tweaking -B parameter on sftp.

A simple test I use if ftp, because it removes the overhead of encryption/encoding of sftp. Actually I often use zmodem or modem for my test, maybe because I'm old

@DocHardinger I think I have a clue. I managed to reliably reproduce the issue on a Lenovo P15s notebook running windoze 10. It will reliably disconnect if I run iw ra0 scan in a loop on OpenWrt 23. So I ran Wireshark to check for lost packets, acks etc, nothing notable to report. However I did notice the Wifi signal strength kept dropping and then the SSID disappears. If I set the saved network to autoconnect, it reconnects fine. But as the loop runs it disconnects again and then reconnects etc. I put my iPhone and Android 11 devices next to the P15s at the same so they are the same distance from the Omage2p and neither of them disconnect when the windoze device disconnects.

This Lenovo P15s can dual boot either windoze 10 or Ubuntu 24.10, so this time I booted into Ubuntu and ran the same test, it doesn't disconnect. So the problem is isolated to windoze.

I ran LinSSID on Ubuntu and it does not detect any notable drop in signal strength, so I rebooted in windoze and ran Acrylic WiFi Analyser, it shows a short-lived drop in signal strength when I'm running iw ra0 scan in a loop.

My working hypothesis is that windoze is aggressively monitoring connectivity and the faster the machine the more likely it is to disconnect, but slower devices like iphones, android phones and old Surface devices are simply not noticing the short lived signal drop.

OpenWrt 22 uses iw v5.16 OpenWrt 23 uses iw v5.19, so I wondered if the newer iw is doing something different. Looking at the code the changes are minimal, so I installed iw v5.16 on OpenWrt 23 but the issue persists.

Both 22 and 23 use the same mt76 firmware release, so I'm looking at the driver code for some hints.

@eng_Ahmed I think everyone needs to use the approach that best aligns with their current experience and expertise. My approach would be to build the package from source and then install it on the devices. I think it's a slower start than simply installing the packages but by building from source to start with, you already have a leg up on task 3, you also can evaluate what each configuration change you make in stage 2 actually does at source code level. So by the time you are ready for stage 3 you already have an understanding of the code.

@ElGoose39 Take a look at the 23.05 documentation that has a detailed explanation on how to create your own repository. You could then remove the old version of python and install your own version. This documentation is relevant to the earlier Onion firmware 18.06 as well.

@eng_Ahmed ipip (ip tunnelling) needs the kmod which needs to be build for the kernel you are using. But since you are using oonf-olsrd2 package it doesn't have that dependency.

@shoresup you can isolate the file system as a performance bottleneck by running a test using dd. I create one file name myread containing:

#!/bin/sh

dd if=/dev/zero of=myfile bs=8k count=10000
sync

and another named mywrite containing:

#!/bin/sh

dd of=/dev/zero if=myfile bs=8k count=10000
sync

Now run these commands to see their timings:

time -v sh myread
time -v sh mywrite

This will give you the file system timings for reading and writing 10000 blocks to and fro the file system

There are other tools but I like dd because it's a really basic test

@DocHardinger Can you set option disassoc_low_ack '0' on your AP and see if it makes any difference. I need it on my sta when connecting to one of Unifi APs.