• 1 Post
  • 94 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle



  • Verizon and ATT just rebrand nokia ONTs and roll some of their own software that is mostly enhanced or changed encryption at L1. Can’t speak for Comcast, I only know about the other two as I’m in a smaller ISP that competes with them.

    They use have L2 onts that don’t have any gateway functions, just fiber to ethernet with some extra overhead to monitor the connection between the hose and shelf.

    The ONT-on-a-stick units do the same thing, just a more compact and expensive interface that doesn’t have great support, unless comcast or running all home run fibers where they can just provide a straight SFP instead of doing any optical splitting.


  • No, you are likely looking at an ONT (optical network terminal), and it is not a router. Even with a port that accepts the fiber (sfp or sfp+ for 10g) on your equipment, the OLT (optical line terminal) likely will not provide you with service.

    If you were to match the wavelengths the ISP is using you are likely to become a “rogue” on their PON that can knock out service for other customers that share the same passive network as you.

    I make assumptions about you being on PON since you say AT&T, generally all I have ever seen from them are passive networks (one fiber with splitters for 1 port to many customers) unless you are paying extra for “dedicated” ($$$$$) internet.

    If they are using a ONT with an “RG” (residential gateway) which is the typical “all in one” you can request the gateway service can be removed and replaced with a layer 2 bridge, where you’re router/firewall gets the “external” addressing and there is nothing being done by the ISP equipment other than sending you traffic and OAM (operations, administration, and maintenance; usually check or alert for light levels, software status, if a part of the ONT fails etc).


  • There are definitely multiple ways they can block traffic to a site, but you have to be sending traffic through them or using DNS from them, or placing your site behind them using them for protection from denial of service attacks.

    Firstly, if you pay or use their free “anti-ddos” services, what is really happening is all traffic to your site is being sent through their network. Should you violate their terms of service, they can choose to terminate that traffic.

    DNS is Domain name service, where I want to visit example.com, and DNS tells the computer to go to 12.34.56.78. The DNS server your computer will ultimately use can be assigned by your ISP, manually configured by your network administrator, etc. One choice you can use, that is regarded by some as a good choice due to response time, is cloudflare. When cloudflare decides to block a site, one method they may use is to redirect DNS replies for that domain to a placeholder that indicates this site is blocked, or reply with NXDOMAIN - Non-eXistent domain.

    An ISP could also choose to buy bandwidth from cloudflare as an upstream provider. For cloudflare enforcing a block, they would redirect traffic destined for any of address they want to a placeholder just like DNS.

    A more aggressive, and dangerous tactic that could cause global outages for a site, would be to falsely claim address as their own to the public internet with Border Gateway Protocol - BGP, then redirect/blackhole it.


  • Certain equipment need to support IPv6 in certain ways, but not necessarily be assigned a v6 address. Anything OSI layer-2 or layer-1 will not need to “explicitly” support v6, with exceptions. The network terminal (ONT/modem) usually needs to support v6, as they will generally have security features to prevent a subscriber from using random addresses they were not assigned, or using multiple.

    At a minimum, core/edge routing supporting v6, premise equipment supporting v6, at least one upstream provider or transit provider that supports v6 in combination with diverse peering with v6, and ancillary servers to provide DHCPv6 and DNS6. Generally I would assume a provider adding v6 is going to do dual stack, which is great for usually not being NATed on at least one IP stack.

    What’s nice about v6 being so old… is that a lot of the equipment they are using will support v6. Most consumer routers just need to get a dhcp reply with v6 with default settings.

    We are deploying v6 to both brand new fiber customers and very legacy dsl customers without widespread equipment replacement now, at a US based ISP, but I don’t work at Bell or have any idea of what other hurdles they may have that we don’t.



  • I work for an telco and I have seen a lot of times that a contract for using preexisting underground infrastructure that have lids like this has a section requiring that they are returned to the same location and orientation when the enclosure is sealed.

    Whoever owns that, municipality or private, will probably take a complaint about it, and may pass it to whoever is responsible or owns the plant inside.


  • jake_jake_jake_@lemmy.worldtoMemes@lemmy.mlRAM
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    1 month ago

    I am working to decommission a windows server, which is currently using 500gb ram, and i have moved all functions to a different application, same purpose and very similar underlying methodology… 32gb of ram on linux. it’s crazy how much bloat windows admins are willing to accept.


  • yes, they can get really startled by that, but with ours I have noticed that she seems to even get spooked by the temperature of the mattress sometimes. it can help to gently hold their arms and legs still for a minute after putting them down because they fling them all around and wake themselves up








  • For indoor cameras, I use TP-Link tapo wireless cameras, and hikvision for outdoor. I put all of them on an isolated camera wlan and vlan without internet. the tapos work fine without internet access, but the status light will always be orange as it tries to reach some tplink aws IP to verify connectivity.

    All the hikvision cameras and tapos support rtsp.