Have been running my brand new Asus RTAX68 router now for a few days as part of setting up my BI system.......was running COmcasts gateway modem/router, went with this for better security and VPN capability.
WIFI was fine up til about two hours or so ago when I saw my phone wasnt connected to WIFI.....looked at the router page and 2.5ghz was working, 5 ghz was not.
Ended up rebooting the router and it came back....
But I was curious as to what happened so I looked at the system log.
I keep getting one message over and over
"miniupnpd[3641]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address"
I panicked -- "Is this a hacker trying to get in? Or some setting I screwed up?". Posted here initially and then kept working on it, so I have edited this thread a jillion times...LOL
I saved the log and then cleared it.....the errors started again......but then after many of the same ones, THIS came up:
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(527): eth5: Auth E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(556): eth5: Assoc E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:52 kernel: wl1: random key value: FE0124DD41CCB4D93FBC0110DC272D19903649A1DBFE0380ABB1264EDEF94281
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:56 kernel: wl0: random key value: 0A81165C94AD850C54EE02B05D5246D1F0B91C8470FD06A2E2D4CCC2EAF660A4
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind E4:F0:42:84:B0:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(527): eth6: Auth E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(508): eth5: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(556): eth6: Assoc E4:F0:42:84:B0:74, status: Successful (0), rssi:0
The "E4" stuff appears to be my chromecast for TV.....so I guess that is legit....
But then , the same error messages starts all over again....
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
It continues with BI shut down....
Based on some googling, I deduced this is a device on my network trying to get out...
Looking around, it seems my WD Cloud drive has the last 6 digits in its MAC address (from the label on it).....figured that was it, so I disconnected the lan cable on it and cleared the log.....no more errors.....sooooooooooo.............finally figured it out.
I think I read somewhere that this is a known issue with the WD drives.......and not a problem.....but it still freaks me out seeing all those errors.
And you would think that all that extra traffic isnt great right?
Anyone have any comment here as far as the WD constantly seeking that connection? Or can I just leave it alone and live with the thousands of error messages?
WIFI was fine up til about two hours or so ago when I saw my phone wasnt connected to WIFI.....looked at the router page and 2.5ghz was working, 5 ghz was not.
Ended up rebooting the router and it came back....
But I was curious as to what happened so I looked at the system log.
I keep getting one message over and over
"miniupnpd[3641]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address"
I panicked -- "Is this a hacker trying to get in? Or some setting I screwed up?". Posted here initially and then kept working on it, so I have edited this thread a jillion times...LOL
I saved the log and then cleared it.....the errors started again......but then after many of the same ones, THIS came up:
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(527): eth5: Auth E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(556): eth5: Assoc E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:52 kernel: wl1: random key value: FE0124DD41CCB4D93FBC0110DC272D19903649A1DBFE0380ABB1264EDEF94281
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:52 wlceventd: wlceventd_proc_event(508): eth6: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:56 kernel: wl0: random key value: 0A81165C94AD850C54EE02B05D5246D1F0B91C8470FD06A2E2D4CCC2EAF660A4
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind E4:F0:42:84:B0:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(527): eth6: Auth E4:F0:42:84:B0:74, status: Successful (0), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(508): eth5: Disassoc E4:F0:42:84:B0:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 28 22:15:56 wlceventd: wlceventd_proc_event(556): eth6: Assoc E4:F0:42:84:B0:74, status: Successful (0), rssi:0
The "E4" stuff appears to be my chromecast for TV.....so I guess that is legit....
But then , the same error messages starts all over again....
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
Mar 28 22:16:18 miniupnpd[1530]: Failed to convert hostname 'fe80::290:a9ff:fed7:4ca8' to ip address
It continues with BI shut down....
Based on some googling, I deduced this is a device on my network trying to get out...
Looking around, it seems my WD Cloud drive has the last 6 digits in its MAC address (from the label on it).....figured that was it, so I disconnected the lan cable on it and cleared the log.....no more errors.....sooooooooooo.............finally figured it out.
I think I read somewhere that this is a known issue with the WD drives.......and not a problem.....but it still freaks me out seeing all those errors.
And you would think that all that extra traffic isnt great right?
Anyone have any comment here as far as the WD constantly seeking that connection? Or can I just leave it alone and live with the thousands of error messages?
Last edited: