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

1000M WAN Link?

Discussion in 'Tomato Firmware' started by Richard Atkinson, Sep 4, 2013.

  1. Richard Atkinson

    Richard Atkinson Reformed Router Member

    So I've been searching for answers on this for a while now with no apparent answer. I've got Shibby's 112 Build on my RT-N66U, and I previously had Toastman's 1.28.0502.1. I've got Bell Aliant's FibreOP 175 / 30 connections which requires the use of VLAN 35 and tagging to connect to the internet.
    So far I've only been successful in connecting at 100M on the WAN port while the rest of the ports can connect at 1000M with no problems. Obviously the 100M port speed is limiting my internet throughput and I'd like to get it working at 1000M as it should be. Is this possible with Tomato? I will say that the very first time I flashed Toastman's build (Not sure which number) it did work properly for a short period of time. However it later switched back to 100M. Thanks for reading.
  2. RMerlin

    RMerlin Network Guru Member

    Most common reason for the port negotiating at 100 Mbits is either the cable is an older Cat5 cable (need Cat5e or higher), or the cable itself is defective.
  3. Richard Atkinson

    Richard Atkinson Reformed Router Member

    I checked the cable with a gigabit switch a couple of weeks ago and it negotiated a full speed link immediately. I'll check it again tomorrow but I'm fairly confident this isn't the issue here.
  4. koitsu

    koitsu Network Guru Member

    The issue can also be vendor PHY incompatibility, in which case there is nothing you can do other than replace the hardware and hope you get a revision of a device that uses a different brand of PHY.

    I've talked at length about this in the past. Please read that entire thread -- it's long, but it proves my point and has all the details. I rectified the issue in question by purchasing a different (newer) revision of cable modem.

    TL;DR -- It sounds to me like a PHY incompatibility between the Asus RT-N66U and Bell Aliant's FibreOP concentrator. I can almost guarantee that if you were to complain about this to Bell, they would blame your router; and if you were to complain about this to Asus, they would blame Bell. You are purely stuck in the middle and there is very little you can do.

    It also could be a configuration issue; for example the Bell Aliant device may actually be configured to set its PHY to 1000mbit/full (rather than autonegotiate), and the Asus would be set to autoneg -- in this mismatch situation, sometimes slower speeds are negotiated as a result. Short version is: if ever hard-setting a port to a specific speed, both devices on each end need to be configured that way. Otherwise both must be left to autoneg. And if autoneg doesn't work, then it's either physical cabling problems or PHY incompatibilities.

    I cannot help past this point.
  5. RMerlin

    RMerlin Network Guru Member

    If that's indeed the case, a cheap workaround would be to put a basic gigabit switch between the router and the FibreOP device.
    dc361 likes this.
  6. koitsu

    koitsu Network Guru Member

    I didn't think of that -- yeah, that'd be a cheap/clever way to test, because if, for example, after sticking that switch in place the link/speed LED associated with the port the FibreOP device is plugged into still reads 100mbit, then you know damn well where the problem lies. ;-)
    dc361 likes this.

Share This Page