ishanjain28

1. https://github.com/openwrt/openwrt/issues/9181

2. https://github.com/openwrt/openwrt/issues/9071

802.11k/v works well enough but the problem is when you are roaming the device is likely to see 2.4ghz network before it sees 5ghz network. Unless the manufacturers considered this scenario, the device will connect to 2.4ghz and remain connected to that instead of upgrading to higher bands. You need usteer in these situations.

You can also kind of patch this problem by setting beacon interval for 5/6ghz networks shorter than beacon interval for 2.4ghz network.

Also the problem with usteer is, they took the easy way out and do broadcast for syncing with other usteer instances instead of multicast so it's a lot of wasted bandwidth and it'll hit all the devices in that l2 segment.

802.11k/v/r on its own is not always sufficient for roaming specially if you have old clients on the network(5 years or older).

Almost every wifi solution like Omada or UI comes with additional heuristics based mechanisms to trigger roaming.

There are also bugs/missing features in 802.11r in openwrt. For example, it does not work if you are using 802.11w or Wifi 6

Also, during roaming it's supposed to do a shortened version of handshake for auth but right now it does a full 4 way handshake afaik or atleast that's what I see in the logs when a client switches to a different ap

1. For the last 6 months, there is a bug which causes ff to read incorrect display resolution information on Samsung devices. This breaks all elements positioned with absolute property and you can't see them or access them. The only fix is to restart firefox. Over time, it has literally gotten so much worse that now I have to do it atleast 10 times in a 30 minute session.

2. Have a site open, click on the nav bar to do a search or open another site and it just reloads the same site again! Redo the action and then it loads.

3. The networking stack is so so so bad I don't even know where to begin with that. It gets stuck randomly, slow loading pages, infinite loading animations just so many problems. There are also similar problems with graphics performance where sometimes, it literally runs at less than 60fps(you can feel it), consumes a lot more battery and heats up the processor. All these issues along side some of the design decisions they have made that they refuse to revert.

I do not feel good about Firefox fenix anymore

Right now, some ncmc card issuers allow validating the card using your phone so you don't have to go to the kiosk after topping up and they are working on letting people use their phones.

Took a little bit of effort tracking down the tab generating this traffic and now they are banned from my local network forever.

This is a mdns repeater for (primarily home) networks. The "recommended" way is to use use PIM/IGMP but you can not control the specific mdns names that'll be repeated over the vlan boundary. There are a few other repeaters but nothing that would've worked for me so I wrote this. It still needs a few improvements around caching responses. mdns enabled devices do known prefix suppression which some times causes problems.

Apple on the other hand unfortunately has nothing like that. If you want refund, You have to go through the hassle of creating a ticket and they may refuse to refund for whatever reason.

I am served IP addresses with relatively short TTLs (1-5minutes) that are in Moscow and North Holland.

In the demos I watched, There is account number and routing number