[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] [Eth0](/topic/eth0) ### Top Social Posts *Showing only X posts for non-authenticated requests. Use your API key in requests for full results.* "@the_void_is_nil @SwitchSpace1 @Avamander @LundukeJournal It all depends on how many nics you're dealing with. If you don't have multi nics eth0 out of the box is the simpler config bc the level of abstraction is perfect in that case" [X Link](https://x.com/Droogstoppel13/status/1982207948228100344) [@Droogstoppel13](/creator/x/Droogstoppel13) 2025-10-25T22:09Z 1501 followers, X engagements "@the_void_is_nil @Avamander @Droogstoppel13 @LundukeJournal Well I also manage a hybrid farm of several hundred cloud and on-premise server as well as distributed VMs and devices in the field I still disable the "predictable" naming. I find that the predictability of eth0 being the first interface is easier" [X Link](https://x.com/SwitchSpace1/status/1982203101646913962) [@SwitchSpace1](/creator/x/SwitchSpace1) 2025-10-25T21:50Z XX followers, XX engagements "@SwitchSpace1 @Avamander @Droogstoppel13 @LundukeJournal They are actually. You should try actually reading docs sometime; it's very helpful. The legacy naming is literally "whichever one the kernel sees first gets eth0". I manage boxes with 4+ NICs some with multiple interfaces per-NIC. (con't)" [X Link](https://x.com/the_void_is_nil/status/1982097435070529654) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-25T14:50Z XXX followers, XX engagements "@Avamander @Droogstoppel13 @LundukeJournal "Predictable" interface names. riiiigght ens192 and ens135.1 are soo much more intuitive than eth0 and eth1. I have never had an issue in the last XX years with interfaces. Udev is fine for linking a name to a mac if needed" [X Link](https://x.com/SwitchSpace1/status/1981863566216138951) [@SwitchSpace1](/creator/x/SwitchSpace1) 2025-10-24T23:21Z XX followers, XX engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
Showing only X posts for non-authenticated requests. Use your API key in requests for full results.
"@the_void_is_nil @SwitchSpace1 @Avamander @LundukeJournal It all depends on how many nics you're dealing with. If you don't have multi nics eth0 out of the box is the simpler config bc the level of abstraction is perfect in that case"
X Link @Droogstoppel13 2025-10-25T22:09Z 1501 followers, X engagements
"@the_void_is_nil @Avamander @Droogstoppel13 @LundukeJournal Well I also manage a hybrid farm of several hundred cloud and on-premise server as well as distributed VMs and devices in the field I still disable the "predictable" naming. I find that the predictability of eth0 being the first interface is easier"
X Link @SwitchSpace1 2025-10-25T21:50Z XX followers, XX engagements
"@SwitchSpace1 @Avamander @Droogstoppel13 @LundukeJournal They are actually. You should try actually reading docs sometime; it's very helpful. The legacy naming is literally "whichever one the kernel sees first gets eth0". I manage boxes with 4+ NICs some with multiple interfaces per-NIC. (con't)"
X Link @the_void_is_nil 2025-10-25T14:50Z XXX followers, XX engagements
"@Avamander @Droogstoppel13 @LundukeJournal "Predictable" interface names. riiiigght ens192 and ens135.1 are soo much more intuitive than eth0 and eth1. I have never had an issue in the last XX years with interfaces. Udev is fine for linking a name to a mac if needed"
X Link @SwitchSpace1 2025-10-24T23:21Z XX followers, XX engagements
/topic/eth0/posts