12,270
edits
Category:FireBrick USB Dongles: Difference between revisions
Category:FireBrick USB Dongles (view source)
Revision as of 10:06, 4 November 2019
, 4 November 2019no edit summary
mNo edit summary |
mNo edit summary |
||
| (41 intermediate revisions by 4 users not shown) | |||
|
<indicator name="FireBrick">[[File:
[[File:Zoom_Dongle_Small.png]]
== Note - installing a dongle ==
=3G Fallback=▼
=== Inserting a SIM into a dongle ===
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).▼
To insert a SIM into a Huawei 3G dongle, for example, you will need to have a large-size SIM, so do not pop out a small-size SIM from its enclosing card. You remove a SIM-carrier tray from the dongle, fit the SIM into the tray and reinsert it into the dongle.
==Supported 3G Dongles==▼
▲=3G/4G Fallback=
▲The 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]] (Discontinued)
*Huawei E353 (Three branding)
*Huawei E170 (BT Branding)
*Huawei E1752Cu (O2 Branding)
*ZTE MF112 (Three branding)
*[http://www.solwise.co.uk/3g-dongle-lp1917e.html Solwise NET-3G-LP1917E] (Discontinued)
==
*[[FireBrick 2700 with 4G ZTE MF823|ZTE 823]] (O2 branding, or direct from Amazon etc work) — this dongle appears to work "out of the box" for failover, but needs [[FireBrick 2700 with 4G ZTE MF823|specific configuration]] if you want to route your IP blocks through it. The FireBrick will get an IP address via DHCP from the dongle, eg 192.168.8.100
*Huawei E3372 - cheaper than the ZTE MF823, available from Amazon and others. In ethernet mode (its default) it works with a factory FireBrick configuration once a USB Interface has been added. The FireBrick will get an IP address via DHCP from the dongle, eg 192.168.8.100 - '''If using an A&A SIM, be sure to set the APN in the dongle, ie via http://192.168.8.1 - Settings - Profile Management - New Profile.''' (Re-tested November 2019)
*Huawei E3272 LTE Surf-Stick (Still Testing)▼
*Huawei E3276S-920 (Still Testing)▼
===Interface for 4G Dongles===
==A Note on Bonding 3G SIMs==▼
A 4G dongle will usually work as an ethernet device, and so the FireBrick will need an interface on the IUSB port, set as a DHCP client. If your config doesn't have an Interface already, then add one such as:
Multiple USB Dongles 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.▼
<interface name="Dongle" port="USB" graph="Dongle">
<subnet name="DHCP Client" nat="true" comment="Dongle"/>
</interface>
==Unknown or not yet working==
*Alcatel One-touch L850
*Alcatel One-Touch 800 (Does not work, seems to only support RNDIS Interface which FireBrick does not support)
Many 4G LTE dongles work by acting as an Ethernet device and perform NAT between the mobile network and the interface presented to the FireBrick. These types of dongles should work OK. If your A&A IP blocks need to be routed to the FireBrick whilst on 4G then using L2TP would be a way to achieve this. We’ll be expanding this section with more details and information as we test further dongles.
▲==A Note on Bonding 3G and 4G LTE SIMs==
▲Multiple USB
▲Using multiple dongles with SIMs from different providers may provide extra resilience in the case of one having a problem.
=Basic Config=
The example below is 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.
<syntaxhighlight lang="xml">
<usb>
<dongle username="me@a.2" password="secret"/>
</usb>
</syntaxhighlight>
=Tunneled IPv6 Fallback=
==Example Config==
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1500):
<syntaxhighlight lang="xml">
<interface name="LAN" port="LAN" ra-client="false">
<subnet ip="2001:8b0::1/64 10.0.0.1/24" ra="true" ra-mtu="1480" ra-dns="2001:8b0::2020 2001:8b0::2021"/>
</syntaxhighlight>
LAN Interface for IPv6 tunnel over 3G dongle (with MTU 1492):
<syntaxhighlight lang="xml">
<interface name="LAN" port="LAN" ra-client="false">
<subnet ip="2001:8b0::1/64 10.0.0.1/24" ra="true" ra-mtu="1472" ra-dns="2001:8b0::2020 2001:8b0::2021"/>
</syntaxhighlight>
Connect to AAISP over PPPoE session (3G dongle tweaks and NAT):
<syntaxhighlight lang="xml">
<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):
<syntaxhighlight lang="xml">
<dongle name="AAISP-3G" username="me@a.2" password="secret" nat="true" graph="AAISP-3G" log="default"/>
</syntaxhighlight>
3G dongle IPv6 default route using IPv4 tunnel:
<syntaxhighlight lang="xml">
<route ip="::/0" gateway="81.187.81.6" comment="IPv6 default route using IPv4 tunnel"/>
</syntaxhighlight>
=== Configuration and testing ===
When you plug a usb dongle into the Firebrick, to test if it is working you can use the CLI ‘<code>show dongle</code>’ command in a [https://en.wikipedia.org/wiki/Telnet Telnet] session. However, unfortunately this command fails to detect the dongle if <usb> and <dongle> elements have not been added to the XML configuration file. You can at first just add the following to the XML by using the web UI of the Firebrick, under Config > XML Edit:
<usb>
<dongle name="AA" />
</usb>
If you prefer not edit the XML, then you can make the change by using the web UI commands Config > Edit choose ‘Interface’ and then ‘USB and 3G/dongle settings’. Drill down until you see whole lot of options in a number of ‘3G/dongle config settings’ fields. Set the option fields appropriately, at a minimum fill in the ‘Name’ field, and then hit ‘Save’. This will add the <code><usb></code> and <code><dongle></code> elements for you in the XML configuration.
Following the application of either of these two alternative methods, the CLI ‘<code>show dongle</code>’ command will now work and will detect the presence of the dongle. You will need to fit an appropriate SIM into the dongle. The result will be something like the following:
With no SIM:
> show dongle
Attached USB devices
--------------------
Socket Vendor Product Name Functions
1 12d1 1003/1003 AA 3G(AT-ppp)
You do not have any 3G/ppp sessions
You do not have any 4G/eth sessions
And with a 3G SIM installed:
> show dongle
Attached USB devices
--------------------
Socket Vendor Product Name Functions
1 12d1 1003/1003 Dongle-AA Memory-stick 3G(AT-ppp)
3G/PPP Dongle Sessions
----------------------
Socket T Name MTU Status
1 0 Dongle-AA 1440 Up tcp-fix
You do not have any 4G/eth sessions
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 <code><usb></code> and <code><dongle></code> elements can be conditional, based on profiles.
Leaving <code><usb></code> active but disabling <code><dongle></code> will leave the dongle powered up but disconnected.
Disabling <code><usb></code> will physically turn off the USB port and therefore also the dongle.
Cold starts take a lot longer!
<syntaxhighlight lang="xml">
<usb>
<dongle name="AAISP-3G" username="me@a.3" password="secret" graph="AAISP-3G" profile="AAISP-3G"/>
This example is taken from a site which has 2 ADSL lines - hence the No-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.
=Ping test example of falling back=
You can tell when the swap over happened as the latency increases and then decreases again when the DSL came back online.
=Telnet Commands=
<pre>show dongle</pre>
[[Category:FireBrick]]
| |||