![]() Packet gets forwarded in fastpath but output interface does not support fastpath *) packets now can go half-fastpath - if input interface supports fastpath and On bridge interface can go fastpath (previously only bridge forwarded packets *) added fastpath support for bridge interfaces - packets received and transmitted *) added ~fasttrack-connection~ firewall action in filter/mangle tables for marking Path conntrack/nat) - currently limited to TCP/UDP only *) ipv4 fasttrack fastpath - accelerates connection tracking and nat for markedĬonnections (more than 5x performance improvement compared to regular slow *) snmp - fix rare bug when some OIDs where skipped *) firewall - fixed sector writes rising starting since 6.28 ![]() *) fasttrack - correctly close fasttrack connections With FastTrack - 460-500Mbps (full pipe) download with CPU 56-84%Īs i need queues and IPsec i switched back to CCR1009, but this opens lots of possibilities. Without FastTrack - 220-240Mbps download with CPU 100% I did some testing, on FastTrack, I have 500Mbps connection at the office, sitting on CCR1009, for a test purpose i replaced it with RB2011, and run some "linux distribution" torrent download this morning. So i expect that default configuration (from factory), will have it enabled by default. So with this FastTrack feature you "magically" make them much faster. I think you misunderstood me - RB75x, RB95x, RB2011, hAP, mAP, cAP - most common setups on these boards includes masquerade rule and some firewall filters. If the FS firewall and NAT is not necessary, tracking is better forcibly disable Basically it is fastpath solution when connection tracking is necessaryĬonnection tracking can operate without NAT, It is rather a function of the "Full State Firewall" It is not about filter rules, it is also about NAT. *) trafflow: add natted addrs/ports to ipv4 flow info. *) packets now can go half-fastpath - if input interface supports fastpath and packet gets forwarded in fastpath but output interface does not support fastpath or has interface queue other than only-hw-queue packet gets converted to slow path only at the dst interface transmit time *) added fastpath support for bridge interfaces - packets received and transmitted on bridge interface can go fastpath (previously only bridge forwarded packets could go fastpath) *) added ~fasttrack-connection~ firewall action in filter/mangle tables for marking connections as fasttrack *) ipv4 fasttrack fastpath - accelerates connection tracking and nat for marked connections (more than 5x performance improvement compared to regular slow path conntrack/nat) - currently limited to TCP/UDP only Easy way to make your Firewall/NAT router up to 5x faster. Starting from v6.29rc9, we introduced new and existing feature - FastTrack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |