I can’t get wireless bonding to work. This is link between two sites under my control, no internet connection - just private LAN for one corporation, “point to point”.
I’m able to achieve 25Mbit halfduplex with each radio currently running nstreme2, I would like to get 50Mbit halfduplex which would be shared to download or upload direction according to immediate need. Thus, one second I would like to see 40Mbit or so download (user receives mail with attachment), another second I would like to see 40Mbit upload (user sends mail with attachment). Current links are not symmetrically loaded, one direction is loaded far more than the other one and I would like to “strenghten up” the loaded one by providing more capacity.
Example : longterm averages are 10Mbit/s download ; 23Mbit upload. The latter one is almost everytime full and people are experiencing slowness.
I saw somewhere that bonding should be done with WDS (not bridge or AP/station modes).
Can anyone provide working examples of wireless bonding? Version used is 2.9.19. Please don’t post links to manual.
Eugene you mean, that WLAN1, WLAN2 both go into bridge, WDS static is made. Then we bond the WDS1 and WDS2. Should we also put the bond interface into the bridge? WHat about ether1 interface? Correct me please:
WLAN1, WLAN2, Ether1 and Bond1 all go into bridge!!!
This configuration must be done also in the 2 routers? (“Once you have done all the above, put WDS1 and WDS2 as bonding slaves”)
The 2 first’s router wireless interfaces must be in bridge mode.
The 2 second’s router wireless interfaces must be again in bridge or station mode?
Can i have connection with bridge-bridge mode?
Gaougalos,
yes, configuration related to both routers.
W1, W2 - router1 wireless interfaces;
W3, W4 - router2 wireless interfaces;
a) set mode=bridge for W1,W2,W3,W4 interfaces;
b) establish WDS link between W1 and W3, respectively W2 and W4.
WDS allows to establish communication between bridge<–>bridge routers.
c) put W1 and W2 wds interfaces as ‘interface bonding’ slaves, the same on router two W3 and W4 WDS interface as bondging slaves.
wireless bonding does NOT work correctly at all. This is not fault of mikrotik, it’s problem of hardware layer, etc. too many things influence quality of tcp/ip bonding on wireless…
btw, it’s reported that ethernet bonding works and works OK exactly as expected. But not with mikrotik…
forget the idea of wireless bonding, rent a fiber. We have spent so much time with this… even Eugene’s example of super-trooper 310Mbit wireless throughput shows you big traces of instable throughput for download/upload channels. And that was on table in room, not on roof competing with other subjects for RF band.
wireless bonding does NOT work correctly at all. This is not fault of mikrotik, it’s problem of hardware layer, etc. too many things influence quality of tcp/ip bonding on wireless… forget the idea of wireless bonding, rent a fiber.
What about bonding a WDS interface and an ethernet interface? We are bridging several MTs using 802.11a radios to create a rudimentary mesh, sharing one MT’s ethernet feed. We would like to be able to connect ethernet to others, where available, both to offload traffic from the mesh, and to provide some amount of fail-over. Insights welcome.
abc123 -
What I found that seems to work - and ChangeIP might jump in on this as well, is look at what rate the wireless connections will connect at consistently…then set the rate for one below that in the configured rate tab. I also include the one just below that as well as the basic 6mbps (802.11a). Like this - the radios connect at 54mbps, set your configured rates at 48mbps, 36mbps and basic the 6mbps. One other thing I do - use the simple queue and set the rate per interface about 10% lower than the upper rate 48mbps - 10% = 43mbps. This gives the interfaces some ‘head room’ when working at the maximum speed to receive acks, etc across the wireless link.
Also a trick that ChangeIP uses frequently is to set in firewall / nat;
dst-address is one of your wireless IP addresses, so you have to set one for each interface IP in the RB, since you have two cards there would be two entires like this in each router. This sets up and maintains a route table entry for the IPs in question along with the associated interface. Most helpful in maintaing ‘order’ in the router…
The dst-nat creates and maintains the correct address / gateway relationship in the routing table of the router.
For some reason certain packets/datagrams /whatever you want to call them, end up going out the wrong gateway. When using this ‘hint’ that issue disappears.
I could go in to some of the workings of routing - but that is something you need to learn if you are going to get deeper in to why something works this way or that way. See the references Mikotik has provided…
