Using tcpdump to see only incoming or outgoing traffic
In the normal course of events, implementations of ' tcpdump 'report on packets going in both directions, which is to say itreports both packets received and packets sent. Normally this isn'tconfusing and you can readily tell one from the other, but sometimessituations aren't normal andyou want to see only incoming packets or only outgoing packets( this has come up before ). Modernversions of tcpdump can do this, but you have to know where tolook.
If you're monitoring regular network
What a FreeBSD kernel message about your bridge means
Suppose, not hypothetically , that you're operatinga FreeBSD based bridging firewall (or some other bridge situation) andyou see something like the following kernel message:
kernel: bridge0: mac address 01:02:03:04:05:06 vlan 0 moved from ix0 to ix1kernel: bridge0: mac address 01:02:03:04:05:06 vlan 0 moved from ix1 to ix0
The bad
The issue with DNF 5 and script output in Fedora 41
These days Fedora uses DNF as its high(er) level package managementsoftware, replacing yum. However, there are multiple versions ofDNF, which behave somewhat differently. Through Fedora 40, thedefault version of DNF was DNF 4; in Fedora 41, DNF is now DNF 5.DNF 5 brings a number of improvements but it has at least oneissue that makes me unhappy with it in my specific situation.Over on the Fediverse I said :
Oh nice, DNF 5 in Fedora 41 has
WireGuard's AllowedIPs aren't always the (WireGuard) routes you want
A while back I wrote about understanding WireGuard's AllowedIPs , and also recently I wrote about how differentsorts of WireGuard setups have different difficulties , where one of the challenges for somesetups is setting up what you want routed through WireGuardconnections. As Ian Z aka nobrowser recently noted in a comment onthe first entry, these days many WireGuard related programs (suchas wg-quick and NetworkManager) will automatically set routes foryou based on AllowedIPs. Much of the time this will work fine, butthere are situations
There are different sorts of WireGuard setups with different difficulties
I've now set up WireGuard in a number of different ways, some ofwhich were easy and some of which weren't. So here are my currentviews on WireGuard setups, starting with the easiest and going tothe most challenging.
The easiest WireGuard setup is where the 'within WireGuard' internalIP address space is completely distinct from the outside space,with no overlap. This makes routing completely straightforward;internal IPs reachable over WireGuard aren't reachable in any otherway, and external IPs aren'
The programmable web browser was and is inevitable
In a comment on my entry on why the modern web is why web browserscan't have nice things , superkuh wrote in part:
In the past it was seen as crazy to open every executable filesomeone might send you over the internet (be it email, ftp, web, orwhatever). But sometime in the 2010s it became not only acceptable,but standard practice to automatically run every executable sent toyou by any random endpoint on the internet.
For 'every executable' you
Rejecting email at SMTP time based on the From: header address
Once upon a time (a long time ago), filtering and rejecting emailbased on the SMTP envelope sender (the SMTP MAIL FROM) was a generallysufficient mechanism to deal with many repeat spam sources. Itdidn't deal with all of them but many used their own domain in theenvelope sender, even if they send from a variety of different IPaddresses. Unfortunately, the rise of (certain) mail service providershas increasingly limited the usefulness of envelope sender addressfiltering, because an increasing number of the
The modern web is why web browsers don't have "nice things" (platform APIs)
Every so often I read something that says or suggests that the bigcombined browser and platform vendors (Google, Apple, and to alesser extent Microsoft) have deliberately limited their browser'saccess to platform APIs that would put "progressive web applications"on par with native applications. While I don't necessarily want tosay that these vendors are without sin, in my view this vastlymisses the core reason web browsers have limited and slow movingaccess to platform APIs. To put it simply, it's
My unusual X desktop wasn't made 'from scratch' in a conventional sense
There are people out there who set up unusual (Unix) environmentsfor themselves from scratch; for example, Mike Hoye recently wrote Idiosyncra .While I have an unusual desktop , Ihaven't built it from scratch in quite the same way that Mike Hoyeand other people have; instead I've wound up with my desktop througha rather easier process.
It would be technically accurate to say that my current desktopenvironment has been built up gradually over time (including overthe time I've been writing Wandering
I'm firmly attached to a mouse and (overlapping) windows
In the tech circles I follow, there are a number of people who arefirmly in what I could call a 'text mode' camp ( eg , also ). Over onthe Fediverse, I said something in an aside about my personaltastes :
(Having used Unix through serial terminals or modems+emulators thereofback in the days, I am not personally interested in going back to asingle text console/window experience, but it is certainly an optionfor simplicity.)
(Although I didn't put