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

m
Tags: Mobile edit Mobile web edit
(31 intermediate revisions by 3 users not shown)
#REDIRECT [[:Category:FireBrick_USB_Dongles]]
 
[[File:2700-small.png|link=:Category:FireBrick]]
[[File:Zoom_Dongle_Small.png]]
 
[[File:Zoom4598.jpg|right]]
=3G Fallback=
The 2700 model has a usbUSB 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==
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_dongleZoom USB dongle|ZOOM model 4598]] (Available from AAISP)
*Huawei E353 (Three branding)
*Huawei E170 (BT Branding)
 
==A Note on Bonding 3G SIMs==
Multiple USB Donglesdongles can used via a USB hub - however the benefits of bonding multiple 3G are small, as you'll typically be contending with yourself and so there will be little or no added bandwidth.
Using multiple dongles with SIMs from different providers may provide extra resilience in the case of one having a problem.
 
=Basic 3G Config=
If you have an AAISP data SIM, the FireBrick can be configured to use this as a backup connection, by using a 3G dongle plugged into the USB port. Any routed legacy IPv4 blocks will continue to work across this link, but so far IPv6 isn't supported (without using a tunnel).
ProvidedThe youexample usebelow your AAISP username and password, then that'sis all you need to get the dongle configured. If your main broadband connection goes down, the FireBrick will automatically switch to use the 3G connection, then back again once your main connection is back.
 
The basic config is:
<syntaxhighlight>
<usb>
<dongle username="me@a.32" password="secret"/>
</usb>
</syntaxhighlight>
 
Provided you use your AAISP username and password, then that's all you need to get the dongle configured. If your main broadband connection goes down, the FireBrick will automatically switch to use the 3G connection, then back again once your main connection is back.
 
== Config with Tunneled IPv6 Fallback==
If the dongle is not using an AAISP SIM, and therefore your IPv4 blocks won't be re-routed down the dongle, then include NAT="true" on the dongle line.
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 (iei.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]].
 
==Example Config==
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1500):
<syntaxhighlight>
<interface name="WANLAN" port="WANLAN" ra-client="false"/>
<usb>
<subnet ip="2001:8b0::1/64 10.0.0.1/24" ra="true" ra-mtu="1480" ra-dns="2001:8b0::2020 2001:8b0::2021"/>
<dongle username="me@a.3" password="secret" nat="true"/>
</usbinterface>
</syntaxhighlight>
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1492):
 
== 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.
 
Here we have an example config, with default logging. Please make changes to suit your FireBrick setup. If your MTU is 1492 then use ra-mtu="1472" instead of ra-mtu="1480".
 
<syntaxhighlight>
<interface name="LAN" port="LAN" ra-client="false">
<subnet ip="2001:8b0::1/64 10.0.0.1/24" ra="true" ra-other="dhcpv6" ra-mtu="14801472" ra-dns="2001:8b0::2020 2001:8b0::2021"/>
</interface>
</syntaxhighlight>
 
Connect to AAISP over PPPoE session (3G dongle tweaks and NAT):
<interface name="WAN" port="WAN" ra-client="false"/>
<syntaxhighlight>
 
<ppp name="AAISP" port="WAN" username="me@a.1" password="secret" nat="true" lcp-rate="1" lcp-timeout="5" graph="AAISP" log="default"/>
</syntaxhighlight>
 
Connect to AAISP over 3G dongle (with NAT):
<usb>
<syntaxhighlight>
<dongle name="AAISP-BACKUP" apn="m2m.aql.net" username="me@a.3" password="secret" nat="false" graph="AAISP-BACKUP" log="default"/>
<dongle name="AAISP-3G" username="me@a.32" password="secret" nat="true" graph="AAISP-3G" log="default"/>
</usb>
</syntaxhighlight>
 
3G dongle IPv6 default route using IPv4 tunnel:
<syntaxhighlight>
<route ip="::/0" gateway="81.187.81.6" comment="IPv6 default route using IPv4 tunnel"/>
</syntaxhighlight>
 
 
= 3G profiles - turningTurning the dongle off outside of office hours=
Sometimes we don't want the dongle to be online 24x7 and want it turned off outside of office hours.
This example brings the dongle online for quick fallback during office hours, and leaves it powered up but disconnected.
 
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.
 
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!
Disabling <usb> will physically turn off the USB port and therefore also the dongle.
Cold starts take a lot longer!
 
<syntaxhighlight>
<usb>
<dongle name="AAISP-3G" username="me@a.3" password="secret" nat="false" graph="AAISP-3G" profile="AAISP-3G"/>
</usb>
 
<profile name="Office_HoursOffice-Hours" comment="Office hours">
<time days="Mon Tue Wed Thu Fri" start="08:00:00" stop="18:00:00"/>
</profile>
 
<profile name="No_DSLNo-DSL" ppp="ADSL1 ADSL2" invert="true"/>
<profile name="AAISP-3G" or="Office_HoursOffice-Hours No_DSLNo-DSL" comment="Backup active during office hours, or if there is no DSL outside of office hours"/>
</syntaxhighlight>
 
This example is taken from a site which has 2 ADSL lines - hence the No_DSLNo-DSL profile being based on ADSL1 and ADSL2 being up.
The AAISP-3G profile is then active during office hours, but it will become active if both of the ADSL lines are down outside of office hours.
 
The 3G profile is then active during office hours, but it will become active if both of the ADSL lines are down outside of office hours.
 
= Ping test example of falling back =
 
Here we ping an IP on the LAN, behind the FB2700, and get the ADSL router to re-sync. The ADSL went down, the 3G kicked in with only a single ping lost, then shortly after the ADSL came back on and took over the routing again.
</pre>
 
You can tell when the swap over happened as the latency increases and then decreases again when the DSL came back online.
 
= Telnet Commands =
 
= Telnet Commands =
 
Will resetReset the usbUSB controller and re-detect everything from scratch.:
<pre>clear usb</pre>
Will reset the usb controller and re-detect everything from scratch.
 
 
Show dongle information:
<pre>show dongle</pre>
To show info
 
 
You can turn on debug logging to get more info
 
<pre>set command log level debug</pre>
-there will be lots of info coming out!
 
 
[[Category:3GData RouterSIM Devices]]
[[Category:FireBrick]] [[Category:3G]] [[Category:Mobile]]
[[Category:3G Router]]
252

edits