OpenWrt v19.07.7
OpenWrt v19.07.7
As we have VMware version running in test, we also making 1st new P-2812HNU-F1 version.
Tor latest version 4.5.6.
We have to check with older versions as we have made new build environment.
After which we can destroy old virtual LD861(2) machine.
DG.
Tor latest version 4.5.6.
We have to check with older versions as we have made new build environment.
After which we can destroy old virtual LD861(2) machine.
DG.
Re: OpenWrt v19.07.7
Manifest list:
We removed the following packages:
Default RT3062.eeprom file (files/lib/firmware folder) not yet implemented.
Multi-language should be implemented.
DG.
Code: Select all
base-files - 204.2-r11306-c4a6851c72
block-mount - 2020-05-12-84269037-1
blockd - 2020-05-12-84269037-1
br2684ctl - 2.5.2-7
bspatch - 4.3-1
busybox - 1.30.1-6
ca-bundle - 20200601-1
cgi-io - 19
collectd - 5.12.0-1
collectd-mod-cpu - 5.12.0-1
collectd-mod-interface - 5.12.0-1
collectd-mod-iwinfo - 5.12.0-1
collectd-mod-load - 5.12.0-1
collectd-mod-memory - 5.12.0-1
collectd-mod-network - 5.12.0-1
collectd-mod-rrdtool - 5.12.0-1
dnsmasq - 2.80-16.3
dosfstools - 4.1-4
dropbear - 2019.78-2
dsl-vrx200-firmware-xdsl-a - 05.08.01.08.01.06_05.08.00.0B.01.01_osc-1
dsl-vrx200-firmware-xdsl-a-patch - 05.08.01.08.01.06_05.08.00.0B.01.01_osc-1
dsl-vrx200-firmware-xdsl-b - 05.08.01.08.01.06_05.08.00.0B.01.01_osc-1
dsl-vrx200-firmware-xdsl-b-patch - 05.08.01.08.01.06_05.08.00.0B.01.01_osc-1
e2fsprogs - 1.44.5-2
ethtool - 5.2-1
f2fs-tools - 1.12.0-3
f2fsck - 1.12.0-3
fdisk - 2.34-1
firewall - 2019-11-22-8174814a-3
fixparts - 1.0.4-2
fstools - 2020-05-12-84269037-1
fwtool - 2
getrandom - 2019-06-16-4df34a4d-3
hostapd-common - 2019-08-08-ca8c2bd2-5
hostapd-openssl - 2019-08-08-ca8c2bd2-5
htop - 3.0.5-1
htpdate - 1.1.1-4
ip6tables - 1.8.3-1
iptables - 1.8.3-1
iw - 5.0.1-1
iwinfo - 2019-10-16-07315b6f-1
jshn - 2020-05-25-66195aee-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.14.221-1-42b6079e72033723f2121ec4d4ac28b4
kmod-atm - 4.14.221-1
kmod-cfg80211 - 4.14.221+4.19.161-1-1
kmod-crypto-aead - 4.14.221-1
kmod-crypto-crc32 - 4.14.221-1
kmod-crypto-crc32c - 4.14.221-1
kmod-crypto-des - 4.14.221-1
kmod-crypto-ecb - 4.14.221-1
kmod-crypto-hash - 4.14.221-1
kmod-crypto-hmac - 4.14.221-1
kmod-crypto-manager - 4.14.221-1
kmod-crypto-md4 - 4.14.221-1
kmod-crypto-md5 - 4.14.221-1
kmod-crypto-null - 4.14.221-1
kmod-crypto-pcompress - 4.14.221-1
kmod-crypto-sha256 - 4.14.221-1
kmod-eeprom-93cx6 - 4.14.221-1
kmod-fs-autofs4 - 4.14.221-1
kmod-fs-ext4 - 4.14.221-1
kmod-fs-f2fs - 4.14.221-1
kmod-fs-vfat - 4.14.221-1
kmod-gpio-button-hotplug - 4.14.221-3
kmod-input-core - 4.14.221-1
kmod-ip6tables - 4.14.221-1
kmod-ipt-conntrack - 4.14.221-1
kmod-ipt-core - 4.14.221-1
kmod-ipt-nat - 4.14.221-1
kmod-ipt-offload - 4.14.221-1
kmod-leds-gpio - 4.14.221-1
kmod-ledtrig-default-on - 4.14.221-1
kmod-ledtrig-heartbeat - 4.14.221-1
kmod-ledtrig-netdev - 4.14.221-1
kmod-ledtrig-timer - 4.14.221-1
kmod-lib-crc-ccitt - 4.14.221-1
kmod-lib-crc-itu-t - 4.14.221-1
kmod-lib-crc16 - 4.14.221-1
kmod-ltq-atm-vr9 - 4.14.221-2
kmod-ltq-deu-vr9 - 4.14.221-1
kmod-ltq-ifxos - 4.14.221+1.5.19-4
kmod-ltq-ptm-vr9 - 4.14.221-2
kmod-ltq-vdsl-vr9 - 4.14.221+4.17.18.6-3
kmod-ltq-vdsl-vr9-mei - 4.14.221+1.5.17.6-4
kmod-mac80211 - 4.14.221+4.19.161-1-1
kmod-nf-conntrack - 4.14.221-1
kmod-nf-conntrack6 - 4.14.221-1
kmod-nf-flow - 4.14.221-1
kmod-nf-ipt - 4.14.221-1
kmod-nf-ipt6 - 4.14.221-1
kmod-nf-nat - 4.14.221-1
kmod-nf-reject - 4.14.221-1
kmod-nf-reject6 - 4.14.221-1
kmod-nls-base - 4.14.221-1
kmod-nls-cp437 - 4.14.221-1
kmod-nls-iso8859-1 - 4.14.221-1
kmod-nls-utf8 - 4.14.221-1
kmod-ppp - 4.14.221-1
kmod-pppoa - 4.14.221-1
kmod-pppoe - 4.14.221-1
kmod-pppox - 4.14.221-1
kmod-rt2800-lib - 4.14.221+4.19.161-1-1
kmod-rt2800-mmio - 4.14.221+4.19.161-1-1
kmod-rt2800-pci - 4.14.221+4.19.161-1-1
kmod-rt2x00-lib - 4.14.221+4.19.161-1-1
kmod-rt2x00-mmio - 4.14.221+4.19.161-1-1
kmod-rt2x00-pci - 4.14.221+4.19.161-1-1
kmod-scsi-core - 4.14.221-1
kmod-slhc - 4.14.221-1
kmod-sound-core - 4.14.221-1
kmod-tun - 4.14.221-1
kmod-usb-audio - 4.14.221-1
kmod-usb-core - 4.14.221-1
kmod-usb-dwc2 - 4.14.221-1
kmod-usb-ehci - 4.14.221-1
kmod-usb-ledtrig-usbport - 4.14.221-1
kmod-usb-ohci - 4.14.221-1
kmod-usb-printer - 4.14.221-1
kmod-usb-storage - 4.14.221-1
kmod-usb-storage-extras - 4.14.221-1
kmod-usb-storage-uas - 4.14.221-1
kmod-usb-uhci - 4.14.221-1
kmod-usb2 - 4.14.221-1
kmod-usb3 - 4.14.221-1
kmod-usbmon - 4.14.221-1
libblkid1 - 2.34-1
libblobmsg-json - 2020-05-25-66195aee-1
libbz2-1.0 - 1.0.8-1
libc - 1.1.24-2
libcap - 2.27-1
libcomerr0 - 1.44.5-2
libevent2-7 - 2.1.11-1
libext2fs2 - 1.44.5-2
libf2fs6 - 1.12.0-3
libfdisk1 - 2.34-1
libgcc1 - 7.5.0-2
libip4tc2 - 1.8.3-1
libip6tc2 - 1.8.3-1
libiwinfo-lua - 2019-10-16-07315b6f-1
libiwinfo20181126 - 2019-10-16-07315b6f-1
libjson-c2 - 0.12.1-3.1
libjson-script - 2020-05-25-66195aee-1
liblo - 0.30-2
libltdl7 - 2.4.6-2
liblua5.1.5 - 5.1.5-3
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
liblzo2 - 2.10-2
libncurses6 - 6.1-5
libnl-tiny - 0.1-5
libopenssl-conf - 1.1.1i-1
libopenssl1.1 - 1.1.1i-1
libpcap1 - 1.9.1-2.1
libpcre - 8.43-1
libpthread - 1.1.24-2
librrd1 - 1.0.50-3
librt - 1.1.24-2
libsmartcols1 - 2.34-1
libss2 - 1.44.5-2
libubox20191228 - 2020-05-25-66195aee-1
libubus-lua - 2019-12-27-041c9d1c-1
libubus20191227 - 2019-12-27-041c9d1c-1
libuci20130104 - 2019-09-01-415f9e48-4
libuclient20160123 - 2020-06-17-51e16ebf-1
libusb-1.0-0 - 1.0.22-2
libustream-openssl20150806 - 2020-03-13-40b563b1-1
libuuid1 - 2.34-1
libxtables12 - 1.8.3-1
linux-atm - 2.5.2-7
logd - 2019-06-16-4df34a4d-3
lscpu - 2.34-1
ltq-vdsl-app - 4.17.18.6-2
ltq-vdsl-vr9-vectoring-fw-installer - 6.8.6-3
lua - 5.1.5-3
luci - git-21.044.30835-34e0d65-1
luci-app-commands - git-21.044.30835-34e0d65-1
luci-app-firewall - git-21.044.30835-34e0d65-1
luci-app-openvpn - git-21.044.30835-34e0d65-1
luci-app-opkg - git-21.044.30835-34e0d65-1
luci-app-p910nd - git-21.044.30835-34e0d65-1
luci-app-privoxy - 1.0.6-2
luci-app-statistics - git-21.044.30835-34e0d65-1
luci-app-transmission - git-21.044.30835-34e0d65-1
luci-app-wifischedule - git-21.044.30835-34e0d65-1
luci-base - git-21.044.30835-34e0d65-1
luci-compat - git-21.044.30835-34e0d65-1
luci-lib-ip - git-21.044.30835-34e0d65-1
luci-lib-ipkg - git-21.044.30835-34e0d65-1
luci-lib-iptparser - git-21.044.30835-34e0d65-1
luci-lib-jsonc - git-21.044.30835-34e0d65-1
luci-lib-nixio - git-21.044.30835-34e0d65-1
luci-mod-admin-full - git-21.044.30835-34e0d65-1
luci-mod-network - git-21.044.30835-34e0d65-1
luci-mod-status - git-21.044.30835-34e0d65-1
luci-mod-system - git-21.044.30835-34e0d65-1
luci-proto-ipv6 - git-21.044.30835-34e0d65-1
luci-proto-ppp - git-21.044.30835-34e0d65-1
luci-ssl-openssl - git-21.044.30835-34e0d65-1
luci-theme-bootstrap - git-21.044.30835-34e0d65-1
mkf2fs - 1.12.0-3
mtd - 24
nano - 5.5-1
netifd - 2021-01-09-753c351b-1
odhcp6c - 2021-01-09-64e1b4e7-16
odhcpd-ipv6only - 2020-05-03-49e4949c-3
openssl-util - 1.1.1i-1
openvpn-easy-rsa - 3.0.4-1
openvpn-openssl - 2.4.7-2
openwrt-keyring - 2019-07-25-8080ef34-1
opkg - 2021-01-31-c5dccea9-1
p910nd - 0.97-8
partx-utils - 2.34-1
ppp - 2.4.7.git-2019-05-25-3
ppp-mod-pppoa - 2.4.7.git-2019-05-25-3
ppp-mod-pppoe - 2.4.7.git-2019-05-25-3
privoxy - 3.0.28-1
procd - 2020-03-07-09b9bd82-1
rpcd - 2020-05-26-67c8a3fd-1
rpcd-mod-file - 2020-05-26-67c8a3fd-1
rpcd-mod-iwinfo - 2020-05-26-67c8a3fd-1
rpcd-mod-luci - 20201107
rpcd-mod-rrdns - 20170710
rrdtool1 - 1.0.50-3
rt2800-pci-firmware - 20190416-1
simple-adblock - 1.8.4-10
spi-tools - 0.8.3-1
swconfig - 12
tcpdump - 4.9.3-2
terminfo - 6.1-5
tor - 0.4.5.6-1
tor-fw-helper - 0.3-1
tor-gencert - 0.4.5.6-1
tor-geoip - 0.4.5.6-1
tor-resolve - 0.4.5.6-1
ubi-utils - 2.1.1-1
ubox - 2019-06-16-4df34a4d-3
ubus - 2019-12-27-041c9d1c-1
ubusd - 2019-12-27-041c9d1c-1
uci - 2019-09-01-415f9e48-4
uclibcxx - 0.2.5-3
uclient-fetch - 2020-06-17-51e16ebf-1
uhttpd - 2020-10-01-3abcc891-1
urandom-seed - 1.0-1
urngd - 2020-01-21-c7f7b6b6-1
usbutils - 007-10
usign - 2020-05-23-f1f65026-1
wifischedule - 1-2
wireless-regdb - 2020.11.20-1
wireless-tools - 29-6
zlib - 1.2.11-3
- coreutils
- coreutils-sort
- luci-app-diag-core
- uhttpd-mod-ubus
- Adblock (any, as it won't work behind Tor)
- f2fs-tools
- fixparts
- kmod-crypto-des
- kmod-crypto-ecb
- kmod-crypto-md4
- kmod-crypto-md5
- kmod-crypto-sha256
- lscpu
- mkf2fs
- partx-utils
- wireless-tools
Default RT3062.eeprom file (files/lib/firmware folder) not yet implemented.
Multi-language should be implemented.
DG.
Re: OpenWrt v19.07.7 & Privoxy
Privoxy, is outdated on OpenWrt ( informed team OpenWrt...)
We try rebuilding TorRouter firmware with Privoxy's source files to 3.0.31 (stable).
Building looks ok, now test on F1 box.
Next build will have the old scripts running, for Tor LED configuration. Although it spams the system logs.
Also sysfixtime has been re-introduced, as it only looks at local file-time-stamp to adjust CRT clock.
This avoids a lot of errors during first boot.
Adjusted files are:
It only starts Tor later during boot.
DG.
We try rebuilding TorRouter firmware with Privoxy's source files to 3.0.31 (stable).
Building looks ok, now test on F1 box.
Next build will have the old scripts running, for Tor LED configuration. Although it spams the system logs.
Also sysfixtime has been re-introduced, as it only looks at local file-time-stamp to adjust CRT clock.
This avoids a lot of errors during first boot.
Adjusted files are:
- /etc/banner2
- /etc/banner2.safe
- /etc/rc.local (adjust DSL and runs htpdate once)
- /etc/sysupgrade.conf (added RT3062.eeprom file for Wifi functionality)
- /etc/crontabs/root (5 minutes check of Tor)
- /etc/init.d/tor (adjust start of Tor during boot -98-)
- /etc/tor/torchk.sh (actual LED adjustment acooriding Tor)
It only starts Tor later during boot.
DG.
Re: OpenWrt v19.07.7
Adjust during build, just before 'make':
- feeds/packages/net/tor/files/tor.init - with START=97 (adjusted, still needed ... sysfixtime works fine for Luci's statistics/collectd )
- package/utils/busybox/files/sysntpd - comment out START and USE_PROCD=0 (sysntpd is gone.)
- feeds/packages/net/htpdate/files/htpdate.conf - & .init adjusted, no more autostart, only run ones in rc.local
Special care about the dev commands in config/network, there are the mac addresses stored (only!) .
Have to check how to read the printenv boot data to use the right mac addresses in OpenWrt. (It does with firstboot command, although only 1 vlan, so no WAN after firstboot.)
DG.
- feeds/packages/net/tor/files/tor.init - with START=97 (adjusted, still needed ... sysfixtime works fine for Luci's statistics/collectd )
- package/utils/busybox/files/sysntpd - comment out START and USE_PROCD=0 (sysntpd is gone.)
- feeds/packages/net/htpdate/files/htpdate.conf - & .init adjusted, no more autostart, only run ones in rc.local
Special care about the dev commands in config/network, there are the mac addresses stored (only!) .
Have to check how to read the printenv boot data to use the right mac addresses in OpenWrt. (It does with firstboot command, although only 1 vlan, so no WAN after firstboot.)
DG.
Re: OpenWrt v19.07.7 & read uboot data
Found out the right specs for uboot-envtools to read the printenv data from uboot.
https://openwrt.org/docs/techref/bootlo ... oot.config
As older firmware needs other settings, it's only available from 19.07.x versions for TorRouter (for now).
Working on a version that also can read older versions.
uboot-envtools enables commands: fw_printenv and fw_setenv.
Both commands need a config file, which points to the right location on mtd.
Using it wrongly can cause the device to be bricked!
fw_env.config:
With this command the (main) mac-address can be read from uboot environment, which holds the right mac per device.
Still eth0 has 'weird' mac address 00:11:22:33:44:55, why not the value of printenv?
For use in future releases.
Until now the mac-addresses were hard-coded within /etc/config/network with lan_dev & wan_dev.
DG.
https://openwrt.org/docs/techref/bootlo ... oot.config
As older firmware needs other settings, it's only available from 19.07.x versions for TorRouter (for now).
Working on a version that also can read older versions.
uboot-envtools enables commands: fw_printenv and fw_setenv.
Both commands need a config file, which points to the right location on mtd.
Using it wrongly can cause the device to be bricked!
fw_env.config:
Code: Select all
# Configuration file for fw_(printenv/setenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR and SPI-dataflash.
# Furthermore, if the Flash sector size is omitted, this value is assumed to
# be the same as the Environment size, which is valid for NOR and SPI-dataflash
# NOR example
# MTD device name Device offset Env. size Flash sector size Number of sectors
#/dev/mtd1 0x0000 0x2000 0x10000
#/dev/mtd2 0x0000 0x4000 0x4000
# MTD SPI-dataflash example
# MTD device name Device offset Env. size Flash sector size Number of sectors
#/dev/mtd5 0x4200 0x4200
#/dev/mtd6 0x4200 0x4200
# NAND example
/dev/mtd1 0x0000 0x2000 0x20000 1
Still eth0 has 'weird' mac address 00:11:22:33:44:55, why not the value of printenv?
For use in future releases.
Until now the mac-addresses were hard-coded within /etc/config/network with lan_dev & wan_dev.
DG.
Re: OpenWrt v19.07.7 & mac addresses
How does OpenWrt uses ethaddr from uboot?
Until now -for several years on a ZyXEL P-2812HNU-F1 device- I do set the mac-addresses manually in /etc/config/network with wan_dev & lan_dev configuration.
Actually the ethaddr is set within first serial break into uboot, but that value is NOT (ever) used by OpenWrt?
And I don't know why not.
When 2 (or more) devices without these wan_dev and lan_dev adjustment are used in 1 network, the most weird issues can occure.
As you have 2 devices with the same mac-address in 1 network (this is not what u want).
See: /phpbb/viewtopic.php?p=241#p241
Now testing with uboot-envtools on OpenWrt, fw_printenv returns the right address (last line):
Only this is not used / or set by OpenWrt:(eth0.2 & wlan0 are hard-coded)
eth0, eth0.1 & br-lan always get 00:11:22:33:44:55 as mac instead of the uboot ethaddr value.
Or you have to override this with the lan_dev configuration.
hexdump returns:
Found out that the ZyXEL P-2812HNU-F1 is not a DT (Device Tree) generic device, as my new Fritz!box 4040 is?
And on the 4040-boxes the mac-addresses are set as desired/required. (no wan_dev or lan_dev needed in /etc/config/network)
For now on the P-2812HNU-F1 boxes location: Where -in the build process?- is the pointing to ethaddr as real value of eth0?
It's not the right one, I presume.
P-2812HNU-F1:
Fritz!box4040:
And the right mac addresses for the 4040-box (in double-word configuration!):
As ifconfig shows on the 4040-box:
DG.
Until now -for several years on a ZyXEL P-2812HNU-F1 device- I do set the mac-addresses manually in /etc/config/network with wan_dev & lan_dev configuration.
Actually the ethaddr is set within first serial break into uboot, but that value is NOT (ever) used by OpenWrt?
And I don't know why not.
When 2 (or more) devices without these wan_dev and lan_dev adjustment are used in 1 network, the most weird issues can occure.
As you have 2 devices with the same mac-address in 1 network (this is not what u want).
See: /phpbb/viewtopic.php?p=241#p241
Now testing with uboot-envtools on OpenWrt, fw_printenv returns the right address (last line):
Code: Select all
addconsole=setenv bootargs $bootargs console=$consoledev,$baudrate
addeth=setenv bootargs $bootargs ethaddr=$ethaddr
addip=setenv bootargs $bootargs ip=$ipaddr:$serverip::::$netdev:off
addmachtype=setenv bootargs $bootargs machtype=P-2812HNU-Fx
baudrate=115200
bootcmd=run nboot
bootdelay=2
consoledev=ttyLTQ1
ethact=ltq-eth
ethaddr=B0:B2:DC:20:56:08
Code: Select all
# ifconfig | grep -e 'HWaddr'
br-lan Link encap:Ethernet HWaddr 00:11:22:33:44:55
eth0 Link encap:Ethernet HWaddr 00:11:22:33:44:55
eth0.1 Link encap:Ethernet HWaddr 00:11:22:33:44:55
eth0.2 Link encap:Ethernet HWaddr B0:B2:DC:20:56:0B
wlan0 Link encap:Ethernet HWaddr B0:B2:DC:20:56:0C
eth0, eth0.1 & br-lan always get 00:11:22:33:44:55 as mac instead of the uboot ethaddr value.
Or you have to override this with the lan_dev configuration.
hexdump returns:
Code: Select all
/# hexdump /proc/device-tree/fpi@10000000/eth@e108000/interface@0/mac-address
0000000 0011 2233 4455
0000006
And on the 4040-boxes the mac-addresses are set as desired/required. (no wan_dev or lan_dev needed in /etc/config/network)
For now on the P-2812HNU-F1 boxes location: Where -in the build process?- is the pointing to ethaddr as real value of eth0?
It's not the right one, I presume.
P-2812HNU-F1:
Code: Select all
/# cat /proc/cpuinfo
system type : xRX200 rev 1.1
machine : ZyXEL P-2812HNU-F1
processor : 0
cpu model : MIPS 34Kc V5.5
BogoMIPS : 332.54
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit nan_legacy nan_2008 perf
shadow register sets : 1
kscratch registers : 0
package : 0
core : 0
VPE : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 1
cpu model : MIPS 34Kc V5.5
BogoMIPS : 333.82
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit nan_legacy nan_2008 perf
shadow register sets : 1
kscratch registers : 0
package : 0
core : 0
VPE : 1
VCED exceptions : not available
VCEI exceptions : not available
Code: Select all
# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 30.37
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 1
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 30.37
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 2
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 30.37
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 3
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 30.37
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
Hardware : Generic DT based system
Revision : 0000
Serial : 0000000000000000
Code: Select all
# find /proc/device-tree/ -name "*mac-address"
/proc/device-tree/soc/edma@c080000/gmac0/local-mac-address
/proc/device-tree/soc/edma@c080000/gmac1/local-mac-address
root@OpenWrt:/# hexdump /proc/device-tree/soc/edma@c080000/gmac0/local-mac-address
0000000 3a2c 23fd ae14
0000006
root@OpenWrt:/# hexdump /proc/device-tree/soc/edma@c080000/gmac1/local-mac-address
0000000 3a2c 23fd af14
0000006
Code: Select all
/# ifconfig | grep -e 'HWaddr'
br-lan Link encap:Ethernet HWaddr 2C:3A:FD:23:14:AE
eth0 Link encap:Ethernet HWaddr 2C:3A:FD:23:14:AE
eth1 Link encap:Ethernet HWaddr 2C:3A:FD:23:14:AF
Re: OpenWrt v19.07.7 & mac address
I followed: https://openwrt.org/docs/guide-developer/mac.address
But some items are not clear for me.
All commands starting ". /lib/functions/system.sh " return nothing to me.
Where -in the build/flash process?- is the pointing to ethaddr (uboot) as real value of eth0?
Found it @ build: target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUFX.dtsi
There is written:
But why is it hard-coded? And why is ethaddr not used from uboot?
After we remove the hard-coded mac address within this .dtsi file: eth0, eth0.1 and br-lan now receive a new mac address every time the router reboots.
Checking further .
Found after firstboot (or an upgrade without 'Keep Settings'), the correct br-lan (eth0.1) mac-address is made, although eth0 keeps mac-address 00:11:22:33:44:55.
Within /etc/config/network a config is made with lan_dev mac-address hardcoded.
Works as desired.
DG.
But some items are not clear for me.
All commands starting ". /lib/functions/system.sh " return nothing to me.
Code: Select all
root@TorRouter-TEST:~# . /lib/functions/system.sh get_mac_binary "/proc/device-tree/fpi@10000000/eth@e108000/interface@0/mac-address:" 0
root@TorRouter-TEST:~#
Found it @ build: target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUFX.dtsi
There is written:
Code: Select all
ð0 {
lan: interface@0 {
compatible = "lantiq,xrx200-pdi";
#address-cells = <1>;
#size-cells = <0>;
reg = <0>;
mac-address = [ 00 11 22 33 44 55 ];
lantiq,switch;
After we remove the hard-coded mac address within this .dtsi file: eth0, eth0.1 and br-lan now receive a new mac address every time the router reboots.
Checking further .
Found after firstboot (or an upgrade without 'Keep Settings'), the correct br-lan (eth0.1) mac-address is made, although eth0 keeps mac-address 00:11:22:33:44:55.
Within /etc/config/network a config is made with lan_dev mac-address hardcoded.
Works as desired.
DG.