I have a 1 Gbps connection with an ISP that rents another telecommunications company’s fiber. That telecom owns the ONT in my apartment.

I had an electrician fix the heated floor in my bathroom a few weeks ago. He had to turn off the main breaker for safety reasons, which also cut power to the ONT. After turning the power back on, my speeds had dropped from 1 Gbps to circa 100 Mbps. I filed a ticket with my ISP, who resolved the issue by having the telecom do something at their end, they said. (Sounds software-y/configuration-y.)

Yesterday, I f*cked my router (a raspberry pi with openwrt) up by flashing the latest pre-release firmware on it. I lost all connections and the Pi wouldn’t recognize any of its hardware interfaces. As part or my “routine”, I rebooted my devices in this order: my APs, my routers and, lastly, my ONT. After some diagnosing, I identified that the problem was indeed the new firmware on the router/Pi. But then I noticed that my speeds had dropped, so I gauged the speeds directly at the ONT and, lo and behold, they were down to 100 Mbps again. I have, yet again, filed a ticked with my ISP, waiting to hear from them now.

My question, just out of curiosity, to those of you that have the knowledge/experience: what could be going on the telecom’s end? Is there a correlation/plausible technical explanation between my connection speeds dropping and restarting or cutting the power to the ONT?

  • emotional_soup_88@programming.devOPEnglish
    21·
    2 days ago

    Thanks for the advice on ruling out physical “dirt” factors! I rarely think of those…

    Regarding the negotiated speeds, I’m unsure where to find them. Neither the interfaces page, nor the status page nor an ip link shows anything speed related (other than the MTUs but those have always been set to 1500).

    • Admiral Patrick@dubvee.orgEnglish
      2·
      2 days ago

      Mine shows up on the main Overview page like in your second screenshot:

      To check from terminal, assuming your WAN interface is eth1:

      cat /sys/class/net/eth1/speed

      Should be 1000 for 1 Gbps, or 100 for 100 Mbps.

      Either end (ONT or Pi) could cause the auto negotiation to drop to 100 Mbps. Since that’s the consistent speed you’re seeing, I’m inclined to believe that’s the problem though the “why” is up in the air. Like I said, try a different ethernet cable and different device connected directly to the ONT and see if it negotiates at 1000 Mbps.

      • emotional_soup_88@programming.devOPEnglish
        2·
        2 days ago

        Every interface under ../net/ returns 1000. Unfortunately, I don’t have any other devices with which to interface directly with the ONT. But then again, there’s just a gigabit switch between the Pi and the ONT… Anyway, thank you so much for indulging me! I’ve learned a lot! :)

        • Admiral Patrick@dubvee.orgEnglish
          2·
          2 days ago

          Well, if it’s negotiating at 1 Gbps but you’re only getting 100 Mbps, assuming the Pi router itself is fine, then yeah, sounds like something upstream from you on the ISP side (ONT provisioning, etc).

          On the plus side, when you engage support next you can let them know you’ve ruled this out so there’s at least that much progress lol.

          • emotional_soup_88@programming.devOPEnglish
            21·
            2 days ago

            Just as a bonus: this lead me to discover why wan/eth1 didn’t show up on the status page. I had to add “device” and “protocol” under “network” in /etc/board.json

            Two birds.