News for hackers. Stuff that matters.
Re:Identifying satellite interference due to GSM rebroadcast... by Aloha on Saturday September 30, 2017 @12:54AM (#15371311)
Tracing down RFI sources can be immensely challenging - I remember reading of one case where the tower itself became a radiating element and a source of RFI.

https://www.thebdr.net/articles/warstories/trenches/trenches...

Here is another where the source of the RFI was a totally unexpected source.

https://www.thebdr.net/articles/warstories/neighbors/bug.pdf

Re:Identifying satellite interference due to GSM rebroadcast... by farva on Saturday September 30, 2017 @04:45AM (#15371916)
For an example of more malicious interference, see https://en.wikipedia.org/wiki/Captain_Midnight_broadcast_sig...
Re:Identifying satellite interference due to GSM rebroadcast... by cameldrv on Saturday September 30, 2017 @05:39AM (#15372047)
Even weirder and more wonderful, and still no one knows who it was: https://www.youtube.com/watch?v=tWdgAMYjYSs
Re:Identifying satellite interference due to GSM rebroadcast... by Spare_account on Saturday September 30, 2017 @03:00PM (#15374466)
"Bandwidth limit exceeded"

Here's the same PDF from the Internet Archive:

https://web.archive.org/web/20170930150048/http://data.satir...

Re:Identifying satellite interference due to GSM rebroadcast... by 13of40 on Saturday September 30, 2017 @02:44AM (#15371604)
I'm sorry for asking this, but can anyone tl;dr the slideshow? The satellite was blindly receiving and rebroadcasting signals from a misbehaving cell tower?
Re:Identifying satellite interference due to GSM rebroadcast... by farva on Saturday September 30, 2017 @02:50AM (#15371613)
Re:Identifying satellite interference due to GSM rebroadcast... by 13of40 on Saturday September 30, 2017 @03:47AM (#15371778)
So the satellite was rebroadcasting the signal at a frequency where it could interfere with GSM? Does the satellite just rebroadcast whatever it receives, verbatim?
Re:Identifying satellite interference due to GSM rebroadcast... by farva on Saturday September 30, 2017 @04:22AM (#15371873)
Block up-converter (BUC) at uplink site (in this case, likely part of a VSAT terminal or Satellite Internet "antenna") takes L-Band (950-1525mhz) input via cable, converts it to C-band uplink (5850-6425mhz) frequency, and transmits to satellite. Satellite then rebroadcasts verbatim at C-band downlink frequency (3400-4200mhz). Except that one of the inputs didn't have a cable or filter attached so it picked up a GSM signal at 936-960mhz. This caused interference on the satellite.
Re:Identifying satellite interference due to GSM rebroadcast... by makomk on Saturday September 30, 2017 @01:55PM (#15374085)
For further context, the reason for this slightly convoluted setup is that normal coaxial cables are really lossy at the high frequencies used to communicate with satellites, so most systems use lower frequency bands on the cable runs and convert the signals by a fixed frequency offset at the actual antenna. It just so happens that the block of frequencies used on the cable runs is similar to common mobile phone frequencies.
Re:Identifying satellite interference due to GSM rebroadcast... by eecc on Saturday September 30, 2017 @03:57AM (#15371800)
Now that was some debugging! Especially liked the part where they grabbed an old GSM to decode the signal. KISS at its best
Re:Identifying satellite interference due to GSM rebroadcast... by sbierwagen on Saturday September 30, 2017 @02:13AM (#15371509)
Context? Why was the signal being rebroadcast? What was the point?
Re:Identifying satellite interference due to GSM rebroadcast... by farva on Saturday September 30, 2017 @02:46AM (#15371607)
TLDR: Unterminated input port at satellite uplink site acted as antenna, picking up nearby cell tower by accident. Fix: put a terminator on the port.
Re:Identifying satellite interference due to GSM rebroadcast... by jwfxpr on Saturday September 30, 2017 @02:07AM (#15371495)
(2011)
Re:Identifying satellite interference due to GSM rebroadcast... by dang on Saturday September 30, 2017 @04:08AM (#15371831)
Added. Thanks!