movq @www.uninformativ.de

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@movq does not follow you (they may not see your replies!)

Recent Twts

Recent twts from movq

movq @www.uninformativ.de
 (13h ago)

(#m6xngra) @mutefall@twtxt.net IIRC, we gave Juniper a try a while back. đŸ€” Something wasn’t right, but I don’t remember anymore what it was (probably the API not being available or not good enough?). đŸ«€ But this was 5 years ago or more, maybe it has changed 


I hope we can stay with MikroTik for a while. Changing switches is not that much fun. 😂

#3matjxa
movq @www.uninformativ.de
 (2d ago)

(#m6xngra) @prologic@twtxt.net I’ve tcpdump’ed and wireshark’ed the shit out of this. 😂 It’s not very helpful. I’d need to gain insight into the decision making of the switch itself. Why does it drop certain packets? That’s almost impossible to find out (unless it happens to be included in the switch’s logs, which it usually isn’t).

Like @mutefall@twtxt.net said, it’s usually some kind of misconfiguration. Hence you begin to dump the entire switch config into a file and then run diff against the config of a working switch. đŸ€Ł Sometimes this approach works, sometimes it doesn’t 


We recently changed from Cisco to MikroTik switches. At least those switches offer some kind of basic API, which means we can configure them via our config management – instead of using the switch’s web UI or SSH, like some cave men. That should make our life much easier.

Honestly, all the switches I’ve seen so far were total crap. So far, MikroTik is the best thing. Maybe there are actually good switches out there, but they probably cost a ton of money, and we can’t afford that.

#pw7ek7a
movq @www.uninformativ.de
 (3d ago)

(#m6xngra) @prologic@twtxt.net In this particular case: Figuring out why a switch decided not to forward ARP broadcasts to certain switch ports. Like, you connect two devices to the switch ports 3 and 4 and they can ping each other – but when you move one of them to port 5, no ping anymore. So, rather low-level stuff.

Or, we have another switch that intermittently doesn’t respond on its management IP anymore (even when you connect your laptop directly to the switch with no other networking hardware in between). I still haven’t figured out this issue.

#vaybcnq
movq @www.uninformativ.de
 (4d ago)

Spent the last few days debugging network issues at work.

Exhausting. You never get a full picture. You poke a little here, poke a little there, 
 Form a hypothesis and test it. Eventually, maybe, you can narrow it down a bit to some segment or even some component.

A very time consuming process. Even more so if you try not to cause downtimes for your users.

I want a magical device that allows me to look inside a cable/fibre.

But hey, at least we got rid of a bunch of Cisco switches in the process. So there’s that.

#m6xngra