New Rosewill L600N Router/CHARTER Driving Me Bats**t Crazy!

[kenc51]

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

[Kaos Kid]

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

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?

As always, thanks for your continued patience and help!

[kenc51]

create the file first in documents folder.
you dont need to run it as admin.
Windows key +R then type cmd

[Kaos Kid]

Cool, thanks! I'll do this over the weekend. A funny thing, I checked the router log a while ago and saw something curious--a "connect" without a "disconnect" preceding it. All the other times, it would disconnect first then reconnect within a second, this entry showed no disconnect but there was a connect listed.

I turned off torrent to test it without for tonight so I can get a baseline, since I wasn't really seeding much anyway. There will be no demands on the system for the rest of the day and night so we'll see if there are any hiccups over the next 18-24 hours.

It appears that the cmd window for this ping stays open and continuously pings until I manually close it by X-ing out of it, correct?

[Kaos Kid]

This was after sitting idle overnight (except for wife and kids surfing) no P2P running

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]

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...

[Kaos Kid]

...aaaaaand another disconnect/reconnect at exactly 1:19PM today, 8 hours to the minute after the last one. Looks like a pattern is developing, if it does the disconnect/reconnect thing at 9:19PM tonite, then there is definitely a pattern. I can't find a setting in the router that would account for automatic disconnects/reconnects every 8 hours, but it sure is a weird coincidence and it is hard to not think that my ISP has something to do with it.

[Kaos Kid]

Yeppers, there is definitely a pattern as I again showed disconnects at 9:19pm last night and again at 5:19amthis morning so it happens for sure every 8 hours on the dot. Would that indicate something in the router doing it intentionally, or my ISP doing? For some reason the ping code you gave me earlier doesn't seem to work for me, I get no acknowledgement after pasting in the code to the command line, just a blinking cursor and it isn't saving anything to the text file. I googled and found a post that suggested I use this format in the command line (and use an IP address rather than a domain name):

ping 65.172.79.82 -t >c:ping.txt

and it didn't seem to work either, I just see the cmd box with a blinking cursor on the next line after the cmd and nothing being recorded in the text file.

Thanks for any further light you can shed on this problem.

[kenc51]

sorry for not getting back to you, but I've been sick with a bad infection for the past 2 weeks.

Did you get it sorted?

that ping command will not display anything on the page as it's re-directing the output to the text file.
You'll need to do CTRL+C to stop it before you want to read the contents of the file.

Some ISP's will force disconnects for users.
My company does it once every 28 days in the middle of the night. This is to ensure we have valid usage stats for their line.
Some products are sold with a bandwidth cap and have charges for going over.
There should be no reason why they would disconnect you after 8 hours though.


Ken

[Kaos Kid]

No worries. I did have Charter come out and check my lines, the tech did make things a tad better by running my internet cable through a noise limiter. My power levels were in the 8-11 range, he said their acceptable levels are between -12>>>12, they came down a bit to between 5>8 dBmV for my four downstream channels,and at the time of this post are 4/4/3/3. We in St Louis Missouri are currently in an unseasonal warm pocket, temps are in the 60s until late tonite then will go down to closer to freezing, I may be paranoid but I see a trend, when it is extremely cold and wet here my power levels are higher, they came down to current low levels when outside temps went up. We'll see if they spike again when the next cold snap hits, in which case it could indicate moisture in my line. I missed the iron egg guarantee because Rosewill indicated on my (and others) newegg review that they are working on the problem so now I am stuck with dealing with them. Oh well, I'm a sucker. I still get the disconnect/reconnect every 8 hours to the minute for just a second, the tech swears that it isn[t something Charter is doing, and has to be in the router firmware. Someone with a similar issue speculated that it is a DNS read error of the router, I don't know enough about that to hazard an opinion but it sounds feasible. Every once in a while internet connection drops and I manually change setting from "Dynamic" to "Static" and use the last IP addy settings that were in there, and get reconnected. Then later I let the router automatically detect settings again and it will find the proper IP address (same one as before, so I'm not losing connection from ISP to modem, but rather between modem and router). PITA but I will live with it a little longer and have it out with Rosewill over the issue of RMA if they don't get it sorted in the next week. Any other suggestions you have will be appreciated.

