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!

FireBrick 3G Dongle: Difference between revisions

Content deleted Content added
CrazyTeeka (talk | contribs)
mNo edit summary
Reedy (talk | contribs)
m clean up, typos fixed: ie → i.e. , usb → USB (5)
Line 3: Line 3:
[[File:Zoom4598.jpg|right]]
[[File:Zoom4598.jpg|right]]
=3G Fallback=
=3G Fallback=
The 2700 model has a usb port that can be used with a 3G dongle for connectivity and/or fallback. The FireBrick 2500 does not have a USB port. By using a 3G dongle with 1 or more FTTC/ADSL lines from AAISP you'll be able to fall back to using 3G in the case of the FTTC/ADSL going down - this includes routing of your public IPv4 blocks and IPv6 blocks (IPv6 via a tunnel)
The 2700 model has a USB port that can be used with a 3G dongle for connectivity and/or fallback. The FireBrick 2500 does not have a USB port. By using a 3G dongle with 1 or more FTTC/ADSL lines from AAISP you'll be able to fall back to using 3G in the case of the FTTC/ADSL going down - this includes routing of your public IPv4 blocks and IPv6 blocks (IPv6 via a tunnel)


==Supported Dongles==
==Supported Dongles==
Dongles do vary, and drivers may need to be written to support a particular dongle. Contact us if you have one which is not working. The following dongles are known to work on a FireBrick 2700:
Dongles do vary, and drivers may need to be written to support a particular dongle. Contact us if you have one which is not working. The following dongles are known to work on a FireBrick 2700:
*[[Zoom_USB_dongle|ZOOM model 4598]] (Available from AAISP)
*[[Zoom USB dongle|ZOOM model 4598]] (Available from AAISP)
*Huawei E353 (Three branding)
*Huawei E353 (Three branding)
*Huawei E170 (BT Branding)
*Huawei E170 (BT Branding)
Line 32: Line 32:


=Config with Tunneled IPv6 Fallback=
=Config with Tunneled IPv6 Fallback=
If using AAISP, then the options for IPv6 routing on the [[:Category:Control Pages|Control Pages]] allow an IPv6 block to be routed to a tunnel endpoint if the main routing (ie ADSL/FTTC) goes down. This means IPv6 can be routed to the 3G dongle if the main broadband(s) go down. The MTU will be limited though.
If using AAISP, then the options for IPv6 routing on the [[:Category:Control Pages|Control Pages]] allow an IPv6 block to be routed to a tunnel endpoint if the main routing (i.e. ADSL/FTTC) goes down. This means IPv6 can be routed to the 3G dongle if the main broadband(s) go down. The MTU will be limited though.


For more configuration options see [[FireBrick_2700_Configuration|FireBrick 2700 Configuration]].
For more configuration options see [[FireBrick 2700 Configuration]].
==Example Config==
==Example Config==
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1500):
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1500):
Line 67: Line 67:
This example brings the dongle online for quick fallback during office hours, and leaves it powered up but disconnected. Fallback still works outside of office hours but takes a few seconds longer to set up.
This example brings the dongle online for quick fallback during office hours, and leaves it powered up but disconnected. Fallback still works outside of office hours but takes a few seconds longer to set up.


Note that both <usb> and <dongle> elements can be based on profiles. Leaving <usb> active but disabling <dongle> will leave the dongle powered up but disconnected. Disabling <usb> will physically turn off the USB port and therefore also the dongle. Cold starts take a lot longer!
Note that both <USB> and <dongle> elements can be based on profiles. Leaving <USB> active but disabling <dongle> will leave the dongle powered up but disconnected. Disabling <USB> will physically turn off the USB port and therefore also the dongle. Cold starts take a lot longer!


<syntaxhighlight>
<syntaxhighlight>
Line 126: Line 126:
=Telnet Commands=
=Telnet Commands=


Will reset the usb controller and re-detect everything from scratch:
Will reset the USB controller and re-detect everything from scratch:
<pre>clear usb</pre>
<pre>clear usb</pre>