Your Universal Remote Control Center
RemoteCentral.com
Custom Installers' Lounge Forum - View Post
Previous section Next section Previous page Next page Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Page 1 of 2
Topic:
Luxul Router Help
This thread has 16 replies. Displaying posts 1 through 15.
Post 1 made on Monday July 18, 2016 at 09:49
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
Disclaimer - This is my personal setup at my new house. I have emailed Luxul support but thought I would pick your brains while I wait for a response.

Issue: Router keeps dropping the internet connection daily. (most commonly after midnight 1:00am ish)

Setup: Windstream internet
Modem - Netgear DSL (New, purchased from BB)
Router - Luxul ABR-4400
Switch - Luxul 2616P
Switch - Luxul 2600
AP - Luxul 1510

Through process of elimination I have determined the issue is most likely the router because rebooting the router is the only thing that fixes this issue. (Restores internet connection)

Some details about my set-up

The house is pre wired with cat6 (40+ drops).

Here is what is connected and always on.

1 - DirecTV genie box (wired direct to switch) always on
4 DirecTV mini box's (wired via coax moca connection)
4 Honeywell thermostats - wireless
1 Haiku (GigAss fan) - wireless
1 Windows computer - wired
1 MyQ garage door access point - wired
1 Vivint alarm panel - wireless
1 Lorex security camera DVR - wired (internet only, cameras are direct conection to the Lorex DVR)
1 OBiTALK VoIP box (For use with Google Voice aka Home Phone. See link below for details)
1 windows laptop - wireless
4 iPhones - wireless
1 Android phone - wireless
1 iPad - wireless
2 - android tablet - wireless
1 - Xbox One - Wired
1 - Roku4 - Wired
1 - 50" Samsung Smart TV - Wired
1 - 60" LG Smart TV - Wired
1 - Epson Printer - Wired


There is some AV gear that is on from time to time but otherwise it's hard powered off via separate switch








[Link: newegg.com]


Luxul v Log File
Mon Jul 18 09:21:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:21:56 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:22:36 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:23:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:24:43 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:24:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:24:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:24:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:23 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:43595 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:48 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:25:49 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:26:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:26:56 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:27:36 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:27:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:27:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:27:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:29:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:29:43 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:30:24 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.9.251:35220 not from a LAN, ignoring
Mon Jul 18 09:30:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:30:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:30:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:31:56 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:32:36 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:32:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:33:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:33:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:33:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:34:43 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:39 2016 daemon.info dnsmasq-dhcp[1389]: DHCPREQUEST(br-lan) 192.168.0.107 e0:b7:b1:80:1d:07
Mon Jul 18 09:35:39 2016 daemon.info dnsmasq-dhcp[1389]: DHCPACK(br-lan) 192.168.0.107 e0:b7:b1:80:1d:07 DIRECTV-HR34-B1801D07
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:35:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:36:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:36:54 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:36:55 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:36:56 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:37:36 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:38:37 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring
Mon Jul 18 09:39:43 2016 daemon.warn miniupnpd[1412]: SSDP packet sender 169.254.5.49:49152 not from a LAN, ignoring

Last edited by AAC_Anthony on July 18, 2016 10:11.
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
Post 2 made on Monday July 18, 2016 at 10:34
Audiophiliac
Super Member
Joined:
Posts:
August 2006
3,312
What F/W is your router on? Do you have DHCP reservations set up with spaces in the names? Have you completely disconnected DirecTV from network to eliminate it as a problem? Luxul has good support. They should be able to tell you what to do.

We have probably 2 dozen or so 4400 routers out there. I have one at home as well, with a 1208P POE switch and a 1510 AP as well. I have had zero issues since I installed that setup over 2 months ago. I have not had to reboot anything, have experienced no dropouts, etc. Neither have I heard any complaints from clients with the routers.

I discovered the hard way about pre- 4.0.6 (I think?) firmwares that would allow you to label DHCP reservations with spaces, even though that was a no no and would require a factory default to sort out. I know DirecTV has caused network headaches for more than myself at one point or another.

Let us know what you find out.
"When I eat, it is the food that is scared." - Ron Swanson
OP | Post 3 made on Monday July 18, 2016 at 10:42
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
On July 18, 2016 at 10:34, Audiophiliac said...
What F/W is your router on? Do you have DHCP reservations set up with spaces in the names? Have you completely disconnected DirecTV from network to eliminate it as a problem? Luxul has good support. They should be able to tell you what to do.

We have probably 2 dozen or so 4400 routers out there. I have one at home as well, with a 1208P POE switch and a 1510 AP as well. I have had zero issues since I installed that setup over 2 months ago. I have not had to reboot anything, have experienced no dropouts, etc. Neither have I heard any complaints from clients with the routers.

I discovered the hard way about pre- 4.0.6 (I think?) firmwares that would allow you to label DHCP reservations with spaces, even though that was a no no and would require a factory default to sort out. I know DirecTV has caused network headaches for more than myself at one point or another.

Let us know what you find out.

The Router firmware is up-to-date, that was the first thing I checked. I will try disconnecting the DirecTV tonight to see if the problem goes away. As for the DHCP reservations I have not played with that yet. This is my first Luxul system I've set up. I was able to setup a guest network on VLan2 so setting DHCP reservations shouldn't be too much of an issue once I get a chance to dig in.
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
OP | Post 4 made on Tuesday July 19, 2016 at 09:05
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
@Audiophiliac

I followed your suggestion of DHCP reservations and assigned a static ip address to each of the DTV box's. The router hasn't dropped its connection since. I will to give a few days and report back my findings.


