Yet again working on my network stack implementation, and just..
I do not enjoy that Layer 2 has to care about stuff from Layer 3
Or that Layer 3 and 4 are/can be entangled with each other,
instead of all of them being able to just work independent of every other layer
WEH
@k4m1 wdym with l2 caring about l3? packet snooping for building ARP/switching tables?
hugs
That's whole another can of worms,
this complaint was just provoked by remembering that EtherType field in Ethernet frame is used to indicate type of protocol that'll follow x-x
So 0800 for ipv4, 0806 for arp, and so forth
@erincandescent @k4m1 @alina the funny thing is that we designed systems to support a multitude of protocols. then we proceeded to only ever (commonly) use three of them (ARP, IPv4, IPv6)
but fear not! we designed IP to support a multitude of protocols too! and then we proceeded to only really use TCP and UDP. For an unwritten reason everything else has to match one of those now :))))
but fear not! we designed TCP/UDP to support a multitude of protocols too!!! and then we proceeded to block every port other than 80, 443 and 53, because everything is HTTP(S) or DNS now
but fear not! we designed^W slapped websockets on top of HTTP because THERE IS NO GOD
Was trying to write a clever and funny reply, or something, but the "AAA"s summarize it all perfectly 
@ity I wish everything was AAAA now, but way too many things are still A only. 😞
@alina @domi @erincandescent @k4m1
mumble.example.com IN AAAAAAA wss://sakamoto.example.com/mumble
k4m1
dmi 💽 
alina🐾💖✨🏳️⚧️
Erin 💽✨
groff 🇺🇦
ity [unit X-69] - VIOLENT FUCK
Wilfried Klaebe
Stryder Notavi
Dec [{(
)}]
Wolf480pl