hi everybody ,
I'm not English
my english not so good , excuse me
I'm going to buy a MikroTik router to set up bonding and tunneling ( eoip )
1. Is the router RB2011UiAS-IN does this work?
not crash?
2. For bonding and tunneling how much RAM and CPU do I need ?
3. What is your suggestion router ?
Total traffic is 120Mbps ( on EoIP - Bonding )
Bonding : ( ether 1 = 60 Mbps ) + ( ether 2 = 60 Mbps ) = 120Mbps
Thanks a lot
Re: EoIP + Bonding
My question is hard ?
Why does not anyone answer ?
Why does not anyone answer ?
Re: EoIP + Bonding
I think the biggest concern for you is going to involve two things:
average packet size
MTU / fragmentation issues.
small packets can bog the router's CPU down a lot more than large packets because ultimately, a router's capacity is measured in packets-per-second, not bytes per second.
All of the connection tracking, natting, firewalling, encapsulation, etc must happen in the same amount whether the packet's payload is 40 bytes or 9 kilobytes.
So you're getting a lot less bang for your buck cpu-wise if your traffic consists of lots of small packets (i.e. VoIP)
Bonding and encapsulating a bridge makes the CPU's job even harder.
Even worse is fragmentation/reassembly. If you are bridging a 1500-byte-MTU network, then the routers will be doing lots of this, because the encapsulated bridge packets become too large for the underlying network to carry intact. So the EoIP interfaces will just fragment the payload (even if it has the DF bit set in the IP header) when required. Reassembling the fragments also takes extra resources at the far end of the connection.
If your router is not doing any sort of bridge filtering, or IP filtering, and depending on the bonding tech you're using, you can get decent performance out of a 2011 with fastpath/fasttrack enabled. However, I'd say that you probably need something a bit more powerful than a 2011 for real-world performance in your planned network. Consider a lower-end CCR.
average packet size
MTU / fragmentation issues.
small packets can bog the router's CPU down a lot more than large packets because ultimately, a router's capacity is measured in packets-per-second, not bytes per second.
All of the connection tracking, natting, firewalling, encapsulation, etc must happen in the same amount whether the packet's payload is 40 bytes or 9 kilobytes.
So you're getting a lot less bang for your buck cpu-wise if your traffic consists of lots of small packets (i.e. VoIP)
Bonding and encapsulating a bridge makes the CPU's job even harder.
Even worse is fragmentation/reassembly. If you are bridging a 1500-byte-MTU network, then the routers will be doing lots of this, because the encapsulated bridge packets become too large for the underlying network to carry intact. So the EoIP interfaces will just fragment the payload (even if it has the DF bit set in the IP header) when required. Reassembling the fragments also takes extra resources at the far end of the connection.
If your router is not doing any sort of bridge filtering, or IP filtering, and depending on the bonding tech you're using, you can get decent performance out of a 2011 with fastpath/fasttrack enabled. However, I'd say that you probably need something a bit more powerful than a 2011 for real-world performance in your planned network. Consider a lower-end CCR.