FireBrick How to: Upload Route Overrides: Difference between revisions
Content deleted Content added
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<indicator name="Howto">[[File:Menu-question.svg|link=:Category:FireBrick How to|30px|Back up to the FireBrick How to Category]]</indicator> |
|||
==Scenario== |
==Scenario== |
||
You are bonding multiple lines up and down, but you want some particular device to only send traffic up a single line rather than bonding the upload. This is also assuming that you're using an AAISP (or similar) service where traffic to you is being bonded by the ISP over all the circuits. |
You are bonding multiple lines up and down, but you want some particular device to only send traffic up a single line rather than bonding the upload. This is also assuming that you're using an AAISP (or similar) service where traffic to you is being bonded by the ISP over all the circuits. |
||
| Line 12: | Line 14: | ||
It's easier to manage the config if we create an IP Group for the device(s) that we want to use line 3 for their upload. |
It's easier to manage the config if we create an IP Group for the device(s) that we want to use line 3 for their upload. |
||
<syntaxhighlight lang=xml> |
|||
<ip-group name="phones" ip="192.0.2.99" comment="IPs here are phones, this is used in route overrides"/> |
<ip-group name="phones" ip="192.0.2.99" comment="IPs here are phones, this is used in route overrides"/> |
||
</syntaxhighlight> |
|||
===Profile=== |
===Profile=== |
||
We want to only override the route if the DSL line is up, so lets create a profile for this: (our line 3 is called ADSL3) |
We want to only override the route if the DSL line is up, so lets create a profile for this: (our line 3 is called ADSL3) |
||
<syntaxhighlight lang=xml> |
|||
<profile name="ADSL3" ppp="ADSL3"/> |
<profile name="ADSL3" ppp="ADSL3"/> |
||
</syntaxhighlight> |
|||
===PPP Changes=== |
===PPP Changes=== |
||
We need to tell the FireBrick a couple of things regarding the config for Line three's PPP: |
We need to tell the FireBrick a couple of things regarding the config for Line three's PPP: |
||
*Use the line as a lower priority (localpref) - that way all other traffic won't be using it |
*Use the line as a lower priority (localpref) - that way all other traffic won't be using it |
||
*Add an IP to the 'Routes' as this is what we'll use as the gateway in the override |
*Add an (arbitrary) IP to the 'Routes' as this is what we'll use as the gateway in the override |
||
e.g.: |
|||
eg: |
|||
<syntaxhighlight lang=xml> |
|||
<ppp name="WAN3" port="WAN" username="example@a.3" password="secret" speed="300000" lcp-rate="1" lcp-timeout="10" routes="0.0.0. |
<ppp name="WAN3" port="WAN" username="example@a.3" password="secret" speed="300000" lcp-rate="1" lcp-timeout="10" routes="0.0.0.3" localpref="50" graph="Line 3" comment="Used for VOIP upload hence localpref and route"/> |
||
</syntaxhighlight> |
|||
===Route override=== |
===Route override=== |
||
This is where the routing logic happens. If the line is up then send traffic from the phone IP group to line 3 |
This is where the routing logic happens. If the line is up then send traffic from the phone IP group to line 3 |
||
<syntaxhighlight lang=xml> |
|||
<route-override name="VoIP |
<route-override name="VoIP" comment="Send VoIP up line 3"> |
||
<rule source-ip="phones" set-gateway="0.0.0.3"/> |
<rule source-ip="phones" set-gateway="0.0.0.3" profile="ADSL3"/> |
||
</route-override> |
</route-override> |
||
</syntaxhighlight> |
|||
==The Result== |
==The Result== |
||
| Line 39: | Line 49: | ||
*If line 3 goes down, then everything is bonded over the remaining lines |
*If line 3 goes down, then everything is bonded over the remaining lines |
||
Once the config is applied, give it a while and watch the graphs - you should see upload traffic on line 3 only when making VoIP calls... |
|||
| ⚫ | |||
| ⚫ | |||