• chevron_right

      Cloudflare Tunnelling

      pubsub.slavino.sk / warlord0blog · Tuesday, 16 January - 18:48 edit

    Using Cloudflare, it is possible to connect to a private internal service via a tunnel. This enables the interaction of a DNS name to get proxied through Cloudflare, and over a tunnel into your secure application – without exposing the application ports to the internet. This means none of our internal services need be published via &ellipsisRead the full post »

    Značky: #Networking, #Web, #Linux, #cloudflare

    • No chevron_right

      i2p Anonymity Network Notes ep. 1

      𝖈𝖍𝖚𝖓𝖐 · pubsub.toofast.vip / notes · Sunday, 26 November - 10:51 edit · 1 minute


    https://geti2p.net/en/

    https://geti2p.net/en/docs/how/intro

    https://geti2p.net/en/docs/how/threat-model

    https://geti2p.net/en/docs/protocol

    https://geti2p.net/en/docs/transport


    "Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the originator of some communication and not the recipient, or the other way around. I2P is designed to allow peers using I2P to communicate with each other anonymously — both sender and recipient are unidentifiable to each other as well as to third parties." from https://geti2p.net/en/docs/how/intro

    "The network itself is message oriented - it is essentially a secure and anonymous IP layer, where messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP packets."

    ...

    So my next questions, in parallel to these links, is for starters what kind of encryption happens that makes tranmissions on i2p network 'anonymous' ? Then I'm curious, how does using a cryptographic hash for a destination or a host (in place of where you'd think an IP address goes, in terms of routing traffic) or an origin host provide anonymity? Or is that it's intention? I'm aware of a couple of fun i2p resources, that are way beyond my current (lack of) comprehension of the i2p network. I will share in comments.


    #notes #computing #i2p #anonymity #networking

    • chevron_right

      RIP to my 8-port Unifi switch after years and years of Texas outdoor temps

      news.movim.eu / ArsTechnica · Friday, 20 October - 13:17 · 1 minute

    Photograph of a US-8-150W switch in situ

    Enlarge / My original US-8-150W shortly before being replaced. Don't judge my zip-tie mounting job—it held for eight years! (credit: Lee Hutchinson)

    This morning, I'd like to pour one out for a truly awesome piece of gear that did everything I asked of it without complaint and died before its time: my Unifi 8-port POE switch, model US-8-150W. Farewell, dear switch. You were a real one, and a lightning strike took you from us too soon.

    I picked up this switch back in January of 2016 , when I was ramping up my quest to replace my shaky home Wi-Fi with something a little more enterprise-y. The results were, on the whole, positive (you can read about how that quest turned out in this piece right here , which contains much reflection on the consequences—good and bad—of going overboard on home networking), and this little 8-port switch proved to be a major enabler of the design I settled on.

    Why? Well, it's a nice enough device—having 802.3af/at and also Ubiquiti's 24-volt passive PoE option made it universally compatible with just about anything I wanted to hook up to it. But the key feature was the two SFP slots, which technically make this a 10-port switch. I have a detached garage, and I wanted to hook up some PoE-powered security cameras out there, along with an additional wireless access point. The simplest solution would have been to run Ethernet between the house and the garage, but that's not actually a simple solution at all—running Ethernet underground between two buildings can be electrically problematic unless it's done by professionals with professional tools, and I am definitely not a professional. A couple of estimates from local companies told me that trenching conduit between my house and the garage was going to cost several hundred dollars, which was more than I wanted to spend.

    Read 5 remaining paragraphs | Comments

    • chevron_right

      Network-watching gadget Monitor-IO chooses a graceful, owner-friendly death

      news.movim.eu / ArsTechnica · Tuesday, 11 April, 2023 - 15:07 · 1 minute

    Monitor-IO, amidst various geeky things

    Enlarge / The Monitor-IO in its natural habitat, glowing green to let you know that everything is copacetic with the network to which it's connected. (credit: Jim Salter)

    Monitor-IO was a gadget that did one thing: live near a router and tell you how its network is doing. It did this both with detailed reports you could access from the local network and with a screen that glowed one of three colors: green for good, purple for problems, and red for dead. It could replace, or at least augment, typing a bunch of IP addresses into a browser and waiting for them to time out.

    We liked the device when we reviewed it in August 2018 , despite our broad understanding of it as a "butter-passing robot," a device that relays information you could otherwise find out on your own. It had, beyond color-coded awareness, "obvious technical chops and real, careful attention to detail" in how it measured and what it could report. However, we also noted that the $100 price made sense for a small business but "might be a bit steep" for a household on a tight budget.

    Monitor-IO seems to have run out of people willing to pay for better network awareness. In an "End-of-service" notice posted on its site , the company cites "rising costs and supply chain issues," among other "numerous headwinds." Faced with no better option, Monitor-IO is shutting down its business and monitoring service on April 15, 2023. (Support will be offered through May 30, 2023.)

    Read 5 remaining paragraphs | Comments

    • chevron_right

      Google Nest and Android devices are now Matter controllers (for future devices)

      news.movim.eu / ArsTechnica · Thursday, 15 December, 2022 - 18:36 · 1 minute

    Google devices shown with a Matter logo

    Enlarge / A whole bunch of Google devices, including Android phones, can now control Matter devices. Those devices will be here at some point, perhaps soon. (credit: Google)

    The promise of Matter —the future where smart-home devices easily nestle into your home, regardless of what other devices or speakers you use—just got a bit closer today. Google announced that Nest and Android devices are Matter-enabled, allowing them to set up and control other Matter devices—that mostly don't exist yet.

    If your Android device runs version 8.1 or higher and has Google Play Service 22.48.14 or newer, you can use it to pair a Matter-compatible device with other Matter products and controllers. In these early post-launch Matter days , that means you can pair a few Eve devices that got their Matter firmware update three days ago. Or you can wait on a few Nanoleaf bulbs, some Level smart locks, or whatever else is to come. Nest devices that have quietly received their latest firmware updates can now be used to control that same (quite limited) set of devices.

    The appeal of the moment is that you could, technically, use an Android phone to put an Eve device onto your Matter network, then use an iOS Home app, Samsung's SmartThings, or an Alexa speaker (when those are updated in early 2023) to actually control that device. Alternatively, devices you brought onto the network with an iOS device could be controlled from a Google Nest Hub or speaker or other Nest device.

    Read 3 remaining paragraphs | Comments

    • chevron_right

      Manjaro – Static IP Address

      pubsub.slavino.sk / warlord0blog · Tuesday, 1 November, 2022 - 18:19 edit

    It surprised me today that all of my Manjaro builds are using DHCP. I needed to make one of the devices a static IP, as it delivers DHCP, and would be a cyclic relationship if it tried to get an IP address from itself before it enabled the interface used to give out IP addresses. &ellipsisRead the full post »

    Značky: #Networking, #dhcp, #manjaro, #Linux

    • chevron_right

      Redditor acquires decommissioned Netflix cache server with 262TB of storage

      news.movim.eu / ArsTechnica · Thursday, 27 October, 2022 - 21:26 · 1 minute

    An Open Connect Appliance server from around 2013 that a Redditor acquired.

    Enlarge / An Open Connect Appliance server from around 2013 that a Redditor acquired. (credit: PoisonWaffle3 / Reddit )

    A Reddit user named PoisonWaffe3 recently acquired a 2013-era Netflix cache server that had been pulled from service and wiped for disposal, which marks a rare occasion the public has been able to get a look at the mysterious hardware, Vice reports .

    The decommissioned cache server—called an "Open Connect Appliance" (or OCA)—operated as part of Netflix's Open Connect content delivery network. Open Connect is a network of servers around the world embedded with local ISPs that contain local copies of Netflix video content, accelerating the delivery of that content to Netflix viewers by putting it as close to the viewers as possible (both geographically and from a perspective of network hops).

    Netflix provides plenty of high-level documentation about Open Connect on its website, but what isn't widely known is what specific components make the Open Connect servers tick—especially one that is almost a decade old. After removing three screws, PoisonWaffle3 took a look inside their unit and discovered a "pretty standard" SuperMicro motherboard, an Intel Xeon CPU (E5 2650L v2), 64GB of DDR3 RAM, 36 7.2TB Western Digital hard disks (7,200 RPM), six 500GB Micron SSDs, a pair of 750-watt power supplies, and one quad-port 10-gigabit Ethernet NIC card. In total, the server contains "262TB of raw storage," according to PoisonWaffle3.

    Read 3 remaining paragraphs | Comments

    • chevron_right

      WireGuard Gnome Extension

      pubsub.slavino.sk / warlord0blog · Monday, 24 October, 2022 - 16:50 edit

    This gives the users a very convenient means of enabling and disabling WireGuard tunnels. Install the Extension from: https://extensions.gnome.org/extension/3612/wireguard-indicator/ Configuration You have two ways to configure WireGuard. Use it from the command line using wg-quick or use it as a systemd service. systemd and Network Manager I like to use it as a service, which &ellipsisRead the full post »

    Značky: #gnome, #vpn, #Networking, #wireguard, #Linux