[–] 2 points 3 days ago

It turns out either bmon or Android or the USB dongle doesn't have the capabilities to read real-time bandwidth of mirrored traffic.

Yeah you need promiscuous mode, I highly doubt that's possible on Android without root, and no idea how to do it with root.

THEY JUST ROTATED THE DAMN THING

Haha that sucks. If a device is on the same subnet, you won't need a gateway and DNS server. Like if your switch is 176.1.2.3/24 and your phone is 176.1.2.4/24, then that won't require a gateway. Although they could be doing some L3 switching or something which could break that.

  • source
  • parent
  • context
  • [–] 2 points 4 days ago (4 children)

    bmon

    Oh cool, I haven't seen that before! If it matters, I think all your traffic would appear as RX, since everything would be received by the NIC.

    finally be able to arp-scan the freakin' thing to find its IP

    I'd set a static IP on the switch, so it doesn't try DHCP or something and confuse your ISP's BNG, but if it's already working then I guess it's fine (and idk your ISP's setup).

  • source
  • parent
  • context
  • [–] 2 points 4 days ago* (6 children)

    try to mirror the relevant ports on the switch

    Still looking for such a program.

    I do functionally the same thing on my router, and I mirror it to a system running Clear NDR which is like a network intrusion detection software. So it will also generate events and stuff, as well as simple flow analysis:

    Screenshot of Events in Clear NDR

    I don't think it has a good way to see the speed though, and I use SNMP + Telegraf + Influx + Grafana for that, but there's probably an easier way.

    I guess for more details, I use MikroTik's packet sniffer firewall rule, to encapsulate the first 1024 bytes of a connection with a TZSP header addressed to Clear NDR, but I've done a lot of extra stuff to get that to work, and it's much more designed around basic port mirroring so that'll work great for you.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (3 children)

    Cool! Also if it wasn't obvious, anything running meshtastic will be able to talk to anything else running meshtastic. Like you could get a Wio Tracker L1 (for home assistant) and 2 T-Watches, and they'd all be able to send messages to each other. You can also setup a channel, for a group chat sort of thing.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (5 children)

    I don't use the home assistant integration, but my understanding is you have to configure WiFi and an MQTT server on a node at your house with the meshtastic app (I probably wouldn't use a T-Watch for that, something with a longer external antenna would be better), and point it to your home assistant's MQTT server. Then there's some more configuration to make home assistant send messages and what to do when it receives messages.

    Most meshtastic compatible devices do have a USB port that presents as a serial interface though, so there's probably an unofficial integration that makes use of that too.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (7 children)

    So it can do voice calls?

    Not over meshtastic, and not with the meshtastic firmware. The T-Watches have WiFi & Bluetooth, and are designed to be programmable. So the speaker and microphone could be used by custom firmware to do whatever, like talk over WiFi or answer calls on your phone.

    Was I right about just getting two watches for communication?

    If all you need is simple text based messaging then yep.

    Is there a good crash course on understanding this stuff?

    There's quite a few resources and videos on meshtastic. For the T-Watches themselves, AFAIK not really.

  • source
  • parent
  • context
  • [–] 5 points 1 week ago (9 children)

    it has a camera and microphone, so can you actually do video calls?

    I don't think any of the T-Watches have cameras. But you're right about the meshtastic bandwidth, it's more for some simple messages.

    So if the network isn't great here I assume I can put up my own node.

    Yep, and a node is just another LoRa device, like the T-Watch. If it's just near your house, it should work great. My Wio Tracker L1 picks up a repeater on the other side my suburb, and that gives me some crazy range.

    It doesn't sound like you do, but if you need intercity range, LoRaWAN might also be worth looking into. In Queensland, many city councils (Brisbane, Gold Coast, Moreton Bay) have their own LoRaWAN networks that peer with The Things Network, and you can integrate it with Home Assistant using an integration, or my preferred way is through MQTT. You would probably have to write the firmware yourself with this option though.

  • source
  • parent
  • context
  • [–] 13 points 2 weeks ago

    There's also no livepatches from Ubuntu Pro, and I thought this was the whole idea of livepatches, to patch critical bugs before you have a chance to update the kernel.

    This also isn't the first time I've been annoyed at Ubuntu's response time. Luckily I mostly run Debian, but I certainly won't be using Ubuntu for anything else in the future.

  • source
  • [–] 16 points 3 weeks ago

    Well you can't sign new certs (with the current date) with an expired root/intermediate cert, but the root/intermediate cert expiring doesn't strictly invalidate the already signed certs.

    But I was more talking about the end-user certificates in the previous comment.

  • source
  • parent
  • context
  • [–] 62 points 3 weeks ago* (last edited 3 weeks ago) (8 children)

    FYI, G3 is the only one listed with the issue, the others are fine AFAIK. But if you don't trust eMudhra at all after that, then that's fair.

    Edit: Actually it's the intermediate certs that are compromised, the roots are still fine, but many of them come from the G3 root cert (and Sectigo's AAA Certificate Services)

    Source: https://emudhra.we-have-a-problem.com/

  • source
  • view more: next ›