Tube2H WPA login max 16 characters, does OpenWrt allow longer?

Hello, I just buy a Tube2H to get a hotspot wifi in a camping but I stuck on the login password for WPA2-psk enterprise beaucause I can only enter 16 characters for the WPA User Name .

The user name is like : itisme@proximuswifi.be.

Should I flash Openwrt to the Alpha Tube2H to fix it?

OpenWrt does not have that limitation. After installing OpenWrt you will need to temporarily connect to the Internet and change the wpad-basic package to full wpad before Enterprise authentication can be used though.

The 2H (not 2HP) has only 32 MB of RAM, which may limit what you can do but should be OK for a simple routed client. Also know the flash size of your unit (most likely 8M) do not use the wrong build it will clobber important information in flash (the ART partition) and prevent wifi from ever working again. If possible, log into the stock firmware with ssh and make a backup of the ART data before flashing.

Thank you,

I found 3 files:
openwrt-19.07.7-ar71xx-generic-tube2h-8M-squashfs-sysupgrade.bin 7.697Ko
openwrt-19.07.7-ar71xx-generic-tube2h-8M-squashfs-factory.bin 3.937ko
gluon--ffmsd24-v2018.2.2+4.1.0-alfa-network-tube2h-sysupgrade.bin 7.667ko

can't I simply add the wpad packadge on the existing firmware?

Assuming the current OS isn't an official openwrt release, no you can't.

ok, so If just update my firmware with this file it should be ok: openwrt-19.07.7-ar71xx-generic-tube2h-8M-squashfs-sysupgrade.bin 7.697Ko ?

.... just follow the guide in the wiki.

and what mk24 said, you need to replace the wpad package after installing openwrt.

ok, will try to do that , many thanks for your help

I have installed openwrt-19.07.7-ar71xx-generic-tube2h-8M-squashfs-factory.bin 3.937ko

Device does not reply anymore

I think that I do not may use the advanced update in alpha menu ...

The http recovery described on the device page is the recommended install method. That should still work even if bricked.

1 Like

connect only a client and device through a cable, nothing else.

client should get IP, and the Tube should be reachable at 192.168.1.1.

(assuming flash was successful, but it seems you didn't use the recommended method)

Finaly after figured out that my firewall was bloking U-boot, I manage to get into the update firmware page .
I upload the sysupdate file but when device reset it is always show the update firmware page on 192.168.1.1

that's what I got:

nc -u -p 6666 192.168.1.1 6666

U-Boot 1.1.4  (Sep 20 2016)

uboot> httpd
httpd
HTTP server is starting at IP: 192.168.1.1
HTTP server is ready!

Request for: /
Request for: /style.css
Data will be downloaded at 0x80800000 in RAM
Upgrade type: firmware
Upload file size: 4031209 bytes
Loading: #######################################
         #######################################


HTTP upload is done! Upgrading...

** Warning: upgrading firmware is in progress

** DO NOT POWER OFF THE DEVICE!

Executing: erase 0x9F050000 +0xF90000; cp.b 0x80800000 0x9F050000 0x3D82E9
Erase FLASH from 0x9F050000 to 0x9FFDFFFF in bank #1
Erasing: #######################################
         #######################################
         #######################################
         #######################################
         #######################################
         #######################################
         ###############

Erased sectors: 249

Copying to FLASH...
Writting at address: 0x9F050000

Done!

HTTP ugrade is done! Rebooting...


Resetting the board...

It does nothin after Resettinng the board

That address implies it is a 16M chip.

You won't see anything on the netcat console during / after boot, but if you open the case and connect a serial terminal the boot log would be shown.

Another thing you could try is use the bootloader CLI to TFTP and boot the initramfs (16M) OpenWrt. This will not alter data in flash.

uboot> printenv
printenv
bootdelay=1
baudrate=115200
ipaddr=192.168.1.1
serverip=192.168.1.2
bootfile="firmware.bin"
loadaddr=0x80800000
ncport=6666
alfa_boot=bootm $kernel_addr || bootm $firmware_addr
uboot_name=u-boot-tube2h.bin
uboot_upg=if ping $serverip; then tftp $loadaddr $uboot_name && if itest.l $filesize == $uboot_size; then erase $uboot_addr +$filesize && cp.b $loadaddr $uboot_addr $filesize && echo OK!; else echo ERROR! Wrong file size!; fi; else ERROR! Server not reachable!; fi
firmware_name=firmware-tube2h.bin
firmware_upg=if ping $serverip; then tftp $loadaddr $firmware_name && erase $firmware_addr +$filesize && cp.b $loadaddr $firmware_addr $filesize && echo OK!; else ERROR! Server not reachable!; fi
ethact=eth0
bootcmd=run alfa_boot
bootargs=console=ttyS0,115200 root=31:02 init=/sbin/init mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),14336k(rootfs),1600k(uImage),64k(NVRAM),64k(ART)
ethaddr=00:c0:ca:a6:02:c6
flash_size=0x01000000
firmware_addr=0x9f050000
firmware_size=0x00f90000
uboot_addr=0x9f000000
uboot_size=0x00040000
env_addr=0x9f040000
env_size=0x00010000
art_addr=0x9fff0000
art_size=0x00010000
kernel_addr=0x9fe50000
stdin=nc
stdout=nc
stderr=nc

