Hi any quick advice would be appreciated. I assume as this is basically openwrt, I can just flash the sysupgrade package to move to this from the official gl.iNet version? Also can I do this via the gui normal login or do I need to do it via u boot?
Immortal is running 23.05.4, substantially newer than the official 21.02. Would this possibly cause further complications…..
Thanks 
sysupgrade, and do not save settings.
I've upgraded via gui normal login.
What complications are you expecting?
Hi
Well you never know
You’ve upgraded to Immortal? How have you found it on Brume 2, especially compared with gl.iNet official? And English language is picked up by default? I was concerned about that.
default is English. I do not have the WAN issue as I do with the stock firmware.
Ok thanks sounds really positive then. I’ll flash it when I get a chance. Thanks
Hi Hecatae I assume the standard gui Luci is installed by default unlike snapshot images? Also does the ppoe gui interface work ok? Thanks!
PPPoE works fine, luci light is included.
Built my own copy just to check the build manifest.
Sooooo
I installed Immortal,nice and fast but I had issues. My set up is fibre modem into brume2 and then Brume to Orbi mesh system in AP mode. This works fine on gl.iNet official. Ppoe worked perfectly when I installed Immortal and had the wan plugged into my laptop. But when I plugged the wan into the wan port of my Orbi there was no internet. I checked Luci settings on gl.iNet official before I installed Immortal and all seemed the same. I recreated the same interfaces. After a few hours mucking about and the wife getting annoyed I’d taken the internet down - lol - I reinstalled gl.iNet official via uboot. Not sure what I did wrong- frustrating!!!
Can check the syslog of the Immortal, what logs print about the PPPoE process
do the Brume 2 immortalwrt LAN and the Orbi LAN clash?
immortalwrt default LAN subnet is 192.168.1.0/24
Tue Oct 22 20:56:56 2024 daemon.notice netifd: Network device 'eth0' link is up
Tue Oct 22 20:56:56 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Oct 22 20:56:56 2024 daemon.notice netifd: Interface 'wan' is setting up now
Tue Oct 22 20:56:56 2024 kern.info kernel: [ 156.472358] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off
Tue Oct 22 20:56:56 2024 kern.info kernel: [ 156.472372] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Oct 22 20:56:56 2024 daemon.notice netifd: wan (3719): uci: Entry not found
Tue Oct 22 20:56:56 2024 daemon.notice netifd: wan (3719): sh: out of range
Tue Oct 22 20:56:56 2024 daemon.info pppd[3726]: Plugin pppoe.so loaded.
Tue Oct 22 20:56:56 2024 daemon.info pppd[3726]: PPPoE plugin from pppd 2.4.9
Tue Oct 22 20:56:56 2024 daemon.notice pppd[3726]: pppd 2.4.9 started by root, uid 0
Tue Oct 22 20:56:56 2024 daemon.info pppd[3726]: PPP session is 16
Tue Oct 22 20:56:56 2024 daemon.warn pppd[3726]: Connected to 4e:96:14:6a:42:ed via interface eth0
Tue Oct 22 20:56:56 2024 kern.info kernel: [ 156.762908] pppoe-wan: renamed from ppp0
Tue Oct 22 20:56:56 2024 daemon.info pppd[3726]: Renamed interface ppp0 to pppoe-wan
Tue Oct 22 20:56:56 2024 daemon.info pppd[3726]: Using interface pppoe-wan
Tue Oct 22 20:56:56 2024 daemon.notice pppd[3726]: Connect: pppoe-wan <--> eth0
Tue Oct 22 20:56:59 2024 daemon.info pppd[3726]: syncppp not active
Tue Oct 22 20:57:00 2024 daemon.info pppd[3726]: CHAP authentication succeeded
Tue Oct 22 20:57:00 2024 daemon.notice pppd[3726]: CHAP authentication succeeded
Hostname ImmortalWrt
Model GL.iNet GL-MT2500
Architecture ARMv8 Processor rev 4 (v8l) x 2
Temperature CPU: 61.0°C
Target Platform mediatek/filogic
Firmware Version ImmortalWrt 23.05-SNAPSHOT r28081-f213890acd / LuCI openwrt-23.05 branch git-24.282.22181-65e5852
Kernel Version 5.15.167
Local Time 2024-10-23 01:38:05
Uptime 0h 4m 50s
Load Average 0.02, 0.05, 0.02
CPU usage (%) 5%
Here's a fresh reboot of Immortalwrt on the Brume 2:
[ 10.027645] mtk_soc_eth 15100000.ethernet eth0: Link is Down
[ 10.079525] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:00] driver [MediaTek MT7981 PHY] (irq=POLL)
[ 10.094377] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/gmii link mode
[ 10.117340] br-lan: port 1(eth1) entered blocking state
[ 10.122601] br-lan: port 1(eth1) entered disabled state
[ 10.128015] device eth1 entered promiscuous mode
[ 10.145603] mtk_soc_eth 15100000.ethernet eth0: PHY [mdio-bus:05] driver [Maxlinear Ethernet GPY211C] (irq=POLL)
[ 10.155822] mtk_soc_eth 15100000.ethernet eth0: configuring for phy/2500base-x link mode
[ 14.312563] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off
[ 14.312578] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 14.743408] pppoe-wan: renamed from ppp0
[ 16.392614] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 16.401085] br-lan: port 1(eth1) entered blocking state
[ 16.406322] br-lan: port 1(eth1) entered forwarding state
[ 16.412082] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Comes up straight away, unlike 4.6.4 or 4.7 actual GL stock firmware.
Tue Oct 22 20:56:58 2024 daemon.notice netifd: Network device 'eth0' link is up
Tue Oct 22 20:56:58 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Oct 22 20:56:58 2024 daemon.notice netifd: Interface 'wan' is setting up now
Tue Oct 22 20:56:58 2024 kern.info kernel: [ 14.312563] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off
Tue Oct 22 20:56:58 2024 kern.info kernel: [ 14.312578] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Oct 22 20:56:58 2024 daemon.notice netifd: wan (2515): uci: Entry not found
Tue Oct 22 20:56:58 2024 daemon.notice netifd: wan (2515): sh: out of range
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: Plugin pppoe.so loaded.
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: PPPoE plugin from pppd 2.4.9
Tue Oct 22 20:56:58 2024 daemon.notice pppd[2522]: pppd 2.4.9 started by root, uid 0
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: PPP session is 16
Tue Oct 22 20:56:58 2024 daemon.warn pppd[2522]: Connected to 4e:96:14:6a:42:ed via interface eth0
Tue Oct 22 20:56:58 2024 kern.info kernel: [ 14.743408] pppoe-wan: renamed from ppp0
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: Renamed interface ppp0 to pppoe-wan
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: Using interface pppoe-wan
Tue Oct 22 20:56:58 2024 daemon.notice pppd[2522]: Connect: pppoe-wan <--> eth0
Tue Oct 22 20:56:58 2024 daemon.info pppd[2522]: syncppp not active
Tue Oct 22 20:56:59 2024 daemon.info pppd[2522]: CHAP authentication succeeded
Tue Oct 22 20:56:59 2024 daemon.notice pppd[2522]: CHAP authentication succeeded
So I'm at a loss as the mt2500 hardware is not the issue but the rubbish 21.02 SDK that the GL firmware is based on.
Tue Oct 22 20:56:52 2024 kern.err kernel: [ 0.863301] mtk_soc_eth 15100000.ethernet: generated random MAC address 5a:d3:64:13:5e:ff
Tue Oct 22 20:56:52 2024 kern.err kernel: [ 0.871524] mtk_soc_eth 15100000.ethernet: generated random MAC address 4a:e3:b8:00:29:f9
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 0.924859] Maxlinear Ethernet GPY211C mdio-bus:05: Firmware Version: 0x886F (release)
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 0.935715] mtk_soc_eth 15100000.ethernet eth0: mediatek frame engine at 0xffffffc009380000, irq 82
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 0.945627] mtk_soc_eth 15100000.ethernet eth1: mediatek frame engine at 0xffffffc009380000, irq 82
Is that Maxlinear Firmware Version the same as in the stock firmware?
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.106049] mmc0: new high speed MMC card at address 0001
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.112517] mmcblk0: mmc0:0001 8GTF4R 7.28 GiB
Tue Oct 22 20:56:52 2024 kern.warn kernel: [ 1.119044] GPT:Primary header thinks Alt. header is not at the end of the disk.
Tue Oct 22 20:56:52 2024 kern.warn kernel: [ 1.126450] GPT:1 != 15269887
Tue Oct 22 20:56:52 2024 kern.warn kernel: [ 1.129406] GPT:Alternate GPT header not at the end of the disk.
Tue Oct 22 20:56:52 2024 kern.warn kernel: [ 1.135400] GPT:1 != 15269887
Tue Oct 22 20:56:52 2024 kern.warn kernel: [ 1.138355] GPT: Use GNU Parted to correct GPT errors.
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.143505] mmcblk0: p1 p2 p3 p4 p5 p6
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.148730] mmcblk0boot0: mmc0:0001 8GTF4R 4.00 MiB
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.154891] mmcblk0boot1: mmc0:0001 8GTF4R 4.00 MiB
Tue Oct 22 20:56:52 2024 kern.info kernel: [ 1.160172] mmcblk0rpmb: mmc0:0001 8GTF4R 512 KiB, chardev (251:0)
Can someone advise on the GPT error.
Sorry I am not quite knowing this comparison. May I know if the PPPoE/WAN connection of the Immortalwrt better than the OpenWRT 2102?
@bruce I do not need to do this with Immortalwrt on the Brume 2, but I do on stock GL 4.6.4 and 4.7
So, there's something changed between the versions.
Still running fine.
Fixed the gpt alternate header issue by running:
fdisk /dev/mmcblk0
w
reboot
Let's check the script of PPPoE dial of the OpenWRT 2102
@hecatae is right!
Ok,
How shall we do this?