You could do a Continuous ping to something and redirect the output to a text file, so you could the check for drops later
Code: Select all
ping -t legitreviews.com > textfile.txt
Code: Select all
ping -t legitreviews.com > textfile.txt
It looks like that is what needs to be tried. I will try that over the weekend (probably overnite Saturday night) after the kids go to bed so no one else will need internet but me. I think from 11pm to 8AM will be enough of a time span to see if there are disconnects when hooked directly to the PC downstairs that is right next to the modem. To be accurate I will install a torrent client on that PC and download/seed a test file to try to recreate the problems accurately. and test with the torrent client "on" during all of Saturday night, then "off" during all of Sunday night, and then compare results. Being a networking noob I've never even done a ping before, I assume that I should do it from an administrators command line and just paste the code you provided into the command line interface. BTW. where will that txt file save to?kenc51 wrote:The only way to be sure is to remove the router from the equation and plug the pc directly into the modem and see if it disconnects.
You could do a Continuous ping to something and redirect the output to a text file, so you could the check for drops later
Code: Select all
ping -t legitreviews.com > textfile.txt
There were instantaneous disconnect/reconnects at 9:19pm and at 5:19am, curious that they were 8 hours apart down to within a second. Cable modem logs show no problems since time of last modem reset (3 days 14h:22m:20s as of this writing). Internet usage at the most was 2 wireless PCs watching youtube vids, one wireless device that was idle, and one wired device that was idle. I see no reason for disconnects other than either router hiccups or intentional ISP actions. I'm not sure if a router heat issue would cause this, I'd figure if that was the problem it would either reboot completely (which would show up in cable modem log) or stay off. Also the router is in a cool basement so...2013-01-19 10:23:37 [5] syslog: [AUTH] 192.168.1.3 login success
2013-01-19 10:03:13 [5] syslog: [DHCP] Dhcp assign 192.168.1.4 to [wireless device]
2013-01-19 09:53:06 [5] syslog: [AUTH] 192.168.1.3 login success
2013-01-19 09:52:57 [5] syslog: [AUTH] Not found session 3813bd49, user login check failed
2013-01-19 09:48:40 [5] syslog: [DHCP] Dhcp assign 192.168.1.3 to [wireless device]
2013-01-19 09:42:45 [5] syslog: [DHCP] Dhcp assign 192.168.1.3 to [wireless device]
2013-01-19 09:34:44 [5] syslog: [DHCP] Dhcp assign 192.168.1.3 to [wireless device]
2013-01-19 05:19:20 [5] syslog: [SNTP] SNTP sync success.
2013-01-19 05:19:19 [5] syslog: [SNTP] SNTP Initialized.
2013-01-19 05:19:18 [5] syslog: [IPCONN] Wan[DHCP] Link was Connected, Run Cmd: ifconfig eth0 xx.xxx.xx.xxx netmask 255.255.248.0 mtu 1500 .
2013-01-19 05:19:18 [5] syslog: [IPCONN] Wan[DHCP] Link was Disconnected
2013-01-19 00:14:55 [5] syslog: [AUTH] 192.168.1.3 login success
2013-01-19 00:14:40 [5] syslog: [AUTH] Not found session 39c74188, user login check failed
2013-01-19 00:07:06 [5] syslog: [DHCP] Dhcp assign 192.168.1.3 to [wireless device]
2013-01-18 21:19:20 [5] syslog: [SNTP] SNTP sync success.
2013-01-18 21:19:20 [5] syslog: [SNTP] SNTP Initialized.
2013-01-18 21:19:19 [5] syslog: [IPCONN] Wan[DHCP] Link was Connected, Run Cmd: ifconfig eth0 xx.xxx.xx.xxx netmask 255.255.248.0 mtu 1500 .
2013-01-18 21:19:19 [5] syslog: [IPCONN] Wan[DHCP] Link was Disconnected
2013-01-18 21:01:28 [5] syslog: [DHCP] Dhcp assign 192.168.1.2 to [wired device]
2013-01-18 18:59:59 [5] syslog: [DHCP] Dhcp assign 192.168.1.3 to [wireless device]
2013-01-18 16:03:53 [5] syslog: [DHCP] Dhcp assign 192.168.1.7 to[wireless device]
2013-01-18 15:53:42 [5] syslog: [DHCP] Dhcp assign 192.168.1.4 to[wireless device]
2013-01-18 15:18:54 [5] syslog: [Log Cleared]
Within reason. Though I am guessing my definition of 'high quality' and yours differs by a level of magnitude.vbironchef wrote:You get what you pay for. With all the effort you put into a piece of you know what. It's just better to buy a high quality router. Your time is money. Return it and buy the best you can buy.
Routers dont actually determine DHCP lease time, they can refresh before the maximum lifetime of the DHCP server but they really cant go longer (well they can due to conflict detection, but that is a different topic).Kaos Kid wrote:The setting in the router allows for DHCP lease time of between 1-160 hours and I've tried many between those two points. Currently at 24 hours, I get the least amount of disconnects with that setting although far from perfect. I just wish I would have RMA'd it back to newegg before now, I have a pretty good record with them (only had one instance that I didn't receive my purchase due to post office error, and they sent a replacement out within a couple of days).
PS edit: Just called Rosewill. Got routed to a call center that made me give them my name and number for a tech to "call me back" in an hour or so. I can't believe they don't even man their own tech support line. This sucks.013-01-30 11:14:06 [5] syslog: [AUTH] 192.168.1.101 login success
2013-01-30 11:13:56 [5] syslog: [AUTH] Not found session 792fb0ef, user login check failed
2013-01-30 08:56:24 [5] syslog: [DHCP] Dhcp assign 192.168.1.106 to [mac address]
2013-01-30 07:15:02 [5] syslog: [SNTP] SNTP sync success.
2013-01-30 07:15:01 [5] syslog: [SNTP] SNTP Initialized.
2013-01-30 07:15:00 [5] syslog: [IPCONN] Wan[DHCP] Link was Connected, Run Cmd: ifconfig eth0 xx.xx.xx.xx netmask 255.255.240.0 mtu 1500 .
2013-01-30 07:14:58 [5] syslog: [SNTP] SNTP Initialized.
2013-01-30 07:14:58 [5] syslog: [IPCONN] Wan[Static] Link was Disconnected
2013-01-30 07:14:13 [5] syslog: [AUTH] 192.168.1.101 login success
2013-01-30 07:13:46 [5] syslog: [AUTH] 192.168.1.101 login failed, because username or password is wrong
2013-01-30 07:13:33 [5] syslog: [AUTH] Not found session 792fb0ef, user login check failed
2013-01-30 06:33:19 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-30 00:15:12 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 23:58:49 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 23:52:32 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 23:26:49 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 23:24:33 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 23:12:31 [5] syslog: [SNTP] SNTP sync success.
2013-01-29 23:12:30 [5] syslog: [SNTP] SNTP Initialized.
2013-01-29 23:12:30 [5] syslog: [SNTP] SNTP Initialized.
2013-01-29 23:12:30 [5] syslog: [SNTP] SNTP Initialized.
2013-01-29 23:12:29 [5] syslog: [IPCONN] Wan[Static] Link was Connected, Run Cmd: ifconfig eth0 xx.xx.xx.xx netmask 255.255.240.0 mtu 1500 .
2013-01-29 23:11:55 [5] syslog: [AUTH] 192.168.1.101 login success
2013-01-29 23:11:44 [5] syslog: [AUTH] Not found session 2c553554, user login check failed
2013-01-29 23:06:57 [5] syslog: [IPCONN] Wan[DHCP] Link was Disconnected
2013-01-29 22:51:39 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 22:49:45 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 22:45:57 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 22:09:08 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 21:36:40 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 21:27:03 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 21:19:33 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:49:38 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:41:13 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:40:19 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:39:54 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:38:47 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:38:37 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:21:45 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 20:14:05 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 19:47:34 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 19:35:02 [5] syslog: [DHCP] Dhcp assign 192.168.1.104 to [mac address]
2013-01-29 19:21:35 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 18:49:30 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 18:46:45 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.81.40
2013-01-29 18:46:45 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:46:45 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:46:45 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:46:45 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:45:21 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:45:21 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:45:21 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:45:21 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:45:21 [0] kernel: <128>[Dos attack: SynFlood] from source 72.21.91.148
2013-01-29 18:41:28 [5] syslog: [DHCP] Dhcp assign 192.168.1.103 to [mac address]
2013-01-29 18:33:19 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-29 18:32:45 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 18:14:47 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 18:12:12 [5] syslog: [DHCP] Dhcp assign 192.168.1.101 to [mac address]
2013-01-29 17:53:16 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-29 17:24:08 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-29 17:23:53 [5] syslog: [DHCP] Dhcp assign 192.168.1.106 to [mac address]
2013-01-29 16:44:21 [5] syslog: [DHCP] Dhcp assign 192.168.1.104 to [mac address]
2013-01-29 16:41:10 [5] syslog: [DHCP] Dhcp assign 192.168.1.104 to [mac address]
2013-01-29 16:00:06 [5] syslog: [AUTH] 192.168.1.101 login success
2013-01-29 15:59:56 [5] syslog: [AUTH] Not found session 141f16cd, user login check failed
2013-01-29 15:59:55 [5] syslog: [AUTH] User admin session timeout and auto logout
2013-01-29 15:35:50 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-29 15:35:07 [5] syslog: [DHCP] Dhcp assign 192.168.1.106 to [mac address]
2013-01-29 15:25:07 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to [mac address]
2013-01-29 15:23:19 [5] syslog: [DHCP] Dhcp assign 192.168.1.106 to [mac address]
2013-01-29 15:20:30 [5] syslog: [AUTH] Not found session 500d237, user login check failed
2013-01-29 15:18:52 [5] syslog: [DHCP] Dhcp assign 192.168.1.100 to
2013-01-29 15:16:07 [5] syslog: [AUTH] 192.168.1.101 login success
2013-01-29 15:15:44 [5] syslog: [AUTH] Not found session 141f16cd, user login check failed
2013-01-29 15:07:00 [5] syslog: [SNTP] SNTP sync success.
2013-01-29 15:06:59 [5] syslog: [SNTP] SNTP Initialized.
2013-01-29 15:06:58 [5] syslog: [IPCONN] Wan[DHCP] Link was Connected, Run Cmd: ifconfig eth0xx.xx.xx.xx netmask 255.255.240.0 mtu 1500 .
2013-01-29 15:06:58 [5] syslog: [IPCONN] Wan[DHCP] Link was Disconnected
Refund or Replacement: replacement
Reason for RMA: This router will not sustain connections between the cable modems used (SB6121 & DPC3008) and router due to DNS resolver and DHCP renewal issues. This has not worked satisfactorily through two firmware upgrades over 3 1/2 months, and I have lost patience. I would like a prepaid RMA sticker to send this back for repair or replacement, or will cross-ship if you decide to upgrade me to the L600T (edit: oops, I meant T600N in my RMA, hopefully they will know that) in the hopes that it doesn't share the same issues as this L600N has. Here is a link to one of the tech forums I frequent detailing the issues I've faced since receiving this router back in early December 2012 and the exhaustive steps taken to correct the flaws inherent in this router:
http://forums.legitreviews.com/about43580.html
As you can see this has been an ongoing problem since I first received it and I see no solution on the horizon. Please advise on your course of action, as that will determine MY next course of action. Thank You.
Rosewill's response: "Your request has been received and we look forward to assisting you in the return process.
Again we want to thank you for your interest in our products.
Rosewill.com
The Best Choice in Value
http://www.rosewill.com/
1-(800) 575-9885 "