+ Reply to Thread
Page 2 of 3 FirstFirst 1 2 3 LastLast
Results 11 to 20 of 21

Thread: Hacked 2b with O2

  1. #11
    I cant telnet or ssh into the hub ?
    I have downgraded and upgraded the firmware to .18
    I can access the usb1 folder on the usb when inserted into the hub but cannot access the sys folder, error is folder is empty or insufficient priviledges....

  2. #12
    Administrator PsiDOC's Avatar
    Join Date
    Dec 2010
    Location
    Pembrokeshire
    Posts
    517
    1: Downgrade to firmware 3.17 using this tutorial: http://www.psidoc.com/showthread.php...-can-unlock-it.
    2: Unlock the router PROPERLY using this tutorial: http://www.psidoc.com/showthread.php...ull-CLI-access.
    3: You can now SSH in an do all you need to do.

    Psi

  3. #13
    Junior Member
    Join Date
    Oct 2011
    Posts
    12
    I now see that Psidoc has already replied but here is a reply I was preparing with more detail!
    It is not possible use the memory stick trick with firmware version .18 as BT have closed that loop hole.
    You have to downgrade to version .17. Use a memory stick to telnet, unlock (if not already done) and modify the internal firewall rules (to allow subsequent ssh).
    I used: conf set fw/policy/0/chain/fw_br0_in/rule/0/enabled 0
    as described by Technodevotee in #2 of http://www.psidoc.com/showthread.php/330-Question-concerning-the-firewall-hack-in-unlocking-instructions.
    I also stopped further upgrades using conf set cwmp/enabled 0
    See #20 by aicer in http://www.psidoc.com/showthread.php...n_upgrade_type
    Do not forget to save to flash: conf reconf 1
    You should then have a fully hacked HH2B but with firmware ..17.
    If you want to upgrade to version ..18, you should first save the ..17 HH settings using the browser interface.
    Then when you upgrade to ..18 you can restore the settings (saved from ..17) via a browser. Without such restoration any firewall modification is lost. Then you should be able to use ssh with ..18
    I am not certain that the upgrade block above survives all this but you can check using ssh and if necessary repeat that blocking command. There is always the possibility that a further upgrade by BT may make it even more difficult.
    Peter

  4. #14
    downgraded and all ok after setting conf set fw/policy/0/chain/fw_br0_in/rule/0/enabled 0
    Now, which changes are required to get onto O2... I have done conf print / and it give a whole hierarchy of settings.....

  5. #15
    I think I know the changes I need to make to the 2B, just need to understand how to make the changes via CLI as I dont understand the command or directory structure.
    So for example if I need to make the following changes how to I go about it,,,,

    Change:
    ifconfig intf=atm_Internet dest=pvc_Internet encaps=vcmux ulp=ppp
    To:
    ifconfig intf=atm_Internet dest=pvc_Internet ulp=mac

  6. #16
    Super Moderator
    Join Date
    Mar 2011
    Posts
    348
    the ifconfig commands are for the 2A not the 2B and I am starting to think they have removed something from the 2B to stop you using it on ETHoA connections

  7. #17
    I was hoping if I could make some of the changes that were made to the 2A for O2, on the 2B, I may be able to get online !

  8. #18
    Super Moderator
    Join Date
    Mar 2011
    Posts
    348
    Yes that is what we are working on

  9. #19
    it would be a good learning exercise for me, so if I can help in any way, please let me know

  10. #20

    Be There (Unlimited)

    HH 2.0 B needs to be set to ETHoA if you've got a dynamic IP. If you got a fixed IP it needs to be set as IPoEoATM.

    Issue is finding out the CLI command to set it up properly.

    Has anyone managed to use HH 2.0 Type B with either Be or O2?

    Regards

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts