Sven GeggusBisher hatte ich unter #Debian #wpasupplicant im roaming config mit #ifupdown am laufen. Aus mehreren Gründen bin ich auf vielen kabelgebundenen Maschinen auf #system-networkd umgestiegen. Kriegt man das wpa-roam setup auch mit #system-networkd zum laufen?
Haack’s NetworkingJust dropped a new blog post, classic bridging with ifupdown. Hope some folks find it helpful or intriguing: https://tech.haacksnetworking.org/2025/11/27/classic-bridging-w-ifupdown/ If you have questions, hop over to Matrix https://matrix.to/#/@haacksnetworking:gnulinux.club and hit me up! #floss #freesoftware #opensource #debian #ifupdown #bridging #networking #virtualization
Kajo 📷 
#FediHelp
Ich versuche gerade folgendes Tutorial von @nobody via #VirtualBox, #Debian12 und Windows 10 einzurichten. (https://www.kuketz-forum.de/t/maximaler-datenschutz-windows-hinter-einem-proxy-betreiben/8428/1)
Die #ifupdown Konfiguration (siehe 3.1.2) wirft einen Fehler. Anbei ein Screenshot aus dem Tutorial (Config /etc/network/interfaces), meine Netzwerkinterfaces (ip addr), meine Config von /etc/network/interfaces, sowie der Fehlermeldung journalctl -xeu networking.service
Kann mir jemand helfen? 🙏
mirabilosHas anyone ever seen this behaviour: (sorry screenreader users for the amount of # in this, trying to get a broad coverage)
I have a #WLAN with a @mikrotik hAP Mini as access point and bridge into the LAN; DHCP server is the BSD box behind that in the LAN.
I was associated from a #Lenovo #Thinkpad #X61 #iwl4965 running #Debian #bullseye with sysvinit and #ifupdown.
Then someone on a #Tuxedo #InfinityBook #N13xWU #iwl8265/8275 with Debian #bookworm and systemd tried to connect, also with ifupdown. In that same moment, I saw this in my dmesg:
Apr 26 16:21:08 host wpa_supplicant[7322]: wlan0: CTRL-EVENT-BEACON-LOSS
Apr 26 16:21:12 host last message repeated 4 times
Apr 26 16:21:12 host vmunix: [9833573.801654] wlan0: deauthenticated from xx:xx:xx:xx:xx:xx (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Apr 26 16:21:12 host wpa_supplicant[7322]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=6
Apr 26 16:21:12 host wpa_supplicant[7322]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='myssidname' freq=2422 MHz)
Apr 26 16:21:12 host wpa_supplicant[7322]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Apr 26 16:21:12 host wpa_supplicant[7322]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE
Apr 26 16:21:15 host wpa_supplicant[7322]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='myssidname' freq=2422 MHz)
Apr 26 16:21:15 host vmunix: [9833576.586487] wlan0: authenticate with xx:xx:xx:xx:xx:xx
Apr 26 16:21:15 host vmunix: [9833576.591044] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Apr 26 16:21:15 host vmunix: [9833576.600286] wlan0: authenticated
Apr 26 16:21:15 host vmunix: [9833576.603383] iwl4965 0000:03:00.0 wlan0: disabling HT/VHT/HE as WMM/QoS is not supported by the AP
Apr 26 16:21:15 host wpa_supplicant[7322]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='myssidname' freq=2422 MHz)
Apr 26 16:21:15 host vmunix: [9833576.608113] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Apr 26 16:21:15 host vmunix: [9833576.716107] wlan0: associate with xx:xx:xx:xx:xx:xx (try 2/3)
Apr 26 16:21:15 host vmunix: [9833576.828160] wlan0: associate with xx:xx:xx:xx:xx:xx (try 3/3)
Apr 26 16:21:15 host vmunix: [9833576.940095] wlan0: association with xx:xx:xx:xx:xx:xx timed out
From that point on, I could not connect any more, even when the Tuxedo left the WLAN, until I toggled the rfkill switch in front of the device twice.
(About ten minutes before that, the Tuxedo was connected and I was not, and I could not connect either until I toggled rfswitch twice.)
Peeking into the syslog of the Tuxedo, whose time is roughly synchronised, I see that at about 16:21:09 they did an ifdown, not an ifup, which came a couple of seconds later‽
For added fun: apparently, systemd starts a global copy of wpa_supplicant but ifupdown rewrites its config and starts its own, so at that point, two were running…
More tags: #WiFi (for those who don’t use the term WLAN) #wpa #wpa_supplicant
JdeBPThe interesting part of that to me, that is unrelated to recent events, is how they *seem* to be reinventing ISC-licenced implementations of CRC32 in 2024. I am certain that such things have existed in the BSDs for decades.
There are probably fully (U.S.) public domain implementations of #CRC32 from the 1990s if one is willing to dig around in the world of old shareware. It was the sort of thing that got posted to magazines or passed around as code snippets in BBSes.
JunicastWhy is #Debian still using something archaic like the #ifupdown scripts. There are modern alternatives like #systemdnetworkd, #NetworkManager or #Netplan
I'd much rather want to see Debian using one of these instead as default.
I'd much rather want to see Debian using one of these instead as default.
Colin@ariadne Apologies for the unsolicited approach. A quick heads up - if you can bear to, please check out IRC channel #ifupdown-ng. GitHub issue 234 refers. ISTM these two could learn some patience and manners, but I’ve probably not helped the situation much by saying so.
Hugely appreciate everything you do.
Hugely appreciate everything you do.
Robert SanderTIL: After "apt install ifupdown2 && apt purge ifupdown" you need to "apt install --reinstall ifupdown2 && systemctl enable networking.service"
Otherwise your network will not start any more after the next boot.
❄️ freezr ❄️#Runit experts I need help! 
I am on #Devuan and I use #ifupdown to manage the interfaces, my issue is the ethernet cable is flaky and often gets disconnected by itself.
Since the system is headless if I re-plug the cable the eth0 interface went already down and I need monitor and keyboard to raise up the interface again.
I believe is properly setup:
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.0.10.3/24
netmask 255.255.255.0
gateway 10.0.10.254
How can I raise up the interface automatically?
Thanks!