Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. cox is incompetent

cox is incompetent

Scheduled Pinned Locked Moved Uncategorized
20 Posts 7 Posters 3 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

    @paul_ipv6 @Viss

    I used to work telecom, we had a resolution code "PFM".

    Half the time it was used was cover for somebody's stupid.

    Other times things did clear by Pure Freaking Magic. Sometimes rattling all the connections gets something seated better. Running a high density bit pattern can drive just enough moisture off to get things working again (until next time).

    paul_ipv6@infosec.exchangeP This user is from outside of this forum
    paul_ipv6@infosec.exchangeP This user is from outside of this forum
    paul_ipv6@infosec.exchange
    wrote last edited by
    #8

    @johntimaeus @Viss

    yeah... i did learn that just running 3 in 24 stress test cleared mystery problems. for a while.

    the other bane of my existence (other than backhoes) was techs going into the hole for a new install, finding the pair they'd been assigned was live and just grabbing "an unused pair" and not getting the provisitioning DB updated. sure enough, give it 6 months and they'd double book that pair and drop our circuit.

    paul_ipv6@infosec.exchangeP fritzadalis@infosec.exchangeF johntimaeus@infosec.exchangeJ 3 Replies Last reply
    0
    • paul_ipv6@infosec.exchangeP paul_ipv6@infosec.exchange

      @johntimaeus @Viss

      yeah... i did learn that just running 3 in 24 stress test cleared mystery problems. for a while.

      the other bane of my existence (other than backhoes) was techs going into the hole for a new install, finding the pair they'd been assigned was live and just grabbing "an unused pair" and not getting the provisitioning DB updated. sure enough, give it 6 months and they'd double book that pair and drop our circuit.

      paul_ipv6@infosec.exchangeP This user is from outside of this forum
      paul_ipv6@infosec.exchangeP This user is from outside of this forum
      paul_ipv6@infosec.exchange
      wrote last edited by
      #9

      @johntimaeus @Viss

      in theory, as a customer, i didn't need to know shit about b8zs, 3 in 24, what a tberd or fireberd test set was, etc. but, the baby bells and sprint both loved going through cycles of firing experienced techs and using contractors, then going back to their own folks but they were wet behind the ears. i do not miss 56k/t1/t3 circuit provisioning and debugging at all.

      johntimaeus@infosec.exchangeJ 1 Reply Last reply
      0
      • paul_ipv6@infosec.exchangeP paul_ipv6@infosec.exchange

        @johntimaeus @Viss

        in theory, as a customer, i didn't need to know shit about b8zs, 3 in 24, what a tberd or fireberd test set was, etc. but, the baby bells and sprint both loved going through cycles of firing experienced techs and using contractors, then going back to their own folks but they were wet behind the ears. i do not miss 56k/t1/t3 circuit provisioning and debugging at all.

        johntimaeus@infosec.exchangeJ This user is from outside of this forum
        johntimaeus@infosec.exchangeJ This user is from outside of this forum
        johntimaeus@infosec.exchange
        wrote last edited by
        #10

        @paul_ipv6 @Viss

        If you ever had issues with Metro Access or Brooks Fibre in Texas, I'm sorry. My ears were very damp

        paul_ipv6@infosec.exchangeP 1 Reply Last reply
        1
        0
        • R relay@relay.infosec.exchange shared this topic
        • paul_ipv6@infosec.exchangeP paul_ipv6@infosec.exchange

          @johntimaeus @Viss

          yeah... i did learn that just running 3 in 24 stress test cleared mystery problems. for a while.

          the other bane of my existence (other than backhoes) was techs going into the hole for a new install, finding the pair they'd been assigned was live and just grabbing "an unused pair" and not getting the provisitioning DB updated. sure enough, give it 6 months and they'd double book that pair and drop our circuit.

          fritzadalis@infosec.exchangeF This user is from outside of this forum
          fritzadalis@infosec.exchangeF This user is from outside of this forum
          fritzadalis@infosec.exchange
          wrote last edited by
          #11

          @paul_ipv6 @johntimaeus @Viss
          At my wife's co, back when t1s were a thing, they had all kinds of noise problems. The tech would come out, swap them to the other pair on the run, and leave. Over and over.

          johntimaeus@infosec.exchangeJ 1 Reply Last reply
          1
          0
          • paul_ipv6@infosec.exchangeP paul_ipv6@infosec.exchange

            @johntimaeus @Viss

            yeah... i did learn that just running 3 in 24 stress test cleared mystery problems. for a while.

            the other bane of my existence (other than backhoes) was techs going into the hole for a new install, finding the pair they'd been assigned was live and just grabbing "an unused pair" and not getting the provisitioning DB updated. sure enough, give it 6 months and they'd double book that pair and drop our circuit.

            johntimaeus@infosec.exchangeJ This user is from outside of this forum
            johntimaeus@infosec.exchangeJ This user is from outside of this forum
            johntimaeus@infosec.exchange
            wrote last edited by
            #12

            @paul_ipv6 @Viss

            Early in the DSL era, you could remotely put the user modem into hardware loopback (like relay goes click). Then feed straight 48v from the datacenter battery stack for 10-30 seconds. Basically dead short current.

            Knocks all kinds if issues right out. Wet mouse condom? It's dry now. And the conductors may have welded together a bit.

            You couldn't do it too much in quick repetition, there were a few small fires.

            viss@mastodon.socialV 1 Reply Last reply
            0
            • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

              @paul_ipv6 @Viss

              Early in the DSL era, you could remotely put the user modem into hardware loopback (like relay goes click). Then feed straight 48v from the datacenter battery stack for 10-30 seconds. Basically dead short current.

              Knocks all kinds if issues right out. Wet mouse condom? It's dry now. And the conductors may have welded together a bit.

              You couldn't do it too much in quick repetition, there were a few small fires.

              viss@mastodon.socialV This user is from outside of this forum
              viss@mastodon.socialV This user is from outside of this forum
              viss@mastodon.social
              wrote last edited by
              #13

              @johntimaeus @paul_ipv6 im 100% sure this is some fuckery on their part. i downgraded from gig to 500mbit metered because it was less than half the price, and almost immediately afterwards i started getting multiple 2-5 minute outages per day. its gotta be some bullshit logical something or other on their end

              also, i wouldnt put it past them to introduce deliberate problems just to punish people who decided to give them less money, because its nearly impossible to prove from this end

              johntimaeus@infosec.exchangeJ 1 Reply Last reply
              0
              • fritzadalis@infosec.exchangeF fritzadalis@infosec.exchange

                @paul_ipv6 @johntimaeus @Viss
                At my wife's co, back when t1s were a thing, they had all kinds of noise problems. The tech would come out, swap them to the other pair on the run, and leave. Over and over.

                johntimaeus@infosec.exchangeJ This user is from outside of this forum
                johntimaeus@infosec.exchangeJ This user is from outside of this forum
                johntimaeus@infosec.exchange
                wrote last edited by
                #14

                @FritzAdalis @paul_ipv6 @Viss

                Very few people learned how to hook an oscilloscope up to a dry pair and look for noise before deciding which one to run on.

                fritzadalis@infosec.exchangeF 1 Reply Last reply
                0
                • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                  @FritzAdalis @paul_ipv6 @Viss

                  Very few people learned how to hook an oscilloscope up to a dry pair and look for noise before deciding which one to run on.

                  fritzadalis@infosec.exchangeF This user is from outside of this forum
                  fritzadalis@infosec.exchangeF This user is from outside of this forum
                  fritzadalis@infosec.exchange
                  wrote last edited by
                  #15

                  @johntimaeus @paul_ipv6 @Viss
                  Well I mean they were both bad. They just didn't want to run a new line.

                  johntimaeus@infosec.exchangeJ 1 Reply Last reply
                  0
                  • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                    @paul_ipv6 @Viss

                    If you ever had issues with Metro Access or Brooks Fibre in Texas, I'm sorry. My ears were very damp

                    paul_ipv6@infosec.exchangeP This user is from outside of this forum
                    paul_ipv6@infosec.exchangeP This user is from outside of this forum
                    paul_ipv6@infosec.exchange
                    wrote last edited by
                    #16

                    @johntimaeus @Viss

                    sprint and us west/worst were the real banes of my existence.

                    johntimaeus@infosec.exchangeJ 1 Reply Last reply
                    0
                    • viss@mastodon.socialV viss@mastodon.social

                      @johntimaeus @paul_ipv6 im 100% sure this is some fuckery on their part. i downgraded from gig to 500mbit metered because it was less than half the price, and almost immediately afterwards i started getting multiple 2-5 minute outages per day. its gotta be some bullshit logical something or other on their end

                      also, i wouldnt put it past them to introduce deliberate problems just to punish people who decided to give them less money, because its nearly impossible to prove from this end

                      johntimaeus@infosec.exchangeJ This user is from outside of this forum
                      johntimaeus@infosec.exchangeJ This user is from outside of this forum
                      johntimaeus@infosec.exchange
                      wrote last edited by
                      #17

                      @Viss @paul_ipv6

                      Possibly a traffic shaper doing a log or database sync?

                      rootwyrm@weird.autosR 1 Reply Last reply
                      0
                      • paul_ipv6@infosec.exchangeP paul_ipv6@infosec.exchange

                        @johntimaeus @Viss

                        sprint and us west/worst were the real banes of my existence.

                        johntimaeus@infosec.exchangeJ This user is from outside of this forum
                        johntimaeus@infosec.exchangeJ This user is from outside of this forum
                        johntimaeus@infosec.exchange
                        wrote last edited by
                        #18

                        @paul_ipv6 USW was horrible. I had a backup OC48 through them that couldn't achieve one 9 reliability.

                        1 Reply Last reply
                        0
                        • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                          @Viss @paul_ipv6

                          Possibly a traffic shaper doing a log or database sync?

                          rootwyrm@weird.autosR This user is from outside of this forum
                          rootwyrm@weird.autosR This user is from outside of this forum
                          rootwyrm@weird.autos
                          wrote last edited by
                          #19

                          @johntimaeus @Viss @paul_ipv6 nope. It's Cock's "fairness" policy. They intentionally oversell to the breaking point everywhere. Where they can legally offer 'metered' bullshit, they intentionally shove all of those customers into extremely low commit streams so that the unlimited customers can easily squeeze them out. Where they can't do metered bullshit, they just oversell well past the breaking point and tell you to get Internet from someone else then.

                          1 Reply Last reply
                          0
                          • fritzadalis@infosec.exchangeF fritzadalis@infosec.exchange

                            @johntimaeus @paul_ipv6 @Viss
                            Well I mean they were both bad. They just didn't want to run a new line.

                            johntimaeus@infosec.exchangeJ This user is from outside of this forum
                            johntimaeus@infosec.exchangeJ This user is from outside of this forum
                            johntimaeus@infosec.exchange
                            wrote last edited by
                            #20

                            @FritzAdalis @paul_ipv6 @Viss

                            I used to have a three page cheatsheet on getting around problems like that. None were good, but they worked.

                            I got it from an engineer at Fujitsu. Crazy stuff like using 2 pair with an extra loop on one to carry one pair's worth of signal. It schmears the transition, but still gets the job done at 1.5 mhz.

                            1 Reply Last reply
                            1
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • Login

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • World
                            • Users
                            • Groups