Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

Linux upload bonding using teql: Difference between revisions

← Older edit
Content deleted Content added
m Add category
AA-Andrew (talk | contribs)
autoreview, Bureaucrats, editor, Interface administrators, reviewer, Administrators
12,616 edits
mNo edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
<indicator name="Front">[[File:Menu-bonding.svg|link=:Category:Bonding|30px|Back up to the Bonding Page]]</indicator>

This is a simpler method of upload bonding than others, where you just want to round robin packets to the upstream, which is the normal case for AAISP.
This is a simpler method of upload bonding than others, where you just want to round robin packets to the upstream, which is the normal case for AAISP.

⚫
You may wish to add ppp3, etc. as pppd sometimes allocates a different number overriding the unit directive. There's no harm in having too many.


In /etc/ppp/ip-up.d place the following script:
In /etc/ppp/ip-up.d place the following script:
Line 15: Line 15:
ip -6 route replace default scope global dev teql0
ip -6 route replace default scope global dev teql0
</pre>
</pre>

⚫
You may wish to add ppp3, etc. as pppd sometimes allocates a different number overriding the unit directive. There's no harm in having too many.

The sysctl is so that the system doesn't get upset at packets going out of one interface and coming in another. I'm not certain this is required, but all examples seem to have it.

The teql device does not need an IP address, as it's virtual. It seems to behave in a sane way wrt. originating IP in all cases I've tried.


[[Category:3rd Party Routers]]
[[Category:3rd Party Routers]]
Retrieved from "http://support.aa.net.uk/Linux_upload_bonding_using_teql"