Wifi mesh network on the cheap

sorry im new to this, i meant that a given device will always connect to the strongest access point (cant find to terminology for it)

No worries -- how a client chooses what to connect to is pretty much up to the client, "normal" 802.11, mesh, or whatever.

An Access Point (AP) can "kick" a client, but it still may try to reconnect.

My wireless devices connect to APs that are connected together with a mesh. As such, they never "see" the mesh at all. I don't know of any phone, tablet, laptop, or the like that is "mesh enabled" without adding additional software, if it is even available.

please point me in the right direction, recently i set up on a friend house 2 consumer grade router running ddwrt one as main/ gateway and the other one in bridge mode, only issue is that 30 minutes later he told me that the internet on the computer that is connected to the second router (Ethernet port) is unreliable. so at this point i would like to learn what to do not only to to do in my house but to help my friend as well

It sounds like you've got something like:

ISP <---> modem <---> router 1 <~~~~> router 2 <---> computer

where the link between the two routers is wireless. Most reliable would be a cable, next most reliable a power-line modem.

WDS is not a "real" standard, so I'd suggest running both routers on the same firmware if you're going to try that. For two devices, a station-client connection and GRE tunneling or even batman-adv would work out OK as well. You don't need a "mesh" unless you've got three or more nodes.

One reference for WDS is https://openwrt.org/docs/guide-user/network/wifi/atheroswds (be aware that Broadcom chips may/will not support WDS the same way as Qualcomm/Atheros chios).

1 Like

u lost me, because for what i have read WDS will cut bandwidth on half

It doesn't matter what technology you use, if you're sharing the radio, the bandwidth will be cut in at least half -- x ms to receive a packet, another x ms to transmit it to the other end. If you put clients on one band and the backhaul on the other, then you don't lose the bandwidth (just increase the latency).

2 Likes

ok so should i go for 802.11s or B.A.T.M.A.N. ?

A mesh network establishes a wireless interconnection among the access points. Performance is better with a wired or other out of band connection, but of course that has higher installation costs and is not practical in many situations.

The interlink of access points is so that users of any AP can reach the Internet. It doesn't have anything to do with how the user devices connect to their access point. Ways to steer users to the best AP for them is an entirely different area of study.

BATMANadv is a routing system which automatically figures out which nodes can link to each other directly and which need to relay traffic. It is an under layer to a radio system. Previously it was common to use adhoc mode as the radio layer. The 802.11s standard includes both a radio layer and a routing layer. The routing in 802.11s is very basic but is fine for a network of only a few nodes.

Lately most commercial and free projects have moved to using only the radio layer of 802.11s with the 802.11s routing disabled, then linking this radio to BATMAN. BATMAN does several things that internal 802.11s routing cannot, for example it can encapsulate VLAN tags in the packets.

2 Likes

all im trying to do is something like google wifi and similiar but on the cheap, i have my ayes in https://qmp.cat/Documentation and https://libremesh.org, but i dont know how to start. what do you think?

If you can live without the self-organizing features of real mesh networks, plain WDS/4addr might be the easiest option - this does however require that you can configure a static binding between each of your APs (and don't move them too often). This approach requires more effort while configuring, but is simple and compatible with all clients (the requirement to run OpenWrt on all involved APs is shared with mesh implementations as well).

1 Like

running openwrt on the router (ap) are not an issue, so what steps should i do next ?

wiki: atheroswds, as already posted by jeff - if possible, try to keep the branches short (as in ideally connect all APs to your main router, as each extension limits the throughput further; a good mesh can profit from multiple uplink routes, WDS/ 4addr can not - but that's often (unless the area gets too large) not needed/ won't help much).

what about this https://qmp.cat/Documentation and do u have and user friendly guide or video i can follow?

I'm not sure why you keep pointing to reasonably complex mesh schemes.

  • Do you have more than two routers in either of your installations?
  • Do you have or intend to have multiple VLANs or an isolated "guest" or "IoT" network?
  • Does one or more of your routers use Broadcom wireless chips?

Unless the answer to at least one of those is "yes", WDS is likely the first approach to try.

As stated before, unless you've got three or more nodes, "mesh" technologies don't provide any advantage over point-to-point technologies.

4 Likes

never mind jeff, i will be playing with it by myself, and if that does not work i will just run an Ethernet cable trough the attic to that room, thank you for not helping at all.

All you need is https://openwrt.org/docs/guide-user/network/wifi/atheroswds
All you ever needed was WDS.

You should use routers with 2 wifi chips so the WDS link and client AP don't use the same radio.

1 Like

i dont know how to do this in cli

Repeater effect (what @weedy (or me, when recommending against daisy-chaining multiple WDS-APs behind each other) is referring to, the slowdown that happens for clients connected to your repeater if its wlan card is shared for both the uplink to the main AP and as its own AP for clients nearby) exists and is real, but most of the time not a real problem (even less if your 5 GHz/ HT40 signal is strong enough to be used for the uplink) - usually you win more by providing dual-band AP services than you lose to the repeater effect (yes, triple-radio APs would be the ideal solution here, but those are rare and expensive - and sometimes perfectionism is the enemy of "good enough").

1 Like

This can be done in the GUI. Set your main AP to Access Point (WDS) mode. This works like a standard AP except it also allows WDS connections. Then set the repeater AP to Client (WDS) mode and specify the SSID of the AP. Place this WDS client in the LAN network.

If you have simple Internet users as the end users, that don't need a seamless LAN network (e.g. sharing a printer between rooms), or incoming traffic from the Internet, you could have the repeater APs do local routing. Then regular AP-client links can be used without WDS.

2 Likes

does wds support wifi roaming ?