I've recently looked closely to an ethernet cable that came with an used modem+router (an AirLive WL-8064ARM) to replace my old one that had died and I can't make out what type of cable it is even after looking at wikipedia.
After comparing it with my old router's cable it seems to be a cross-over cable, but it only has 4 types of colors: blue, orange, white/blue stripe and white/orange stripe. Also it says on its cover - E188601 TYPE CM 24AWG/2PRS UTP VERIFIED (UL) CAT 5 PATCH CABLE TO TIA/EIA 568A LL84201 CSA TYPE CMG FT4 COPARTNER. I bolded what I think is most important in identifying the type of cable. But shouldn't it say crossover cable instead of patch cable? Here's why:
Here's an image edit I've done to explain what each end of the cable looks like:
As you can see it's different from what is shown here: http://en.wikipedia....Crossover_cable
However this router would go down in the middle of the night, so it wasn't good for me...
I bought a WL-600g with 188.8.131.52.A firmware and have had no problems ever since. However yesterday I decided to do a test to each router individually just to see if they gave me any different latencies and came to the conclusion they didn't.
However at the end I noticed I had mixed the ethernet cables from each, but I thought it wasn't a big deal, as they had both worked. It seems they both have Auto MDI/MDIX function, so that's why they worked even with a seemingly cross-over cable.
Currently I'm using the WL-600g with the normal Cat5 cable that came with it but, I'm not sure if it's coincidence or not, it seems that ever since my WL-600g has been acting strangely. Sometimes it seems like I lose my connection and when I look at the log I see this at the time the connection dropped:
Jan 1 20:49:55 user warn dnsprobe: dns query failed Jan 1 20:49:57 user warn dnsprobe: dns query failed Jan 1 20:49:57 user notice dnsprobe: Primary DNS server Is Down... Switching To Secondary DNS server Jan 1 20:50:28 user notice dnsprobe: Switching Back To Primary DNS server Jan 1 21:01:20 user warn dnsprobe: dns query failed Jan 1 21:01:22 user warn dnsprobe: dns query failed Jan 1 21:01:24 user warn dnsprobe: dns query failed Jan 1 21:01:24 user notice dnsprobe: Primary DNS server Is Down... Switching To Secondary DNS server Jan 1 21:01:56 user notice dnsprobe: Switching Back To Primary DNS server
The only connection drops I had until then were just ISP IP-assigning related, that happened about in a 12-24h period. This DNS problem seems to happen randomly, but especially when I'm navigating through several pages or waiting for something to load.
And just today the router stopped answering to the PC on its own for the very first time since I bought it, with the icon on the bottom right corner saying the connection was down. 192.168.1.1 in the browser wouldn't access to anything. But it eventually reconnected on its own somehow...
Can anyone explain why is this happening? Did connecting the cable I mentioned at the start could have damaged/screwed something or is this something else entirely, ie a coincidence and it's my ISP's fault (the DNS not answering etc)?
Edited by RoninPedroshin, 10 May 2009 - 07:02 AM.