Hello all,
What is the best setup in Mikrotik for making long distance P2P links, if I want to use static routes ?
Can it be done with normal station - AP link or should I use WDS or NStreame ?
I left ACK timeout at dynamic, and it works out of the box.Don't forget to set ack-timeout depend on the distance
I placed a 20 mile link between my place of work and my house, but since my company has a strict routing policies in internal subnet, I need to set up a static route.
Since I know that I cannot bridge AP-station link due to 802.11 MAC problems, I was wondering if routing is affected by that same problem.
I.E. should I use a WDS or Nstreame or will it work with normal AP-station link.
1) Nstreme protocol is designed to achieve better performance over long range wireless links .
2) If you want to create transparent network between both routers, you have to use WDS. (WDS cannot be used together with Dual Nstreme, but you are able to use WDS together with Nstreme. Use structure AP -- station-wds for your wireless routers.
2) If you want to create transparent network between both routers, you have to use WDS. (WDS cannot be used together with Dual Nstreme, but you are able to use WDS together with Nstreme. Use structure AP -- station-wds for your wireless routers.
-
-
joeri91942
Frequent Visitor
- Posts: 88
- Joined:
- Location: Sundsvall, Sweden
Now could someone please explain to me why one would use WDS to create a transparent link over a long distance???
A long distance link would have limited bandwith, medium to high latency and generally be "thinner" then the local networks on both sides.. if you're using M$ networking (as I assume you are using) on both sides then this link would have to carry a lot of name resolution lookups, server announcents, name broadcasts etc..... since all local traffic would be "local" over all of the networks... right?
Add a broadcast storm to this and you're out of business!
Wouldn't it be better to create a proper, subnetted, routed IP network instead? That's the way we've been doing backhaul links and I've had almost no problems with mine.....
/Jörgen
A long distance link would have limited bandwith, medium to high latency and generally be "thinner" then the local networks on both sides.. if you're using M$ networking (as I assume you are using) on both sides then this link would have to carry a lot of name resolution lookups, server announcents, name broadcasts etc..... since all local traffic would be "local" over all of the networks... right?
Add a broadcast storm to this and you're out of business!
Wouldn't it be better to create a proper, subnetted, routed IP network instead? That's the way we've been doing backhaul links and I've had almost no problems with mine.....
/Jörgen
-
-
joeri91942
Frequent Visitor
- Posts: 88
- Joined:
- Location: Sundsvall, Sweden
I have had some slight problems with links bouncing up and down on link speed and getting varying ping times, resulting in lost packets and communication problems... specifically VoIP is cranky when the packet latency fluctuates! hello (hello... hello.... ) echos are a prime symptom on that
got that mostly taken care of by
- using nstreme
- reducing the allowed max transmit speeds, usually I set them to max 24Mb
- reducing! transmit powers... have no real explanation on this but in real life it has helped
/Jörgen
got that mostly taken care of by
- using nstreme
- reducing the allowed max transmit speeds, usually I set them to max 24Mb
- reducing! transmit powers... have no real explanation on this but in real life it has helped
/Jörgen
I do want to route this link.Jörgen, I agree with you, routing is another way to realize scenario. And which one to choose depends on scenario requirements.
Bridge is out of the question.
I only need to know if routing will work over AP-station connection or I have to use WDS or Nstreame to create background for routed subnets.
(I.E. does 802.11 limitations affect routed subnets in the same way as they affect bridging ?)
Yes, 'routing' has to work without any problems and withoud WDS.
Thank you guys for fast answersYes, routing work well with AP-station setting... no problems on 60 wireless routers Smile
Nstream may help with increasing throughput on line... but it need enough CPU power on fast lines... Wink
. Another question: If I choose to do it via standard AP-station link, does it matter from which side is default gateway located ?
I ask because I remember that when I used P2P link with two Ovislink 1120 AP-s (one at WISP I connected to and one at my home) to connect to the internet, internet could not work if the default gw was at the station side of that link. (I.E. it had to be at the AP side)
Who is online
Users browsing this forum: No registered users and 6 guests