Open Testing7B opened 4 years ago
It works well. Did you perform a factory reset?
Yes, I did. Nevermind, looking forward to your build based on 46468, bring it on!
This is indeed a bug. I will try to fix it. It seems to happen only once before factory reset
[Mastiff]init start_wan: start_wan_if(0)! [1 init:start_wan_if +37] unit=0. update_wanstate(wan0, 0, 0) convert_wannvram(wan0) ** wan_ifname: eth1 is NOT UP _ifconfig: name=eth1 flags=1043 IFUP addr= netmask= update_wanstate(wan0, 1, 0) start_wan_if(0x067e): ifup:eth1 set_hwaddr: error setting MAC address of eth1 to 68:DB:54:E4:95:D6 _ifconfig: name=eth1 flags=1043 IFUP addr= netmask= start_wan_if(0x0682): start auth:0 start_auth:: done start_wan_if(0x068c): start udhcpc:eth1, 0 start_wan_if(): End. udhcpc_wan:: deconfig set_hwaddr: error setting MAC address of eth1 to 68:DB:54:E4:95:D6 _ifconfig: name=eth1 flags=1043 IFUP addr=0.0.0.0 netmask= wan_down(eth1) wan_down(eth1): . stop_auth:: done route_manip: cmd=DEL name=eth1 addr=0.0.0.0 netmask=0.0.0.0 gateway=(null) metric=0 update_wanstate(wan0, 3, 0) start_usb [disable_ppa_wan][3928] ppacmd delwan -i eth1 update_wanstate(wan0, 4, 3) udhcpc:: deconfig done udhcpc_wan:: bound set_hwaddr: error setting MAC address of eth1 to 68:DB:54:E4:95:D6 _ifconfig: name=eth1 flags=1043 IFUP addr=0.0.0.0 netmask= set_hwaddr: error setting MAC address of eth1 to 68:DB:54:E4:95:D6 _ifconfig: name=eth1 flags=1043 IFUP addr=192.168.50.156 netmask=255.255.255.0 wan_up(eth1) update_wanstate(wan0, 2, 0) writting prerouting eth1 192.168.50.156 eth1 0.0.0.0 br0 192.168.51.1 Couldn't get the enabled rules of Parental-control correctly! nat_rule: skip nat_rules because of no PHY. [1912 udhcpc:filter_setting +38] write porttrigger NO default route!!!
@paldier is this Beta version BLUECAVE_R5.1.1-gc693e81.trx include the fixes for Issue #11? Beta firmware BLUECAVE_R5.1.1-gf0c1f0a.trx does not solve the Issue #11 .If include the fixes #11 , i will upgrade my router and test it out also. Thanks for the advice
@chongaik3 you can try it
I have reported it to asus, another bug, the WAN is connected but it shows not connected,just like broadcom.
New firmware is out version 9.0.0.4.384_46629, website gives a different version though, hopefully it will fix this issue ...
Hi! Asus 3.0.0.4.384.46468 firmware has WAN reconnection bug when using PPPoE as described here: https://www.snbforums.com/threads/issues-with-latest-blue-cave-firmware.62959/ Any chance you could check and fix it in your upcoming release?