User Tools

Site Tools


toh:bt:homehub_v5a

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:bt:homehub_v5a [2018/07/13 11:46]
lankme [More examples]
toh:bt:homehub_v5a [2018/08/29 17:14] (current)
bill888 [United Kingdom - Quick Setup with LuCI]
Line 69: Line 69:
  
 | **Resistor number** | **Function** | **Info** | **Notes** | | **Resistor number** | **Function** | **Info** | **Notes** |
-| R77 | Serial TX | Below the NAND flash | Use the solder to the pad right of it | +| R77 | **Serial TX** | Below the NAND flash | Use the solder to the pad right of it | 
-| R78 | Serial RX | Directly below R77, and to the left. | Use the solder pad to the right of it | +| R78 | **Serial RX** | Directly below R77, and to the left. | Use the solder pad to the right of it | 
-| R45 | boot_sel2 | Below R78 to the right. | Use the solder pad above it |+| R45 | **boot_sel2** | Below R78 to the right. | Use the solder pad above it |
 | R46 | boot_sel3 | Front of the PCB, next to SW4 (WPS button) | Not used for installation over serial | | R46 | boot_sel3 | Front of the PCB, next to SW4 (WPS button) | Not used for installation over serial |
-|     | GND       | USB socket shield and other locations. | Use the solder pad for WPS switch closest to NAND flash. |+|     ​| ​**GND**       | USB socket shield and other locations. | Use the solder pad for WPS switch closest to NAND flash. |
  
 Serial uses Baud rate 115200. Serial uses Baud rate 115200.
Line 94: Line 94:
 UART</​code>​ UART</​code>​
   - Remove the connection between boot_sel2 and GND   - Remove the connection between boot_sel2 and GND
-  - Load u-boot via serial console into the device'​s memory (this takes approx. 3 minutes): lede-lantiq-bthomehubv5a_ram-u-boot.asc. ​ under linux you can use picocom to connect as follows: +  - Load u-boot via serial console into the device'​s memory (this takes approx. 3 minutes): lede-lantiq-bthomehubv5a_ram-u-boot.asc ​using the instructions for Microsoft Windows or Linux as follows. 
-<​code>​picocom -b 115200 /​dev/​ttyUSB0</​code>​**NEW:​** ​In picocom, press <​**Ctrl-a**>​ <​**Ctrl-s**>​ and enter the full path to the ''​lede-lantiq-bthomehubv5a_ram-u-boot.asc''​ to send the bootcode.+ 
 +**__Microsoft Windows__**  
 + 
 +Download and study the "​**Serial console instructions using MS Windows**"​ and "​**LEDE Installation Guide for BT Home Hub 5A**" documents listed in the Downloads section of this page. 
 + 
 +**__Linux__**  
 + 
 +You can use picocom to connect as follows: 
 +<​code>​picocom -b 115200 /​dev/​ttyUSB0 ​--send-cmd="​cat"​</​code> ​ 
 +In picocom, press <​**Ctrl-a**>​ <​**Ctrl-s**>​ and enter the full path to the ''​lede-lantiq-bthomehubv5a_ram-u-boot.asc''​ to send the bootcode.
  
 Alternatively,​ open another terminal and execute the following command to send the bootcode <​code>​cat lede-lantiq-bthomehubv5a_ram-u-boot.asc > /​dev/​ttyUSB0</​code> ​ Now you should see the ''​BTHOMEHUBV5A#''​ u-boot prompt. Alternatively,​ open another terminal and execute the following command to send the bootcode <​code>​cat lede-lantiq-bthomehubv5a_ram-u-boot.asc > /​dev/​ttyUSB0</​code> ​ Now you should see the ''​BTHOMEHUBV5A#''​ u-boot prompt.
Line 104: Line 113:
  
  
-==== Installing OpenWrt/​LEDE (switching from original BT/Plusnet firmware to LEDE) ====+===== Installing OpenWrt/​LEDE (switching from original BT/Plusnet firmware to LEDE) =====
  
 **<color #​ed1c24>​Use these instructions to install all stable and snapshot builds of LEDE released after 30 November 2016, and all snapshots of OpenWrt released from January 2018.</​color>​** **<color #​ed1c24>​Use these instructions to install all stable and snapshot builds of LEDE released after 30 November 2016, and all snapshots of OpenWrt released from January 2018.</​color>​**
