1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Verizon router -to- WRT54G (loosing connection very often)

Discussion in 'Cisco/Linksys Wireless Routers' started by Exahertz, May 15, 2008.

  1. Exahertz

    Exahertz Addicted to LI Member

    Hey.

    First, here's my network:

    [​IMG]

    (I know there’s a lot of routers but everything works great except for one connection between the Verizon ISP router and a Linksys router) and heres whare the problem is:

    [​IMG]

    I am using a version 2.0 WRT54G with Alchemy firmware v1.0 v3.37 to connect to the Verizon FIOS router.

    The connection seems to work for a few hours out of the day but it does drop intermittently (and it’s not a heat issue):

    When the problem exists, I can not ping from 192.168.1.225 to 192.168.1.1 (as indicated by the red lines) but the strange thing is, I can ping from 192.168.1.225 to 192.168.1.240 on the Linksys router

    [​IMG]

    However I am always able to ping from 192.168.1.33 to 192.168.1.1 (as indicated by the green lines).
    So the Verizon router is still okay, but it seems to be dropping the Linksys router?

    The Verizon router has DHCP turned off.
    The Linksys router and all PC clients are addressed statically.
    I noticed that when the problem happens the Verizon router says that the client is inactive.
    If I change something in the Linksys router, like give it a new IP address or change the MAC address the two routers link right back up and start communicating again.
    If I do nothing they do eventually communicate again, but then it drops a few hours later (like a cycle)

    Could this have something to do with the routing tables and/or ARP packets not being sent correctly?
    Why would the Verizon router be dropping the WRT54G but not the PC client?

    Any help would sure be appreciated :wink:
     
  2. Exahertz

    Exahertz Addicted to LI Member

    Ok here's how I fixed the problem and gained some bandwidth:

    First let me explain how I had the router configured,
    Originally I had the linksys's WAN port connected to one of the Verizon's switch ports using a standard Ethernet cable. BAD IDEA! Why??? Well... the wireless portion of the router is basically virtual physical media (or a virtual cable) connected and controlled on the switch side, so when you're connected wirelessly its almost the same as being connected to a physical switch port. but because i (client PC) was connected wirelessly and the Verizon router connected to the WAN port I had to send packets from the client into the Linksys router, through the NAT layers (Routing Device), which goes out through the router's WAN port and into the Verizon router's switch ports. this made it so i couldnt get to or ping to 192.168.1.1 and i had more complications/restrictions/firewalls/layers/protocols/MAC tables in the way of my true gateway to the internet.

    The Fix:
    Remove the cable from the Linksys router's WAN port, use a crossover cable from one of the linksys's switch ports to one of the Verizon's switch ports (crossover cables are needed to connect like-devices).
    What this did was basically turn my Linksys router into a wireless switch thus eliminating processor overhead and propagation delay (basically the router doesn’t have to do any work and the packets can move through just the switch very quickly).
    But that’s not all there is to it, and this is ware I was really stumped. I never disabled the router, so even though I could ping around in my own network I couldn’t get out to the web or ping the DNS. This was because the router portion was still pointing my DNS to the WAN port (which had nothing connected to it). I tried everything and I really thought that a DNS of 192.168.1.1 would point it to the Verizon router but it didn’t. So by simply turning off the internal address configuration the DNS had no ware else to point but to the Verizon router and bingo, replies from Google were rushing in.

    Weird thing was, before I disabled the internal address configuration, every time I saved a new setting I was able to ping out to the Internet for 5 seconds. This is probably because the router was resetting and shut down for 5 seconds while the switch was still running.

    So in short,
    Use a crossover cable from switch port to switch port
    Point your DNS to your ISP router
    Disable the router's internal address configuration
    And you've got yourself a wireless switch!
     

Share This Page