Its easy to make the common mistake when your working between different operating systems. One of the most common ones to make is ifconfig and ipconfig.
Just for the record ifconfig is for linux based operating systems and ipconfig is for the windows operating system. To make things a little easier, we can look to set alias so that in the event where by we issue the incorrect command, it will invoke the correct command.
Linux alias firstname.lastname@example.org:~# ipconfig bash: ipconfig: command not found Here we can see that we issue the ipconfig command but its only valid for windows environments. email@example.com:~# alias ipconfig=ifconfig We set the incorrect command first which equals (=) to the correct command. firstname.lastname@example.org:~# ipconfig ens3: flags=4163
mtu 1500 inet 192.168.0.1 netmask 255.255.0.0 broadcast 192.168.255.255 inet6 fe80::f816:3eff:fe31:d2dd prefixlen 64 scopeid 0x20 ether fa:16:3e:31:d2:dd txqueuelen 1000 (Ethernet) RX packets 526 bytes 45008 (43.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 450 bytes 49142 (47.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0