Re: ISP data collection from home routers
Hi Giovane On 24.03.22 11:43, Giovane C. M. Moura via NANOG wrote: Hello there, Several years ago, a friend of mine was working for a large telco and his job was to detect which clients had the worst networking experience. To do that, the telco had this hadoop cluster, where it collected _tons_ of data from home users routers, and his job was to use ML to tell the signal from the noise. I remember seeing a sample csv from this data, which contained _thousands_ of data fields (features) from each client. I was _shocked_ by the amount of (meta)data they are able to pull from home routers. These even included your wifi network name _and_ password! (it's been several years since then). Creepy. And the provided CPE usually sucks too, what a deal... I feel validated in preferring to use my own router at home. And home users are _completely_ unaware of this. So my question to you folks is: - What's the policy regulations on this? I don't remember the features (thousands) but I'm pretty sure you could some profiling with it. For the policies probably this is a good place to start if you are interested in US legislation (you didn't specify any location), as it's not federally regulated from what I gather: https://www.ncsl.org/research/telecommunications-and-information-technology/2019-privacy-legislation-related-to-internet-service-providers.aspx - Is anyone aware of any public discussion on this? I have never seen it. I remember reading some discussion around ISPs selling browsing behavior data that they collect from their subscribers in the tech press during Pai's term as the head of the FCC. It was probably on Ars Technica or Techdirt. Thanks, Giovane Moura Best, Joel -- Joel Busch, Network SWITCH Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 30, direct +41 44 268 16 58 https://switch.ch https://swit.ch/linkedin https://swit.ch/twitter
Re: Unimus as NCM (Network Configuration Management) Tool
On 04.04.2024 09:06, Mark Tinka wrote: RANCID works perfectly for Cisco, Juniper, Arista, Brocade (Foundry) and HP. They are also known to support other obscure vendors. Can confirm for Cisco. We use it for ECI (now Ribbon) gear as well, just with our local modifications. We copied the Juniper scripts and modified them to not set some CLI states and to adapt the commands that are run. It's not that complicated to modify. Joel Busch AS559 SWITCH
Re: constant FEC errors juniper mpc10e 400g
, Physical link is Up Interface index: 226, SNMP ifIndex: 800 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled Pad to minimum frame size: Disabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Schedulers : 0 Last flapped : 2024-04-17 13:55:28 CDT (00:36:19 ago) Input rate : 0 bps (0 pps) Output rate: 0 bps (0 pps) Active alarms : None Active defects : None PCS statistics Seconds Bit errors 0 Errored blocks 0 Ethernet FEC Mode : FEC119 Ethernet FEC statistics Errors FEC Corrected Errors 801787 FEC Uncorrected Errors 0 FEC Corrected Errors Rate2054 FEC Uncorrected Errors Rate 0 Link Degrade : Link Monitoring : Disable Interface transmit statistics: Disabled Logical interface et-7/1/4.0 (Index 420) (SNMP ifIndex 815) Flags: Up SNMP-Traps 0x4004000 Encapsulation: ENET2 Input packets : 1 Output packets: 1 Protocol inet, MTU: 1500 Max nh cache: 75000, New hold nh limit: 75000, Curr nh cnt: 1, Curr new hold cnt: 0, NH drop cnt: 0 Flags: Sendbcast-pkt-to-re Addresses, Flags: Is-Preferred Is-Primary Destination:10.10.10.76/30 <http://10.10.10.76/30>, Local: 10.10.10.77, Broadcast: 10.10.10.79 -- -Aaron -- -Aaron -- Joel Busch, Network SWITCH Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 30, direct +41 44 268 16 58
Re: Compiling RTG on EL9
Hi Nick On 13.07.2024 00:19, Nick Hilliard wrote: Whoa, that's some blast from the past. At the time of the latest release in 2003, rtg was still duking it out with mrtg and cricket, which was used by the cool kids. Still some good memories there. Who knew we could be part of the cool kids for once! We're still keeping our cricket 1.0.5 from 2004 alive over here, I just recently rebased our local mods on the debian maintainer version 1.0.5-22. Joel
Re: ACX6360-OX Question
I second the method Jared is suggesting, go hop-by-hop, check light levels, and make use of loopback modes to establish which partial sections may be working already. (If any loopback is available, I don't know your platform specifically) On 08.01.2025 22:19, Jared Mauch wrote: make sure that if there's any payload options thos eare set correctly, be they otu or odu for your 100g signal. Additionally, check that your modulation format and FEC settings are the same on both ends. It seems that at least Juniper's own CFP2-DCO-T-WDM-HG have a variety of settings, assuming you are using those. -Joel