[vbironchef]

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.

[egloeckle]

Every 8 hours? Idle curiosity, what is your DHCP lifetime on the address you are getting?

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.

Within reason. Though I am guessing my definition of 'high quality' and yours differs by a level of magnitude.

[Kaos Kid]

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).

vbironchef, at the time that was all I could afford, I was dazzled by the smoke and mirrors of n600 and dual band capacity. If the egg will give me a full refund, I have saved up a bit since then and can probably go up to $100 US shipped, hopefully can find something more reliable in that price range. If I have to deal with Rosewill over it, I assume they will just send a replacement new or refurbed unit, so doubt my problems will be solved going that route.

[Major_A]

I know that this doesn't help with your current situation but it might be time to move on. The router sounds like a giant nightmare. Check out TP-Link on one of your favorite shopping sites. I've played with a few of them and they work very well and have outlived most routers I personally purchase. My sister/brother in law have an older TP-Link that has been running 24/7/365 for over 2 years without any issues. I know personally that their modem from Comcast needs to be rebooted more often than the router.
http://www.newegg.com/Product/ProductLi ... Mark=False

[egloeckle]

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).

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).

If you change the DHCP lease time to something like 4 hours, do you get the traffic drops every 4 hours? If so, if it is possible, try connecting something else to the line to pull DHCP and see if you get the same dropouts (check the DHCP lease time to figure out when it should happen). The fact that it is happening on such even intervals is a huge flag to me. Especially when setting a static then back to DHCP 'fixes' it. To me it almost sounds like the DHCP implementation on that router is terrible or bugged which could be bad firmware or potentially a hardware issue that an RMA may solve.

Only other thing I can think of is your modem is rebooting periodically for some reason. The router is not requesting a new DHCP lease in this case (it shouldnt) but charter is blocking you until it does. Your manual steps force a DHCP refresh fixing the problem.

[Kaos Kid]

Just got off the phone with newegg, no love from them Although there was an iron egg guarantee on the router page when I ordered it, they are now saying that the iron egg guarantee was only supposed to be good for the wireless adapter I bought with it as part of a combo. I know for a fact that the iron egg emblem was on the router page, but the egg rep asked if I had proof of that--of course not, who would think to take a screenshot of the page when they order? Looks like I have learned to not trust them, and IF I DO ever buy from newegg again I will be sure to screenshot every applicable page for proof. Here comes the cliche: Newegg left me with egg on my face this time! Now I will be going back to update my review on newegg, it had been down to 3 stars but now this router will receive ONE star because at least a power light comes on when it is plugged in

Charter did tell me that they ping every two hours to test that modem is connected and talking back, if that means anything to you. I will change the DHCP lease time to 2 hours just because I've run out of other things to try...

Here is a copypasta of the router log since yesterday at 3pm, I removed mac addresses and xx'd IP addresses, but otherwise this is what is happening (time progresses from bottom to top). You can even see where it disconnected last night around 11pm Central but didn't reconnect and I had to switch it to read a static address--then this morning I switched it back to dynamic and it reconnected me to the modem which still had my dynamic address. The cable modem logs show no interruption in service this whole time (up for 5 days 22h:55m:19s) which is consistent with me keeping the same dynamic IP address this whole time even when switching the router from dynamic to static back to dynamic. I think you are correct that it is something to do with DHCP or DNS implementation. Now to get on the phone with Rosewill, something tells me this won't end well either. They need to either fix their firmware CORRECTLY this time or allow a WW-DRT to be implemented for it since they don't seem to know what they are doing here with this router.

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

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.