Thanks again for your suggestion...
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
Post 5 made on Tuesday July 19, 2016 at 17:46
WhiteVan Lifestyle
Loyal Member
Joined:
Posts:
July 2007
5,108
My guess is you have this fixed. Ive seen quite a few cases where DirecTV on DHCP is involved in an IP address conflict. I'm not quite sure why this happens but I am sure its DirecTV every time and a static IP fixes it every time.
Safe 'n Sound Central Coast CA www.mysafensound.com [Link: facebook.com]
OP | Post 6 made on Wednesday July 20, 2016 at 10:13
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
On July 19, 2016 at 17:46, WhiteVan Lifestyle said...
My guess is you have this fixed. Ive seen quite a few cases where DirecTV on DHCP is involved in an IP address conflict. I'm not quite sure why this happens but I am sure its DirecTV every time and a static IP fixes it every time.

I think you are correct, it hasn't drop the connection since assigning the static IP addresses. It's weird because I had the same setup at my old house with a cheap Linksys router running DD-WRT and never ran into this issue.

Oh-well, all's well that ends well.
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
Post 7 made on Wednesday July 20, 2016 at 21:39
vwpower44
Super Member
Joined:
Posts:
August 2004
3,662
WAN Acceleration also needs to be turned off. This is key.
Stay Hungry, Stay Foolish...
OP | Post 8 made on Thursday July 21, 2016 at 15:07
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
On July 20, 2016 at 21:39, vwpower44 said...
WAN Acceleration also needs to be turned off. This is key.

I came across that on another site and turned it off as well.

Thanks for the suggestion...
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
OP | Post 9 made on Thursday August 4, 2016 at 15:53
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
Update:

Internet still dropping off. Having to reboot router almost daily.

1. Replaced modem (no luck)
2. Had windstream replace line from house to the street (no luck)
3. Contacted Luxul and they have issued an RAM (waiting on replacement)

If replacing the router doesn't work then I will begin the process of pulling things off the network one by one to see if I can find the source of the problem.

Anyone have any experience using a NetGear DSL modem with the ABR-4400 on Windstream? Seams straightforward enough. I have the modem set to "Modem Only" and the router set to PPPoe followed by my login credentials for windstream.

Thanks in advance...
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
Post 10 made on Monday August 8, 2016 at 09:54
Total Control Remotes
Super Member
Joined:
Posts:
July 2006
2,987
We ran away from Luxul years ago and haven't looked back. I keep hearing how reliable their new lineup is, but I can't imagine that being the case. Every time I walk past the stockpile in my garage of systems I have ripped out I cringe and remember the pain very well.
Post 11 made on Monday August 8, 2016 at 11:53
vwpower44
Super Member
Joined:
Posts:
August 2004
3,662
Their new stuff has been great. The 4400 Router, and 1510 WAPS are really nice. I just replaced my UniFi system in my house with this combo and couldn't be happier.
Stay Hungry, Stay Foolish...
OP | Post 12 made on Tuesday August 9, 2016 at 20:59
AAC_Anthony
Audio Authority Corp.
Joined:
Posts:
September 2010
167
On August 8, 2016 at 11:53, vwpower44 said...
Their new stuff has been great. The 4400 Router, and 1510 WAPS are really nice. I just replaced my UniFi system in my house with this combo and couldn't be happier.

Are you on Cable or DSL for your internet connection? PPPoe?
Anthony Grote | Account Manager
859-685-1294, www.audioauthority.com
Follow us - [Link: twitter.com]
Post 13 made on Saturday August 13, 2016 at 08:50
Don Heany
Senior Member
Joined:
Posts:
September 2008
1,178
On August 8, 2016 at 11:53, vwpower44 said...
Their new stuff has been great. The 4400 Router, and 1510 WAPS are really nice. I just replaced my UniFi system in my house with this combo and couldn't be happier.

Have this combo with 3 WAPs and the XWC1000. Switch is a Cisco SG200. Modem an Xfinity gateway set to bridge mode. Could not find setting for WAN acceleration in the interface but that hasn't caused any issues (knock on wood).

The problem I ran into was- not being able to see NuVo players on the network for turnup. UPnP was enabled, so that wasn't the issue. I pulled the Cisco switch and tried an unmanaged Pakedge piece, no dice. Was going to attempt removing the controller from the setup but ran out of time. Will be heading back next week to get this nailed down. Any tips? BTW, the router is the A, not X model...
Post 14 made on Saturday August 13, 2016 at 12:18
vwpower44
Super Member
Joined:
Posts:
August 2004
3,662
Take the Luxul out and use the Xfinity Gateway. I know this is against everything we do, but when those things are in bridge mode, something still acts wonky. I tried an ERL, ABR4400, and still had issues with AirPlay, Sonos, and UPNP on Sony Receivers with Music Connect. Used the router/modem from Xfinity and it works fine. My assumption is that bridge mode on certain models of the xfinity router are not 100% bridged. Between Xfinity and FiOptics they are f-ing killing me.
Stay Hungry, Stay Foolish...
Post 15 made on Monday August 15, 2016 at 06:10
Don Heany
Senior Member
Joined:
Posts:
September 2008
1,178
On August 13, 2016 at 12:18, vwpower44 said...
Take the Luxul out and use the Xfinity Gateway. I know this is against everything we do, but when those things are in bridge mode, something still acts wonky. I tried an ERL, ABR4400, and still had issues with AirPlay, Sonos, and UPNP on Sony Receivers with Music Connect. Used the router/modem from Xfinity and it works fine. My assumption is that bridge mode on certain models of the xfinity router are not 100% bridged. Between Xfinity and FiOptics they are f-ing killing me.

Was going to pull the wireless controller out of the mix, but this seems a more likely solution and a fairly quick change up. Will change the gateway addy and pray Comcast doesn't update and default it to 10.0.0.1. Thanks veedub!
Page 1 of 2


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse