This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| user_guide:mobile_support [2016/10/12 10:47] – [Introduction] admin | user_guide:mobile_support [2016/10/12 14:54] (current) – [3G / Mobile support for APdesk and MESHdesk] admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 3G / Mobile support for APdesk and MESHdesk ====== | ====== 3G / Mobile support for APdesk and MESHdesk ====== | ||
| + | {{ : | ||
| ===== Introduction ===== | ===== Introduction ===== | ||
| Line 8: | Line 9: | ||
| * Since neither **MESHdesk** nor **APdesk** are driven by hardware sales but rather to provide creative solutions, this then offered just such an opportunity. | * Since neither **MESHdesk** nor **APdesk** are driven by hardware sales but rather to provide creative solutions, this then offered just such an opportunity. | ||
| * We can now with pride say we also support mobile Internet connections as an alternative to Ethernet based Internet connections. | * We can now with pride say we also support mobile Internet connections as an alternative to Ethernet based Internet connections. | ||
| + | |||
| + | {{ : | ||
| - | ---------------- | + | |
| + | ------------------------- | ||
| ===== A Catch-22 ===== | ===== A Catch-22 ===== | ||
| Line 21: | Line 26: | ||
| * **Enable** will enable all the fields which you can then populate. | * **Enable** will enable all the fields which you can then populate. | ||
| * **Disable** will disable an existing mobile configuration (provided there is one) | * **Disable** will disable an existing mobile configuration (provided there is one) | ||
| - | | + | * See the following screenshot which was for one of my 3G dongles |
| + | {{ : | ||
| + | |||
| + | <WRAP center round tip 90%> | ||
| + | * The following URL has a nice list of APN and usernames for various providers over the world: | ||
| + | * http:// | ||
| + | </ | ||
| + | |||
| + | |||
| + | | ||
| + | |||
| + | ------------- | ||
| + | |||
| + | ===== What's the requirements? | ||
| + | * There is not much extra requirements. You basically need the following things. | ||
| + | * A device that can support a mobile Internet connection, eg. one with a USB port that can take the 3G dongle. | ||
| + | * The extra modules required included with the firmware running on the device. See this bit on building your own firmware: [[http:// | ||
| + | * The latest version of the **MESHdesk Node Config Utility** | ||
| + | * Hardware that can access the mobile network eg. a 3G Dongle. | ||
| + | * On the exit points of both **MESHdesk** meshed and APdesk AP Profiles you **cannot** have an exit point that is bridged with Ethernet | ||
| + | * You can have a: | ||
| + | * Captive Portal | ||
| + | * NAT + DHCP | ||
| + | * OpenVPN Bridge | ||
| + | |||
| + | ----------------- | ||
| + | |||
| + | ===== Lets get technical ===== | ||
| + | For those technical people, the next section is aimed at you. | ||
| + | * The MESHdesk Node Config Utility will insert an entry into the **/ | ||
| + | * This means you can actually pre-build / configure the device, provided they do not require a pin or the pin is common among the devices which you will flash the firmware on. | ||
| + | * It also means you can disable the interface in **/ | ||
| + | * The script which sets up the device will check if there is a **wwan** entry in the meshdesk config file and if it is there and active it will include that declaration in the **/ | ||
| + | * If you need more inf on getting your mobile dongle working, refer to this pages: | ||
| + | * https:// | ||
| + | * Although the above page has lots of information, | ||
| + | |||
| + | <code bash> | ||
| + | config interface ' | ||
| + | option proto ' | ||
| + | option service ' | ||
| + | option pincode 1234 | ||
| + | option apn ' | ||
| + | option username ' | ||
| + | option device '/ | ||
| + | </ | ||