Live data from Hacker News

RouterOS – Communications Assistance for Law Enforcement Act (2012)

wiki.mikrotik.com

51–57 of 57 posts

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#51
It's a small router world.

Some SOHO networking devices made by Microtik, QNAP and Ubiquiti contain Arm SoCs made by AWS (Annapurna Labs), https://en.wikipedia.org/wiki/Annapurna_Labs

The venerable PC Engines APU2 is a fanless x86 AMD 10W TDP router with 4GB ECC RAM, TPM 2.0 and GPIO pins, open schematics and coreboot, which can run pfSense, OPNsense, OpenBSD, Linux, FreeBSD and OpenWRT, with virtualization support. Constrained by supply chain at present. mPCIe slots for WiFi, LTE & mSATA.

Ubiquiti ERLite-3 can run Linux and OpenBSD (octeon/MIPS).

There are some generic Intel-based small routers, https://www.servethehome.com/topton-intel-j4125-4x-i225-fanl...

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#52
post #40

Earlier quoted context omitted.

How so? Unless you own a router with CALEA capabilities and specifically configure it to log all of your data, it's not going to snitch on you.

> router with CALEA capabilities and specifically configure it to log all of your data the point is that in the US this [the device you own snitching on you] is required by law https://en.m.wikipedia.org/wiki/Communications_Assistance_fo...

You're misinterpreting it. CALEA requires that service providers have the capability to do interceptions when requested by law enforcement. It has absolutely nothing to do with end-user devices.

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#53
post #52

Earlier quoted context omitted.

> router with CALEA capabilities and specifically configure it to log all of your data the point is that in the US this [the device you own snitching on you] is required by law https://en.m.wikipedia.org/wiki/Communications_Assistance_fo...

You're misinterpreting it. CALEA requires that service providers have the capability to do interceptions when requested by law enforcement. It has absolutely nothing to do with end-user devices.

> It has absolutely nothing to do with end-user devices.

absolutely nothing ? are you sure about that

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#54

Go address some of the posters "why is the front page worthy" - I'm not surprised that 3 letter agencies get all the data they want, but very often it's very covert and not so "official".

Lawful interception is not for "three letter agencies", but for the police (TLAs have their own totally different ways to get this data, in the US they even have their own courts for this). So these are generally documented, judicial processes.

Lawful interception is precisely not made for "three letter agencies", since the latter derive the majority of their power from not spying on the law subjects of their own country. Although the US have of course intentionally muddled this with FISC and at times outright disregard for that simple principle.

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#55

Go address some of the posters "why is the front page worthy" - I'm not surprised that 3 letter agencies get all the data they want, but very often it's very covert and not so "official".

Edit: I meant to type To, not Go. Go makes no grammatical sense :/

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#56

Go address some of the posters "why is the front page worthy" - I'm not surprised that 3 letter agencies get all the data they want, but very often it's very covert and not so "official".

"why is this on the front page?" because someone found and read this wiki and decided to share it with others who also found it interesting so they upvoted it. now here we are

No no, I'm in agreement of this post being relevant, I typoed :(

Re: RouterOS – Communications Assistance for Law Enforcement Act (2012)

#57

Not sure why this is on the front page, but to clarify it's required by the FCC [0] for carriers. Microtik, just like every other network vendor, has this in their product (port mirroring for law enforcement) so that they can check the box. CALEA has been around since the 90s [1]. [0] https://www.fcc.gov/public-safety-and-homeland-security/poli... [1] https://en.wikipedia.org/wiki/Communications_Assistance_for_...

I found this interesting insofar as it is somewhat rare for endpoint CPEs to have these features baked in, in particular with any sort of CALEA semantics. This is almost always a burden pushed on the transitory service providers upstream from the device. Network device OEMs, in my experience running an ISP (in addition to both making routers and white-labeling them for our service), have never been held to the CALEA…

> I found this interesting insofar as it is somewhat rare for endpoint CPEs to have these features baked in, in particular with any sort of CALEA semantics.

This isn't targeting CPE equipment - MicroTik is baking into their unified OS. If you're a service provider you don't configure CALEA in the CPE, you configure it upstream in the headend where all traffic from your customers egress your network. It's much easier to grab it all at the bottleneck than to have data streaming over your expensive last mile twice for each customer, that doesn't make any network architecture or OpEx sense. It's just easier to make CALEA a function of RouterOS vs target specific models. There's nothing specific about the hardware that's required to implement the functionality.

Post reply on HN