| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Support for adding a fwmark to an interface. It will make it possible to
use firewall to mark specific traffic for a specific ISP.
|
| |
|
|
| |
This is a shorthand of definig a host and bind it to interface
|
| |
|
|
| |
We should not use the uninitialized "value".
|
| |
|
|
| |
This will set the preference for the 'ip rule'
|
| |
|
|
|
|
|
| |
Add config option for executing actions when interface gateway goes
up/down.
Add config option for required hosts up per interface (defaults to 1)
|
| |
|
|
|
| |
We should not try load-balance at all if there are only 1 or less
interfaces configured with "load-balance"
|
| |
|
|
|
| |
Add a config option to tell pingu that we want the interface to be
load balanced. We also have an optional value to tell the weight.
|
| | |
|
| |
|
|
| |
and some whitespace fixes
|
|
|
New format allows users to define interfaces and ping hosts separately.
This means we can run pingu in routing-only mode to set up and manage
route tables for multi-isp.
We allow the user config a preferred alternate route table for each
interface. If not configured, pingu will pick one.
Example interface definition looks like:
interface eth0 {
route-table 10
}
Example host definition looks like:
host 192.168.0.1 {
bind-interface eth0
}
|