Environment size: 1165/65532 bytes


uboot> iminfo
iminfo

## Checking Image at 80800000 ...
   Bad Magic Number
uboot>
uboot> md 0x9fff0000
md 0x9fff0000
9FFF0000: 00C0CAA6 02C700C0 CAA602C6 FFFFFFFF    ................
9FFF0010: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0020: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0030: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0040: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0050: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0080: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF0090: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00A0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00B0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00C0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00D0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00E0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FFF00F0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
uboot>


md 0x9f050000
9F050000: 1F8B0800 EEC3B059 0003D4B8 438C304C    .......Y....C.0L
9F050010: F0EE3BB6 6DDB36DF B16DDBB6 6DDBB66D    ..;.m.6..m..m..m
9F050020: DBB66DDB 33F7FBDF DCC5D9DC 9CD5599C    ..m.3.........Y.
9F050030: 5FD2A9A4 BAD2A9A4 AA3BF5B4 9589A3AD    _........;......
9F050040: 89359D85 8D819909 C0FF2118 FE838D85    .5........!.....
9F050050: E57F2C23 3B2BC3FF 6A1958D8 1919D998    ..,#;+..j.X.....
9F050060: 58001899 19595918 59FEF3B3 01303032    X....YY.Y....002
9F050070: B3B23101 1030FC9F 4AE87FC5 C5C9D9C0    ..1..0..J.......
9F050080: 918000C0 D0C5C2DA D8D0CEF9 FF2FEE7F    ............./..
9F050090: B7FF7F29 E4A098AA 088D9F01 1AF543DB    ...)..........C.
9F0500A0: 00C849CA FE600000 FFB38691 E6A14041    ..I..`........@A
9F0500B0: 81806524 E49508E4 EC4D6CD5 1C9D09A4    ..e$.....Ml.....
9F0500C0: 2D6C5DDC 6999E918 39E8FE2B E7FF8BCD    -l].i...9..+....
9F0500D0: 7FE100D9 C5DCFFDF 71763F7F 7F456D7E    ........qv?..Em~
9F0500E0: D22C6FEF 7B0A9EB6 5B3CD73E B2050EEE    .,o.{...[<.>....
9F0500F0: 717CA674 1A840D9E 4094AD69 52A1F3DE    q|.t....@..iR...

md 0x9fe50000
9FE50000: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50010: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50020: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50030: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50040: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50050: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50060: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50070: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50080: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE50090: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500A0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500B0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500C0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500D0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500E0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................
9FE500F0: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF    ................


TFTP from IP: 192.168.1.2
      Our IP: 192.168.1.1
    Filename: 'firmware.bin'
Load address: 0x80800000
       Using: eth0

     Loading: *
## Error: 'Connection from this IP Address is prohibited by security settings of the server.' (2), starting again!

Stupid question, maybe does I need to rename the file I upload too "firmware.bin" ?

The "security settings error" came from the server. Your TFTP server is misconfigured.

It's definitely a 16M model, so the simplest course would be to http the 16M sysupgrade instead of 8M.

1 Like

the 16M should be the tube 2hp, tube2h is 8M.

Thank you Very much for your support Mike

Status

System

Hostname

OpenWrt

Model

ALFA NETWORK Tube2H

Architecture

Atheros AR9330 rev 1

Firmware Version

OpenWrt 19.07.7 r11306-c4a6851c72 / LuCI openwrt-19.07 branch git-21.044.30835-34e0d65

Kernel Version

4.14.221

Local Time

2021-02-15 15:27:11

Uptime

0h 4m 45s

Load Average

0.47, 0.36, 0.17

Where can I find the full wpad package?