[egloeckle]

Only entry that looks relevant there is:

2013-01-29 23:06:57 [5] syslog: [IPCONN] Wan[DHCP] Link was Disconnected

And that is horribly vague.

What brand/model is the cable modem? Most modems will only monitor the 'cable' part of the connection, which is not going down (which is good). At least we know the charter portion of the connection is stable, it could potentially still be the modem, DHCP or even the router.

Do you still have your old router around? The only other thing I caught from the logs is that the MTU is set to 1500 which may or may not be correct. While I dont think this being off would cause the issue you are seeing it does tend to cause some strange issues due to fragmentation.

[vbironchef]

Take the hit on a restocking fee and move on.

[Kaos Kid]

vbironchef, by the time newegg deducts 15% restocking fee and I pay shipping for the return, there wouldn't be any value left--plus I would also have to send back the wireless dual band adapter I got in the combo as well, which I DO like... so I'm just stuck with this. Lesson learned. It supposedly has a 1 year warranty with Rosewill so I will let them tinker with a fix for a little while, I'm thinking if I would try to RMA to them I would just get a refurb back anyway that may or may not have the problem fixed. I guess that is the catch-22 with buying value priced items, if they are lemons it isn't worth the cost to return them. I'll just keep saving for the future and the NEXT router I get will be from the LR router reviews section and be an editors choice ;)

Egloeckle, the modem is an SB6121, and I have already swapped it out once for a fresh one. The modem is seeing and talking to Charter just fine, but the router isn't always reading the correct address from the modem ie: starts out dynamic, then at some future point loses connection and I switch it to static with the same IP info and it gives me connection back for awhile, then later on can run the setup wizard and it can miraculously "see" the dynamic address again. Others have pointed to a DHCP/DNS conflict, and I am leaning toward a bug in the firmware that is causing that, how else would you get regularly timed disconnects?

I just got off the phone with the Rosewill tech and he told me to try something that is not in their FAQs, and is actually contrary to the firmware upgrade they themselves put out as a "fix". Where normally on the LAN side the router is seen as 192.168.1.1, it stays that way but their firmware upgrade fix was to make the ranges under "use router as a DHCP server" between 192.168.1.100 start to 192.168.1.200 end. That is in the upgrade guide with the firmware update, and doesn't solve my problem... As HIS fix he told me to change the router IP address itself to 192.168.2.11 and the starting and ending ranges will then change accordingly, and I should assign my address reservations from that range instead. Unfortunately I was at a wirelessly connected computer at the time so all I could do is take notes until I can go downstairs to my computer that has wired connection and make all the settings changes. Once I do that, I will post back with my results and then monitor my logs overnight to see if it works any better than just using their default firmware fix. Wish me luck! *Knocking on wood*

PS I was hoping he could give me a secret setting to be able to add a IP blacklist to this router, since for some reason I am getting DoS synflood attacks from two IPs on the Edgecast Network and was thinking maybe something like that would be messing with my routers ability to connect. He said that this is not supported since this wasn't meant to be a high end router, so I can only hope that someone will come up with a DD-WRT solution for this router to open up some functionality.

[Kaos Kid]

Update

I've finally given up on Rosewill being able to fix this problem through firmware upgrades. I have sent in an RMA request to have this repaired or replaced with a working unit at their expense through a prepaid RMA sticker for shipping, I feel that it is the least they can do considering all I've been through dealing with this lemon of a router. I received a standard generic form acknowledging receipt of my request, now the ball is in Rosewill's court to rectify this situation satisfactorily and so salvage their reputation.

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 "

[skier]

I would check to see if you can load up DD-WRT on it, My TP Link WDR-3600 had to be rebooted 2-3 times a day due to DNS issues, after I upgraded it to DD-WRT it has been golden (and a simply awesome router)

another thing to try if the replacement does the same thing- DD-WRT is a much more in-depth interface anyway if you can load it