Line 129: Line 138:
     - Carefully read the instructions that the script provides     - Carefully read the instructions that the script provides
     - Once the script is finished you have unlocked u-boot and changed the UBI volumes/​partitions (LEDE is not installed yet)     - Once the script is finished you have unlocked u-boot and changed the UBI volumes/​partitions (LEDE is not installed yet)
-    - Installing LEDE is usually easy: use wget to download ''​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin''​ (to /tmp), then run: <​code>​sysupgrade /​tmp/​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin</​code>​ or more easily download and copy the ''​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin''​ image to the USB stick you used to backup the firmware earlier. You can then run <​code>​sysupgrade /mnt/​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin</​code>​+    - Installing LEDE is usually easy: use wget to download ''​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin''​ (to /tmp), then run: <​code>​sysupgrade /​tmp/​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin</​code>​ or more easily download and copy the ''​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin''​ image to the USB stick you used to backup the firmware earlier. You can then run <​code>​sysupgrade /tmp/​mounts/​USB-A1/​lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin</​code>​
     - After the installation has completed, the device will reboot automatically back to boot-over-UART (''​CFG 04''​) mode.  Power cycle the hub to enable LEDE to boot.     - After the installation has completed, the device will reboot automatically back to boot-over-UART (''​CFG 04''​) mode.  Power cycle the hub to enable LEDE to boot.
     - If the hub presents you with a 'VR9 #' prompt, execute these two commands, and power cycle the hub to enable LEDE to boot: <​code>​setenv bootcmd ubi part UBI\; ubi read \$(loadaddr) kernel\; bootm \$(loadaddr)</​code><​code>​saveenv</​code>​     - If the hub presents you with a 'VR9 #' prompt, execute these two commands, and power cycle the hub to enable LEDE to boot: <​code>​setenv bootcmd ubi part UBI\; ubi read \$(loadaddr) kernel\; bootm \$(loadaddr)</​code><​code>​saveenv</​code>​
Line 135: Line 144:
  
  
 +===== ADSL/VDSL Configuration Examples =====
  
-===== Switch =====+[[docs:​guide-user:​network:​wan:​isp-configurations]]
  
-<​sortable>​ 
-^ Case label ^ swconfig/​kernel port number ^ 
-| 1          | 4                           | 
-| 2          | 2                           | 
-| 3          | 0                           | 
-| 4          | 1                           | 
-| WAN (red)  | 5                           | 
-| -          | 6 (CPU)                     | 
-| -          | 3 (unused) ​                 | 
-</​sortable>​ 
  
