#ifconfig — Public Fediverse posts

@da_667 why not replace the containerism with more vm, i learned today some container setup have built in ci/cd pipelines which was pretty interesting and all the tests that get done...the thing that creeped me out the most was security onion and malcolm running so many inf for the bvarious conatainer #ifconfig #did you fuck with it?

Thank you for the reaction Alan. Now I know a bit more from that part of History

@alanc @JdeBP

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Thank you for the reaction Alan. Now I know a bit more from that part of History

@alanc @JdeBP

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Thank you for the reaction Alan. Now I know a bit more from that part of History

@alanc @JdeBP

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Thank you for the reaction Alan. Now I know a bit more from that part of History

@alanc @JdeBP

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Thank you for the reaction Alan. Now I know a bit more from that part of History

@alanc @JdeBP

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

@Radio_Azureus

#Illumos (and thus #OmniOS, #SmartOS, #Tribblix, et al.) has #ifconfig as well.

Indeed, some of its tooling, such as for service management, has been stable since the late 1980s; whereas the BSDs went through some churn in this area in the 1990s and early 2000s.

https://illumos.org/man/8/ifconfig

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

@vermaden @omar
I always use alsamixer -c0 up to cxx from the OSS ALSA period since it's ncurses based & faster than GUI programs.

Many things in Linux were changed for good reason, but some are questionable. I don't use systemD init is easier to maintain. It aint broke so KISS

Pipewire is fun to add FX in my signal chain to my DAW, but for serious work I have a physical FX rack.
I love pavucontrol

I understand why Wayland was made and only have it on my SBC Raspberry Pi5

#Ifconfig #ip #init #systemD #Xorg #Wayland #programming #pipewire #ALSA #OSS

In light of recent reports I thought about adding AF_VSOCK support (if that is meaningful) to the #nosh toolset's #ifconfig .

It turns out that there's no vsock device on my Debian development machine.

I do not have the time at the moment to look into this more thoroughly.

@lymenzies

If you want a FreeBSD-like ifconfig on Linux-based operating systems, I made one. I needed the same syntax across both.

http://jdebp.info/Softwares/nosh/

http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml

#ifconfig #FreeBSD #nosh

maybe i should try with usb live iso first #iwconfig #ifconfig #ip link

@Larvitz

2.

Probably best to illustrate how ifconfig handles netmasks too.

3.

Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.

#FreeBSD #procstat #fstat #iostat #ifconfig #netstat

@Larvitz

2.

Probably best to illustrate how ifconfig handles netmasks too.

3.

Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.

#FreeBSD #procstat #fstat #iostat #ifconfig #netstat

@Larvitz

2.

Probably best to illustrate how ifconfig handles netmasks too.

3.

Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.

#FreeBSD #procstat #fstat #iostat #ifconfig #netstat

@Larvitz

2.

Probably best to illustrate how ifconfig handles netmasks too.

3.

Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.

#FreeBSD #procstat #fstat #iostat #ifconfig #netstat

@freezr

If you like the FreeBSD syntax, I have an ifconfig that is closer to FreeBSD syntax than the net-tools one is.

In fact, that was its raison d'être. It brought (most of) the FreeBSD syntax to Debian so that I could auto-translate /etc/network/interfaces into FreeBSD-like setup that used ifconfig.

http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml

http://jdebp.info/Softwares/nosh/guide/networking.html

#FreeBSD #ifconfig #nosh

2/2

🔴 "ipconfig" es la herramienta de configuración de red de Windows.

🔴 "ss -i" muestra info interna de comunicaciones TCP. Es el reemplazo de iproute2 para el "netstat" de net-tools.

🔴 "hostname" muestra y gestiona el nombre de host en GNU/Linux, y la opción "-I" no existe y produce un error.

Y ustedes, ¿todavía usan #ifconfig? 😜
Los invito a pasar por acá:

👇
https://juncotic.com/iproute2-ifconfig-hora-de-actualizarse/

Espero que hayamos aprendido algo más de #GNU #Linux hoy! ✨

Cualquier duda comenten! 💬

1/2

Vamos con el feedback de la encuesta!! Mil gracias a todos por participar!! 🤗

🟢 Solución: ip a

El comando #ip permite realizar casi todas las configuraciones de red en GNU/Linux.

"ip a" es la abreviatura de "ip addr", o "ip address", todos hacen lo mismo.

Es parte del paquete #iproute2, reemplazo de net-tools de #Unix, y remplaza a varias herramientas hoy consideradas obsoletas en Linux (creo que hace todo lo que antes hacíamos con #ifconfig, #route, #iptunnel, o #arp).

(sigue)

@dalias @starsider @atax1a @avuko

I think that specialized is the wrong way around, there. Usually it is the generalized tool, the one that can do every possible niche task (e.g. openssl even containing a WWW server) that is complex. Whereas the specialized tool (e.g. other SSL tools that do only SSL wrapping) is the simpler.

#ifconfig is the example that most people bring up, but the tale of #ps on Linux is also interesting as a different case study.

#GNU #Linux

Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig

Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig

Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig

Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig

Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig

As implied, the #NetBSD port of #nosh, #redo, and #djbwares is pretty much done.

NetBSD doesn't make it as easy to switch between process 1 programs as FreeBSD does, so the system manager is not tested. But many of the other tools from tai64nlocal, cyclog, and setterm; through login-envuidgid and envdir; to the service manager and console-tty37-viewer; have now been used in earnest.

There are known missing bits in #ifconfig and list-process-table. And UVT realizers are not tested at all yet.

#iproute2 6.14.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

#iproute2 6.14.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

#iproute2 6.14.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

@fooflington @nixCraft

l simply use BSD syntax ifconfig on Linux, as well.

http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml

#ifconfig #nosh

#iproute2 6.11.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

#iproute2 6.11.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

#iproute2 6.11.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2

@nixCraft I find the iproute2 syntax so much saner! I love it ❤️

Although I spent some years working with good old ifconfig I wouldn’t even consider using it today and writing this I realize I can’t remember its syntax anymore. And that’s a good thing for me.

#iproute2 #ifconfig #linux

Um jeito simples de descobrir o IP de externo(público) a partir do terminal:

curl ifconfig.me/ip

#linux #curl #ifconfig.me

#Powershell #ifconfig Descobrindo o IP publico da máquina pelo Powershell https://bit.ly/3ONv2KF via PlanetPowerShell

#Powershell #ifconfig Descobrindo o IP publico da máquina pelo Powershell https://bit.ly/3tJSX6B via PlanetPowerShell

lladdr-tied interface config support has been committed https://undeadly.org/cgi?action=article;sid=20221206062638 #openbsd #ifconfig #networking #macaddress #lladdr

It has to be said 🤣

#Techi #dev #linux #windows #ifconfig #ipconfig #iwconfig #ipa

Learn about alternative tools to deprecated #Linux commands https://www.fosslife.org/alternatives-deprecated-linux-commands #tools #CommandLine #security #commands #egrep #fgrep #nslookup #ifconfig #netstat #route #flags #ip