User:Stuarth/sandbox: Difference between revisions
Content deleted Content added
Created page with "'''Firebrick Failover''' '''AIM:''' To provide a seamless fail-over from one wan to another, on a firebrick using an AAISP internet service and another Internet service. '''Description:''' If your AAISP Internet connection should fail for any reason, perhaps damage to cabling etc., and you have the benefit of another route to the internet, then your connection to AAISP can remain connected. '''Firebrick features used:''' * Interfaces: To connect another Internet sou..." |
No edit summary |
||
| Line 21: | Line 21: | ||
Assuming you have already successfully connected your Firebrick to the Internet, you will want to connect the Starlink to the Firebrick. This can be achieved by simply dedicating a port and interface as a direct connection to the Starlink router. The important thing to note is tables. The Firebrick by default uses Tables of ‘0’ for routing and ‘0’ for payload. As we only want the Starlink connection to take over when the FTTP fails we will pick another routing table, in this case ‘10’ |
Assuming you have already successfully connected your Firebrick to the Internet, you will want to connect the Starlink to the Firebrick. This can be achieved by simply dedicating a port and interface as a direct connection to the Starlink router. The important thing to note is tables. The Firebrick by default uses Tables of ‘0’ for routing and ‘0’ for payload. As we only want the Starlink connection to take over when the FTTP fails we will pick another routing table, in this case ‘10’ |
||
[[File:Image1.png| |
[[File:Image1.png|955x490px]] |
||
Note there is also a subnet created simply to collect an IP address from the Starlink Router, as ‘DHCP-client’. |
Note there is also a subnet created simply to collect an IP address from the Starlink Router, as ‘DHCP-client’. |
||