-Depending on your version of LuCI and your ''/​etc/​board.json'',​ LuCI may display ports in various orders (matching the labels/​matching the swconfig numbering/​not matching anything) and may or may not list the WAN port even though it's available via [[docs:​techref:​swconfig]]. +==== United Kingdom ​Quick Setup with LuCI ====
-  * If LuCI lists seven ports (Port 0 -- Port 5 + CPU), it's probably using the swconfig numbering and ignoring ''/​etc/​board.json''​. ​ Put up with the internal numbering or upgrade ​LuCI.  On the bright side, you don't need to edit anything to make use of the WAN port. +
-  * If LuCI lists five ports (LAN 1 -- LAN 4 + CPU), it's probably using either the case label numbering or a made-up numbering. ​ Either way, it's probably based on ''/​etc/​board.json''​. ​ You can either use ''/​etc/​config/​network''​ instead or [[#​example_boardjson_tweak |edit /​etc/​board.json]] to make the UI include the WAN port (and if necessary, correct the numbering).+
  
-Notes about this quirky layout: +__**For VDSL (FTTC):**__
-  ​According to [[docs:​techref:​swconfig]] ''​eth0''​ is the (only) interface through which the switch is configured, yet if you want to see traffic on switch port 5 (WAN) you'll need to add it to a VLAN and you'll see the traffic on ''​eth1.**N**'',​ which isn't presented as a choice in LuCI.  (eth1 seems to behave both as [[https://​bugs.lede-project.org/​index.php?​do=details&​task_id=83#​comment308| a second CPU port]] and as a physical port on the switch, depending on context.) +
-    ​* For example, in the typical wired-WAN setup where you've put ports 1--4 in VLAN 1 and the WAN port in VLAN 2, you'd set **Interfaces** -> **WAN** -> **Physical Settings** -> **Custom Interface:​** ''​eth1.2''​. +
-  * Since [[https://​github.com/​openwrt/​luci/​commit/​3ea9c85ed6a12c9175a11626f2bfeb9ae8425f9c |commit 3ea9c85e]] ​(mid-Aug 2016LuCI can hide some of the layout oddness. ​ ''/​etc/​board.d/​02_network''​ generates ''/​etc/​board.json''​ which newer LuCI uses when presenting the Network -> Switch page. +
-    * OpenWrt has an incorrect ''/​etc/​board.d/​02_network''​ as of [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​lantiq/​base-files/​etc/​board.d/​02_network?​rev=48941 |r48941]], but (with newer LuCI) you can [[#​example_boardjson_tweak |edit /​etc/​board.json]]. +
-    ​LEDE has a correct ''/​etc/​board.d/​02_network''​ as of [[https://​git.lede-project.org/?​p=source.git;​a=blob;​f=target/​linux/​lantiq/​base-files/​etc/​board.d/​02_network;​hb=96f6bd501a3b57813e698ad2b531f115f710c75e#​l121 |96f6bd501]] so should have a correct ''/​etc/​board.json'',​ but may not expose the WAN port. +
-  ​In at least LEDE, [[https://​bugs.lede-project.org/​index.php?​do=details&​task_id=83#​comment580 |at the kernel/​driver/​switch level the layout seems unlikely to change]], so kernel messages and swconfig will use the non-obvious switch port numbering for the foreseeable future. +
-  * It's possible that configurations using ''​eth1''​ [[https://​forum.openwrt.org/​viewtopic.php?​id=63354 |may be unstable]]. +
-  * LAN and WAN may have been separated this way [[https://​forum.openwrt.org/​viewtopic.php?​id=53511&​p=18 |to avoid "tx ring" kernel errors]]; more clarity needed. +
-  * Changeset [[https://​dev.openwrt.org/​changeset/​40317 |40317]] created the [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​lantiq/​dts/​BTHOMEHUBV5A.dts?​rev=+48657#​L212 |DTS]] with this odd layout and changeset [[https://​dev.openwrt.org/​changeset/​46223 |46223]] copied it to create HH5A support --- but it may simply reflect equally odd hardware layout.+
  
-==== Example board.json tweak ====+  - Go to LuCI -> Network -> Interfaces.  
 +  - Set '​DSL'​ parameters to 'Annex B(all)'​ and '​tone'​ set to 'A43C + J43 + A43', select PTM, and VDSL. 
 +  - Edit the '​WAN'​ interface -> Physical Settings tab.  
 +  - Select '​Custom Interface'​ and enter '​ptm0.101'​ or '​dsl0.101'​ for LEDE 17 and OpenWRT 18 respectively to set vlan 101 for BT Openreach network compatibility.
  
-Assumptions:​ +For most ISPs except ​for TalkTalk and Sky/NOW broadband:
-  * you want to use the WAN port, not DSL, for your uplink +
-  * you're using a LuCI newer than [[https://​github.com/​openwrt/​luci/​commit/​3ea9c85ed6a12c9175a11626f2bfeb9ae8425f9c |commit 3ea9c85e]] (mid-Aug 2016) meaning you see LAN 1 -- LAN 4; either you're annoyed that you can't see port 5, or you're annoyed at the UI not matching the labelled ports +
-  * you can edit config files, probably via ([[docs:techref:​hardware:​port.serial|serial]] or [[doc/​howto/​firstlogin |SSH]]) [[docs:​guide-user:​base-system:​user.beginner.cli|CLI access]] +
-  * you've made a backup copy of ''/​etc/​board.json''​ already, or you're confident you can regenerate defaults using ''/​etc/​board.d/​*''​ later+
  
-Replace ​''​/etc/board.json'' ​with the following.  ​Note that by doing this, you're not //configuring// anything.  ''/​etc/​board.json'' ​is only meant to describe hardware properties and defaults. ​ The changes to ''​roles''​ and ''​network'' ​are just for internal consistency.  ​Nonetheless,​ you should ​**put your own unit's MAC address in ''​network:*:macaddr''​**+  - Edit the 'WAN' ​interface. 
-<WRAP bootlog><​nowiki>​{ +  - Choose PPPoE protocol. 
-        "​model":​ { +  - Enter username and password. 
-                "​id":​ "​BTHOMEHUBV5A",​ + 
-                "​name":​ "BT Home Hub 5A" +For TalkTalk: 
-        }, + 
-        "​led":​ { +  - Edit the 'WAN' ​interface. 
-                "​wifi":​ { +  - Choose DHCP protocol. 
-                        "​name":​ "​wifi",​ + 
-                        "​type":​ "​trigger",​ +For Sky Broadband:​ 
-                        "​sysfs":​ "​bthomehubv5a:​blue:​wireless",​ + 
-                        "​trigger":​ "​phy0tpt"​ +[[http://www.skyuser.co.uk/forum/sky-broadband-fibre-help/​50483-generic-open-wrt-sky-fibre-mer-guide.html]] 
-                }, + 
-                "​internet":​ { + 
-                        "​name":​ "​internet",​ +__**For ADSL (PPPoA):​**__ 
-                        "​type":​ "​netdev",​ + 
-                        "​sysfs":​ "​bthomehubv5a:​blue:​broadband", +  - Go to LuCI -> Network -> Interfaces'​. ​ 
-                        "​device":​ "​nas0",​ +  - Set 'DSL' ​parameters ​to 'Annex A(all)' and 'tone' ​set to 'A43C + J43 + A43', select ATM, and ADSL. 
-                        "​mode":​ "link tx rx" +  **Important:** Remove the 'ATM bridge' ​section as this is incompatible with PPPoA connections
-                }, + 
-                "​dimmed":​ { +For most ISPs except Sky/​NOW ​broadband. 
-                        "​name"​"​dimmed",​ + 
-                        "​sysfs"​"​dimmed",​ +  - Edit the '​WAN'​ interface. 
-                        "​default"​"0" +  - Choose PPPoA protocol. 
-                } +  - Enter username and password. 
-        }, +  - PPPoA EncapsulationVC-Mux 
-        "​switch":​ { +  - VCI38 
-                "​switch0":​ { +  - VPI: 0 
-                        "​enable":​ true, + 
-                        "​reset":​ true, +Sky Broadband may also accept usernameinstall@o2broadband.co.uk with no password with PPPoA protocol. 
-                        "​ports":​ [ + 
-                                { +__**For ADSL (PPPoE):**__
-                                        "​num":​ 0, +
-                                        "​role":​ "​lan",​ +
-                                        "​index":​ 3 +
-                                }, +
-                                { +
-                                        "​num":​ 1, +
-                                        "​role":​ "​lan",​ +
-                                        "​index":​ 4 +
-                                }, +
-                                { +
-                                        "​num":​ 2, +
-                                        "​role":​ "​lan",​ +
-                                        "​index":​ 2 +
-                                }, +
-                                { +
-                                        "​num":​ 4, +
-                                        "​role":​ "​lan",​ +
-                                        "​index":​ 1 +
-                                }, +
-                                { +
-                                        "​num":​ 5, +
-                                        "​role":​ "​wan",​ +
-                                        "​index":​ 5 +
-                                }, +
-                                { +
-                                        "​num":​ 6, +
-                                        "​device":​ "​eth0",​ +
-                                        "​need_tag":​ true +
-                                } +
-                        ], +
-                        "​roles":​ [ +
-                                { +
-                                        "​role":​ "​lan",​ +
-                                        "​ports":​ "0 1 2 4 6t", +
-                                        "​device"​"eth0.1" +
-                                } +
-                                { +
-                                        "​role":​ "​wan",​ +
-                                        "​ports":​ "5 6t", +
-                                        "​device":​ "eth1.2" +
-                                } +
-                        ] +
-                } +
-        }, +
-        "​network":​ { +
-                "​lan":​ { +
-                        "​ifname":​ "​eth0.1",​ +
-                        "protocol": "​static",​ +
-                        "​macaddr":​ "​18:​62:​2c:​XX:​XX:​XX"​ +
-                }, +
-                "​wan":​ { +
-                        "​ifname":​ "eth1.2", +
-                        "​protocol":​ "​dhcp",​ +
-                        "​macaddr"​<copy this from lan above, bump last octet up by one> +
-                } +
-        } +
-+
-</​nowiki></​WRAP>​\\+
  
-===== ADSL/​VDSL/​VDSL2 examples ===== +  - Go to LuCI -> Network -> Interfaces. ​ 
-==== Use with 'BT' ​Infinity ​(FTTCUK VDSL ====+  - Set 'DSL' ​parameters to 'Annex A(all)' and '​tone'​ set to 'A43C + J43 + A43', select ATM, and ADSL. 
 +  - Set 'ATM bridge'​ parameters, VCI: 38, VPI: 0. Encapsulation mode: LLC 
 +  - Edit the '​WAN'​ interface -> Physical Settings tab.  
 +  - Select '​Custom Interface'​ and enter '​nas0'​ or '​dsl0'​ for LEDE 17 and OpenWRT 18 respectively.
  
-For my FTTC, in luci '​network/​interfaces'​ I set '​dsl'​ to 'Annex B(all)' ​and left '​tone'​ where it was at 'A43C + J43 + A43', selected PTM, and VDSL.+BT and Plusnet support PPPoE protocol(Sky/NOW and TalkTalk do not support PPPoE on ADSL)
  
-In '​WAN' ​I set PPPoE and username and password ​(I'm on plusnet, so it's <​username>​@plusdsl.net + pwd). In Physical Settings, I selected '​Custom Interface'​ and entered '​ptm0.101'​ (apparently sets vlan 101 for BT network compatibility). A little guesswork....+  - Edit the '​WAN' ​interface. 
 +  - Choose ​PPPoE protocol. 
 +  - Enter username and password.
  
-Seems to work nicely. 
  
 +For other configurations,​ such as 'VDSL Bridge modem' (to emulate old Openreach VDSL modems), refer to the **LEDE Installation Guide for BT Home Hub 5A** for instructions.
 ==== 1und1 (Germany) VDSL2 (Annex B) example ==== ==== 1und1 (Germany) VDSL2 (Annex B) example ====
  
Line 346: Line 281:
  
 </​nowiki></​WRAP>​\\ </​nowiki></​WRAP>​\\
 +
  
 ==== rt.ru (Russia) ADSL2 (Annex A) example ==== ==== rt.ru (Russia) ADSL2 (Annex A) example ====
Line 423: Line 359:
 ... ...
 </​nowiki></​WRAP>​\\ </​nowiki></​WRAP>​\\
 +
 +
 +
 +===== Switch =====
 +
 +<​sortable>​
 +^ Case label ^ swconfig/​kernel port number ^
 +| 1          | 4                           |
 +| 2          | 2                           |
 +| 3          | 0                           |
 +| 4          | 1                           |
 +| WAN (red)  | 5                           |
 +| -          | 6 (CPU)                     |
 +| -          | 3 (unused) ​                 |
 +</​sortable>​
 +
 +Depending on your version of LuCI and your ''/​etc/​board.json'',​ LuCI may display ports in various orders (matching the labels/​matching the swconfig numbering/​not matching anything) and may or may not list the WAN port even though it's available via [[docs:​techref:​swconfig]].
 +  * If LuCI lists seven ports (Port 0 -- Port 5 + CPU), it's probably using the swconfig numbering and ignoring ''/​etc/​board.json''​. ​ Put up with the internal numbering or upgrade LuCI.  On the bright side, you don't need to edit anything to make use of the WAN port.
 +  * If LuCI lists five ports (LAN 1 -- LAN 4 + CPU), it's probably using either the case label numbering or a made-up numbering. ​ Either way, it's probably based on ''/​etc/​board.json''​. ​ You can either use ''/​etc/​config/​network''​ instead or [[#​example_boardjson_tweak |edit /​etc/​board.json]] to make the UI include the WAN port (and if necessary, correct the numbering).
 +
 +Notes about this quirky layout:
 +  * According to [[docs:​techref:​swconfig]] ''​eth0''​ is the (only) interface through which the switch is configured, yet if you want to see traffic on switch port 5 (WAN) you'll need to add it to a VLAN and you'll see the traffic on ''​eth1.**N**'',​ which isn't presented as a choice in LuCI.  (eth1 seems to behave both as [[https://​bugs.lede-project.org/​index.php?​do=details&​task_id=83#​comment308| a second CPU port]] and as a physical port on the switch, depending on context.)
 +    * For example, in the typical wired-WAN setup where you've put ports 1--4 in VLAN 1 and the WAN port in VLAN 2, you'd set **Interfaces** -> **WAN** -> **Physical Settings** -> **Custom Interface:​** ''​eth1.2''​.
 +  * Since [[https://​github.com/​openwrt/​luci/​commit/​3ea9c85ed6a12c9175a11626f2bfeb9ae8425f9c |commit 3ea9c85e]] (mid-Aug 2016) LuCI can hide some of the layout oddness. ​ ''/​etc/​board.d/​02_network''​ generates ''/​etc/​board.json''​ which newer LuCI uses when presenting the Network -> Switch page.
 +    * OpenWrt has an incorrect ''/​etc/​board.d/​02_network''​ as of [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​lantiq/​base-files/​etc/​board.d/​02_network?​rev=48941 |r48941]], but (with newer LuCI) you can [[#​example_boardjson_tweak |edit /​etc/​board.json]].
 +    * LEDE has a correct ''/​etc/​board.d/​02_network''​ as of [[https://​git.lede-project.org/?​p=source.git;​a=blob;​f=target/​linux/​lantiq/​base-files/​etc/​board.d/​02_network;​hb=96f6bd501a3b57813e698ad2b531f115f710c75e#​l121 |96f6bd501]] so should have a correct ''/​etc/​board.json'',​ but may not expose the WAN port.
 +  * In at least LEDE, [[https://​bugs.lede-project.org/​index.php?​do=details&​task_id=83#​comment580 |at the kernel/​driver/​switch level the layout seems unlikely to change]], so kernel messages and swconfig will use the non-obvious switch port numbering for the foreseeable future.
 +  * It's possible that configurations using ''​eth1''​ [[https://​forum.openwrt.org/​viewtopic.php?​id=63354 |may be unstable]].
 +  * LAN and WAN may have been separated this way [[https://​forum.openwrt.org/​viewtopic.php?​id=53511&​p=18 |to avoid "tx ring" kernel errors]]; more clarity needed.
 +  * Changeset [[https://​dev.openwrt.org/​changeset/​40317 |40317]] created the [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​lantiq/​dts/​BTHOMEHUBV5A.dts?​rev=+48657#​L212 |DTS]] with this odd layout and changeset [[https://​dev.openwrt.org/​changeset/​46223 |46223]] copied it to create HH5A support --- but it may simply reflect equally odd hardware layout.
 +
 +==== Example board.json tweak ====
 +
 +Assumptions:​
 +  * you want to use the WAN port, not DSL, for your uplink
 +  * you're using a LuCI newer than [[https://​github.com/​openwrt/​luci/​commit/​3ea9c85ed6a12c9175a11626f2bfeb9ae8425f9c |commit 3ea9c85e]] (mid-Aug 2016) meaning you see LAN 1 -- LAN 4; either you're annoyed that you can't see port 5, or you're annoyed at the UI not matching the labelled ports
 +  * you can edit config files, probably via ([[docs:​techref:​hardware:​port.serial|serial]] or [[doc/​howto/​firstlogin |SSH]]) [[docs:​guide-user:​base-system:​user.beginner.cli|CLI access]]
 +  * you've made a backup copy of ''/​etc/​board.json''​ already, or you're confident you can regenerate defaults using ''/​etc/​board.d/​*''​ later
 +
 +Replace ''/​etc/​board.json''​ with the following. ​ Note that by doing this, you're not //​configuring//​ anything. ​ ''/​etc/​board.json''​ is only meant to describe hardware properties and defaults. ​ The changes to ''​roles''​ and ''​network''​ are just for internal consistency. ​ Nonetheless,​ you should **put your own unit's MAC address in ''​network:​*:​macaddr''​**.
 +<WRAP bootlog><​nowiki>​{
 +        "​model":​ {
 +                "​id":​ "​BTHOMEHUBV5A",​
 +                "​name":​ "BT Home Hub 5A"
 +        },
 +        "​led":​ {
 +                "​wifi":​ {
 +                        "​name":​ "​wifi",​
 +                        "​type":​ "​trigger",​
 +                        "​sysfs":​ "​bthomehubv5a:​blue:​wireless",​
 +                        "​trigger":​ "​phy0tpt"​
 +                },
 +                "​internet":​ {
 +                        "​name":​ "​internet",​
 +                        "​type":​ "​netdev",​
 +                        "​sysfs":​ "​bthomehubv5a:​blue:​broadband",​
 +                        "​device":​ "​nas0",​
 +                        "​mode":​ "link tx rx"
 +                },
 +                "​dimmed":​ {
 +                        "​name":​ "​dimmed",​
 +                        "​sysfs":​ "​dimmed",​
 +                        "​default":​ "​0"​
 +                }
 +        },
 +        "​switch":​ {
 +                "​switch0":​ {
 +                        "​enable":​ true,
 +                        "​reset":​ true,
 +                        "​ports":​ [
 +                                {
 +                                        "​num":​ 0,
 +                                        "​role":​ "​lan",​
 +                                        "​index":​ 3
 +                                },
 +                                {
 +                                        "​num":​ 1,
 +                                        "​role":​ "​lan",​
 +                                        "​index":​ 4
 +                                },
 +                                {
 +                                        "​num":​ 2,
 +                                        "​role":​ "​lan",​
 +                                        "​index":​ 2
 +                                },
 +                                {
 +                                        "​num":​ 4,
 +                                        "​role":​ "​lan",​
 +                                        "​index":​ 1
 +                                },
 +                                {
 +                                        "​num":​ 5,
 +                                        "​role":​ "​wan",​
 +                                        "​index":​ 5
 +                                },
 +                                {
 +                                        "​num":​ 6,
 +                                        "​device":​ "​eth0",​
 +                                        "​need_tag":​ true
 +                                }
 +                        ],
 +                        "​roles":​ [
 +                                {
 +                                        "​role":​ "​lan",​
 +                                        "​ports":​ "0 1 2 4 6t",
 +                                        "​device":​ "​eth0.1"​
 +                                }
 +                                {
 +                                        "​role":​ "​wan",​
 +                                        "​ports":​ "5 6t",
 +                                        "​device":​ "​eth1.2"​
 +                                }
 +                        ]
 +                }
 +        },
 +        "​network":​ {
 +                "​lan":​ {
 +                        "​ifname":​ "​eth0.1",​
 +                        "​protocol":​ "​static",​
 +                        "​macaddr":​ "​18:​62:​2c:​XX:​XX:​XX"​
 +                },
 +                "​wan":​ {
 +                        "​ifname":​ "​eth1.2",​
 +                        "​protocol":​ "​dhcp",​
 +                        "​macaddr":​ <copy this from lan above, bump last octet up by one>
 +                }
 +        }
 +}
 +</​nowiki></​WRAP>​\\
 +
 +
 +
  
  
toh/bt/homehub_v5a.1531482396.txt.gz · Last modified: 2018/07/13 11:46 by lankme