Looking for info and possibility of (future) support of TP-Link Omada er605 Router

For Developers
247

I have not encounted this issue.
The MAC adress is detected and set on sysupgrade. See code below,

mtd_get_mac_uci_config_ubi() {
	local volumename="$1"

	. /lib/upgrade/nand.sh

	local ubidev=$(nand_attach_ubi $CI_UBIPART)
	local part=$(nand_find_volume $ubidev $volumename)

	cat "/dev/$part" | sed -n 's/^\s*option macaddr\s*'"'"'\?\([0-9A-F:]\+\)'"'"'\?/\1/Ip'
}

The only reason it would be random is if the partition the MAC address was on was overriden before running sysupgrade.

As I didnt use @chill1Penguin method of flashing recovery then OpenWRT I dont know if that is the cause or not. Maybe they can shed some light on it?

In the mean time you can just force OpenWRT to use the "correct" MAC.

Network -> Interfaces -> Devices -> eth0 -> Configure -> MAC address

248

Hi @Darbness thanks for the info,

The problem is not in eth0/eth1.... the MAC address problem is in the dsa device (in my case), the rest of devices always get the same MAC after rebooting/upgrading.

imagen
imagen702×58 2.13 KB

Can you check if your dsa device changes MAC after rebooting?

Thanks,

249

Yep, that changes after a reboot. I dont use VLANs so not much help here sorry.

250

Thanks @Darbness for the feedback!!!

In my case VLANs are working fine.

251

With the stock firmware, the MAC address is in the tddp UBI partition. The method I developed for flashing preserves this partition. If you overwrote the tddp partition or deleted it, then your MAC address will go to a random address.

As for the MAC address changing on the dsa switch, I can confirm that the address also changes to a random MAC for me, as well. To fix this by default, I suspect that a patch would have to be developed. I don’t have time to do so at the moment. Manually setting the MAC in LUCI seems to fix the changing MAC on the dsa switch.

2 Likes
252

If I touch anything in dsa device (via Luci), the network becomes unresponsive.
To make it work again, I have to edit network file and remove dsa device and reboot network.

254

Any updates on this? I have a v2, but I'm afraid to install and have no internet at all at home :frowning:

cheers

255

I have both the 605 (with OpenWRT installed - thank you @chill1Penguin for the super easy install script!) and 8511. With that said, given I want to get OpenWRT up on the latter device.

Some information regarding the ER8411 (the successor to the 605):

ubinfo 
root@ER8411:/# ubinfo -a

UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:59
Present UBI devices:            ubi0

ubi0
Volumes count:                           19
Logical eraseblock size:                 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks:     2016 (255983616 bytes, 244.1 MiB)
Amount of available logical eraseblocks: 1001 (127102976 bytes, 121.2 MiB)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  40
Current maximum erase counter value:     2
Minimum input/output unit size:          2048 bytes
Character device major/minor:            241:0
Present volumes:                         0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        partition-table
Character device major/minor: 241:1

Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        support-list
Character device major/minor: 241:2

Volume ID:   2 (on ubi0)
Type:        static
Alignment:   1
Size:        67 LEBs (8507392 bytes, 8.1 MiB)
Data bytes:  4141997 bytes (3.9 MiB)
State:       OK
Name:        kernel
Character device major/minor: 241:3

Volume ID:   3 (on ubi0)
Type:        static
Alignment:   1
Size:        265 LEBs (33648640 bytes, 32.0 MiB)
Data bytes:  27918336 bytes (26.6 MiB)
State:       OK
Name:        rootfs
Character device major/minor: 241:4

Volume ID:   4 (on ubi0)
Type:        static
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
Data bytes:  131 bytes
State:       OK
Name:        firmware-info
Character device major/minor: 241:5

Volume ID:   5 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        83 LEBs (10539008 bytes, 10.0 MiB)
State:       OK
Name:        rootfs_data
Character device major/minor: 241:6

Volume ID:   6 (on ubi0)
Type:        static
Alignment:   1
Size:        67 LEBs (8507392 bytes, 8.1 MiB)
Data bytes:  4141511 bytes (3.9 MiB)
State:       OK
Name:        kernel.b
Character device major/minor: 241:7

Volume ID:   7 (on ubi0)
Type:        static
Alignment:   1
Size:        265 LEBs (33648640 bytes, 32.0 MiB)
Data bytes:  27918336 bytes (26.6 MiB)
State:       OK
Name:        rootfs.b
Character device major/minor: 241:8

Volume ID:   8 (on ubi0)
Type:        static
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
Data bytes:  131 bytes
State:       OK
Name:        firmware-info.b
Character device major/minor: 241:9

Volume ID:   9 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        83 LEBs (10539008 bytes, 10.0 MiB)
State:       OK
Name:        rootfs_data.b
Character device major/minor: 241:10

Volume ID:   10 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        17 LEBs (2158592 bytes, 2.0 MiB)
State:       OK
Name:        log
Character device major/minor: 241:11

Volume ID:   11 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        17 LEBs (2158592 bytes, 2.0 MiB)
State:       OK
Name:        log.b
Character device major/minor: 241:12

Volume ID:   12 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        3 LEBs (380928 bytes, 372.0 KiB)
State:       OK
Name:        extra-para
Character device major/minor: 241:13

Volume ID:   13 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        3 LEBs (380928 bytes, 372.0 KiB)
State:       OK
Name:        extra-para.b
Character device major/minor: 241:14

Volume ID:   14 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        device-info
Character device major/minor: 241:15

Volume ID:   15 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        device-info.b
Character device major/minor: 241:16

Volume ID:   16 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        tddp
Character device major/minor: 241:17

Volume ID:   17 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        tddp.b
Character device major/minor: 241:18

Volume ID:   18 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        83 LEBs (10539008 bytes, 10.0 MiB)
State:       OK
Name:        database

Currently trying to build an image for this (thankfully, it seems like ~8 MB is available for the kernel), and I'll update this as necessary. Seems like the same process would work given the similarity in TP-Link's firmware (both kernel and kernel.b exist as well, which confirms that the recovery partition is also present on this router).

Edit: Seems like a new target is needed for mvebu/cortexa72 (board is using a Marvell's CN913x series SOC).