33 ms·
More addon tools simply proves the point. Task / BSD / Linux set ip / ifconfig / ifconfig or now "ip" which is extremely confusing wifi / ifconfig / iwconfig
by GalacticDomin8r 13y ago
More addon tools simply proves the point.
Task / BSD / Linux
set ip / ifconfig / ifconfig or now "ip" which is extremely confusing
wifi / ifconfig / iwconfig
speed / ifconfig / miitool or ethtool
duplex / ifconfig / miitool or ethtool
vlan / ifconfig / vlan
wol / ifconfig / miitool or ethtool
bridge / ifconfig / brctl
link aggregation / ifconfig / flags while loading module OR use distro network config scripts and restart all networking or reboot server
Want find out which nic is occupying ethX perhaps for tuning or scripting etc?
Linux = complicated, by distro/version
FreeBSD = nic by device eg em0
- deno 13y ago> Linux = complicated, by distro/version Most Linux distros are adopting consistent naming schemes, using biosdevname algorithm, e.g. https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming https://fedoraproject.org/wiki/Features/ConsistentNetworkDev... > More addon tools simply proves the point. I was only showing that comparing Linux’s ifconfig with BSD’s ifconfig is not fair, not really making any point. I don’t see how this is all that confusing though, you get ip for managing routing and iw/ethtool/etc for managing interfaces or creating interfaces on lower networking levels or device level. It’s just different.