Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| ru:doc:howto:mwan3 [2018/03/03 19:45] – ↷ Links adapted because of a move operation | ru:doc:howto:mwan3 [2019/12/10 05:57] – [Mwan3 архитектура] vaha | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| * Связанные страницы: | * Связанные страницы: | ||
| - | * '' | + | * '' |
| ===== Последний релиз: ===== | ===== Последний релиз: ===== | ||
| Line 54: | Line 54: | ||
| * mwan3 реализует обычную для Linux политику балансирования трафика через несколько WAN, когда балансировка базируется на per-IP connection основе и это not channel-bonding, | * mwan3 реализует обычную для Linux политику балансирования трафика через несколько WAN, когда балансировка базируется на per-IP connection основе и это not channel-bonding, | ||
| - | * As such load-balancing will help speed multiple separate downloads or traffic generated from a group of source PCs all accessing different sites but it will not speed up a single download from one PC (unless the download is spread across multiple | + | * Такая балансировка нагрузки поможет ускорить несколько отдельных загрузок или трафик, |
| ==== Mwan3 архитектура ==== | ==== Mwan3 архитектура ==== | ||
| - | * Mwan3 is triggered by hotplug-events. When an interface comes up, it creates a custom routing table and iptables | + | * Mwan3 запускается событиями |
| - | * Once all the routes and rules are initially set up, mwan3 exits. The kernel takes care of all the routing decisions. If a new interface hotplug event occurs, mwan3 will run again to adjust route and tables as needed. | + | * Как только все маршруты и правила установлены, mwan3 завершает работу. Ядро берет на себя все решения по маршрутизации. Если происходит событие горячей замены нового интерфейса, mwan3 снова запустится, |
| - | * A monitoring script | + | * Сценарий мониторинга |
| ==== Mwan3 Роутинг==== | ==== Mwan3 Роутинг==== | ||
| Line 132: | Line 130: | ||
| * A TP-LINK TL-WR1043ND hardware version 1.10 router (ar71xx platform) ([[toh/ | * A TP-LINK TL-WR1043ND hardware version 1.10 router (ar71xx platform) ([[toh/ | ||
| * A TP-LINK TL-WDR3600 router (ar71xx platform) ([[toh/ | * A TP-LINK TL-WDR3600 router (ar71xx platform) ([[toh/ | ||
| - | * A openwrt 12.09 mips metarouter over a mikrotik r493g routeros 6.27 ([[inbox/doc/mikrotik_metarouter_openwrt]]). | + | * A openwrt 12.09 mips metarouter over a mikrotik r493g routeros 6.27 ([[docs: |
| * A NetGear WNDR3800 router (ar71xx platform) ([[toh/ | * A NetGear WNDR3800 router (ar71xx platform) ([[toh/ | ||
| Line 301: | Line 299: | ||
| * Reboot after making this change | * Reboot after making this change | ||
| - | * For more information, | + | * For more information, |
| ===== Ручная загрузка пакетов ===== | ===== Ручная загрузка пакетов ===== | ||
| Line 877: | Line 875: | ||
| * Related pages: | * Related pages: | ||
| - | * [[docs:user-guide: | + | * [[docs:guide-user: |
| === Example 1: Register the external IP of the active WAN interface === | === Example 1: Register the external IP of the active WAN interface === | ||
| Line 915: | Line 913: | ||
| * Related pages: | * Related pages: | ||
| - | * [[docs:user-guide: | + | * [[docs: |
| === Possible problems === | === Possible problems === | ||
| Line 996: | Line 994: | ||
| * Related pages: | * Related pages: | ||
| - | * [[docs:user-guide: | + | * [[docs: |
| Transparent HTTP proxying relies on using iptables rules to transparently redirect outgoing traffic to port 80 first through the local proxy at another port number. | Transparent HTTP proxying relies on using iptables rules to transparently redirect outgoing traffic to port 80 first through the local proxy at another port number. | ||