RT-AC87u firmware:384.9 - strange device on device list

[TuxLama]

Hi,
and thank you very much for yours fantastic job,

After updating to 384.9 firmware , i have a strange device connected to my router,
Edited - images don't show up

ASUS
169.254.39.251 
1C:B7:2C:C0:F4:F4

digging a bit the same device show up in ssh client, "ifconfig"

admin@RT-AC87U-CM:/tmp/home/root# ifconfig
br0       Link encap:Ethernet  HWaddr 1C:B7:2C:C0:F4:F0
          inet addr:192.168.58.1  Bcast:192.168.58.255  Mask:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:93477 errors:0 dropped:0 overruns:0 frame:0
          TX packets:133738 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12142068 (11.5 MiB)  TX bytes:80161667 (76.4 MiB)

br0:0     Link encap:Ethernet  HWaddr 1C:B7:2C:C0:F4:F0
          inet addr:169.254.39.247  Bcast:169.254.39.255  Mask:255.255.255.0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr D8:50:E6:4F:FF:C0
          inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:xxx.xxx.xxx.xxx
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2545762 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2573418 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3249514410 (3.0 GiB)  TX bytes:3299228245 (3.0 GiB)
          Interrupt:180 Base address:0x5000

eth1      Link encap:Ethernet  HWaddr 1C:B7:2C:C0:F4:F0
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:5029 errors:0 dropped:0 overruns:0 frame:763
          TX packets:22735 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:664241 (648.6 KiB)  TX bytes:11979761 (11.4 MiB)
          Interrupt:163

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:1851 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1851 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:263046 (256.8 KiB)  TX bytes:263046 (256.8 KiB)

tun21     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.20.40.1  P-t-P:10.20.40.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan1     Link encap:Ethernet  HWaddr 1C:B7:2C:C0:F4:F0
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:376834 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134604 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:37318304 (35.5 MiB)  TX bytes:80562408 (76.8 MiB)

vlan2     Link encap:Ethernet  HWaddr 1C:B7:2C:C0:F4:F0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

however in different MAC addressees,
First i do "factory default", and apply saved config file, did not help.
nvram show | grep F4:F4

admin@RT-AC87U-CM:/tmp/home/root# nvram show | grep F4:F4
wl1_hwaddr=1C:B7:2C:C0:F4:F4
1:macaddr=1C:B7:2C:C0:F4:F4
wl_hwaddr=1C:B7:2C:C0:F4:F4
wl0.4_hwaddr=1E:B7:2C:C0:F4:F4
size: 51516 bytes (14020 left)

seems like this is a router interface, and i find it at "Wireless ->WDS-> Basic config"
First, it is a bug or my router configuration mistake/error ?Second, it is way to fix this ?

..Thanks

 

[ColinTaylor]

I believe it's the internal network connection to the Quantenna WiFi.

 

[skeal]

I second what @ColinTaylor says. This is an Asus thing. Not sure there is, or needs to be, a fix for it, but this is normal for that router.

 

[roguetr]

https://www.snbforums.com/threads/identifying-ac87-interfaces.21356/#post-155217

Sent from MI 5 running Pixel Experience

 

[TuxLama]

Well, it's newer show before 384.9 firmware, actually i will try full reset with "clear nvram ", i will post result.
Btw: how i can backup OpenVPN server settings and apply it after doing reset? manually copy key's or it is a better way?

 

[roguetr]

Well, it's newer show before 384.9 firmware, actually i will try full reset with "clear nvram ", i will post result.
Btw: how i can backup OpenVPN server settings and apply it after doing reset? manually copy key's or it is a better way?

It may just be that the interface wasn't previously configured. It appears it's all controlled by nvram variables.

Sent from MI 5 running Pixel Experience

 

[TuxLama]

Looks like this happened exactly after upgrading to 384.9 version. The router works normal - so far, but this strange device magically become after flashing to latest build.

"on connected device list"
    
ASUS
    
169.254.39.251   
1C:B7:2C:C0:F4:F4

What i do is revert to Asus original latest build from support page, reset nvram, perform basic configuration and every thing looks right, no "Asus" device on list.
Next, flashed Merlin firmware ver. 384.7_2, reboot and again, every thing looks right, no "Asus" device on list.
Next, flashed Merlin firmware ver. 384.9 reboot, and ....(dam..) again i got Asus device.

Interestingly, nvram variables for original Asus firmware and Merlin looks the same, on this area, "nvram show | grep F4:F4"

Asus RT-AC87U firmware 3.0.0.4.382_50702-g6c0e289

admincm@RT-AC87U:/tmp/home/root# nvram show | grep F4:F4
wl1_hwaddr=1C:B7:2C:C0:F4:F4
size: 42594 bytes (22942 left)
1:macaddr=1C:B7:2C:C0:F4:F4
wl0.4_hwaddr=1E:B7:2C:C0:F4:F4

ASUSWRT-Merlin RT-AC87U firmware 384.9

admincm@RT-AC87U-F4F0:/tmp/home/root# nvram show | grep F4:F4
wl1_hwaddr=1C:B7:2C:C0:F4:F4
1:macaddr=1C:B7:2C:C0:F4:F4
size: 50774 bytes (14762 left)
wl0.4_hwaddr=1E:B7:2C:C0:F4:F4

and ...I can live with this device , or maybe i will revert to 384.7_2 build, if this make me tired

..Thanks

 

[roguetr]

Maybe it's the server_ipaddr that triggers configuration. You'd assume the device should be listed in dmesg for all versions.

Considering it's a known device for your model, I wouldn't think there's any reason to worry that it's being listed.

Sent from MI 5 running Pixel Experience

 

[RMerlin]

Just ignore it, it's simply the Quantenna system running inside the RT-AC87U, and connected to the Broadcom system over an internal switch port.

 

[pcmarc]

Got same problem after upgrading above 384.7_2.
But all is working fine

 

[skeal]

Got same problem after upgrading above 384.7_2.
But all is working fine

This is not a problem, it is what @RMerlin said above. This is a hardware difference from other devices.

 

[CapricornDog]

Would this be why all my devices connected on the 5ghz band show in the network map as being connected via a cable?

 

[El Mariachi]

Yea its happening on my 87U as well. Nothing to worry about.

@CapricornDog maybe but in other threads @RMerlin conveyed that this was a bug introduced by some Asus code changes some time ago and not within the scope of his project to correct. Awaiting for an Asus fix as it is part of the closed source code.