Hi.
We want to get 100mbps internet connection from site1 over site2 to site3.
For latency, redundancy and speeds sake we want to use 2x rocketm5 dishes on a rb1200 and bond the 2x lan interfaces.
If i understand correctly it can be problematic due to tcp packets arriving out of order,https connections failing ect...
Will bonding 2x seperate eoip tunnels work better ?
This link will run our traffic between 2 data centres, and the hops will be 60km each
I have also tested 802.3ad bonding, seems that traffic only runs rx on ether1 and tx on ether2, failover works 100%.
Any advise or suggestions will be appreciated.
I would not like to take the radwin route at the end of the day.
Thank you
Re: 100mbps internet connection over bonded help needed
EoIP is pretty much GRE. GRE means just slapping on another header and sending the packet merrily its way - it doesn't do anything at all for preventing reordering of packets.
You say you need an Internet connection. Is that connection going to carry more than just one connection in a layer 4 definition of the word? Have you looked at the hash methods available for 802.3ad mode?
http://wiki.mikrotik.com/wiki/Manual:In ... escription
You say you need an Internet connection. Is that connection going to carry more than just one connection in a layer 4 definition of the word? Have you looked at the hash methods available for 802.3ad mode?
http://wiki.mikrotik.com/wiki/Manual:In ... escription
The default is layer 2, so if you have a routed link as a point to point, all frames have the source/destination MAC addresses of the two end points and only one path each way is chosen for all traffic. But if a whole bunch of other IP traffic is routing across that link setting the modes to layer-2-and-3 or layer-3-and-4 would hash based on IP addresses or TCP/UDP ports, which would balance traffic across both links. Each connection between two end points or in the same TCP/UDP connection would still only go across one line, but overall traffic would balance. Because each connection is always on one line, you also avoid any re-ordering issues.transmit-hash-policy (layer-2 | layer-2-and-3 | layer-3-and-4; Default: layer-2) Selects the transmit hash policy to use for slave selection in balance-xor and 802.3ad modes
layer-2 - Uses XOR of hardware MAC addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. This algorithm is 802.3ad compliant.
layer-2-and-3 - This policy uses a combination of layer2 and layer3 protocol information to generate the hash. Uses XOR of hardware MAC addresses and IP addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations. This algorithm is 802.3ad compliant.
layer-3-and-4 - This policy uses upper layer protocol information, when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. For fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This algorithm is not fully 802.3ad compliant.
Who is online
Users browsing this forum: No registered users and 17 guests