New AirSnitch attack breaks Wi-Fi encryption in homes, offices, and enterprises
#HackerNews #AirSnitch #WiFi #Attack #WiFiSecurity #CyberThreats #EncryptionNews
Quixoticgeek
and 1 other
boosted
#Tumbleweed boots on #RaspberryPi 5!
Thanks to U-Boot, kernel updates, and the RP1 driver, core features like Ethernet, #WiFi, USB, and #HDMI are working. A major step forward for #openSUSE on #ARM. https://news.opensuse.org/2025/11/04/raspberrypi5-opensuse/
#Tumbleweed boots on #RaspberryPi 5!
Thanks to U-Boot, kernel updates, and the RP1 driver, core features like Ethernet, #WiFi, USB, and #HDMI are working. A major step forward for #openSUSE on #ARM. https://news.opensuse.org/2025/11/04/raspberrypi5-opensuse/
FreeBSD doesn't have Wi-Fi driver for my old MacBook. AI build one for me
Slow Wi-Fi? I found 10 proven ways to fix your internet this weekend (most are free) https://zdnet.com/home-and-office/networking/bad-wifi-10-fixes-for-better-internet/ via @ZDNet & @sjvn
How to speed up your home/small-office #WiFi.
Slow Wi-Fi? I found 10 proven ways to fix your internet this weekend (most are free) https://zdnet.com/home-and-office/networking/bad-wifi-10-fixes-for-better-internet/ via @ZDNet & @sjvn
How to speed up your home/small-office #WiFi.
Slow Wi-Fi? I found 10 proven ways to fix your internet this weekend (most are free) https://zdnet.com/home-and-office/networking/bad-wifi-10-fixes-for-better-internet/ via @ZDNet & @sjvn
How to speed up your home/small-office #WiFi.
Slow Wi-Fi? I found 10 proven ways to fix your internet this weekend (most are free) https://zdnet.com/home-and-office/networking/bad-wifi-10-fixes-for-better-internet/ via @ZDNet & @sjvn
How to speed up your home/small-office #WiFi.
The Weight of a Millimeter
A distracted driver, a motorcycle crash, and the terrifying wait to see if I would ever walk again.
https://my-notes.dragas.net/2026/02/02/the-weight-of-a-millimeter/
#MyNotes #Blogging #Life #Reflections #Memories #WiFi #Hacking
A distracted driver, a motorcycle crash, and the terrifying wait to see if I would ever walk again.
https://my-notes.dragas.net/2026/02/02/the-weight-of-a-millimeter/
#MyNotes #Blogging #Life #Reflections #Memories #WiFi #Hacking
Stefano Marinelli
boosted
So, after I met problems with iwlwifi driver and my attempts to aggregate both em0 and wlan0 interfaces to the one lagg0 interface (https://mastodon.bsd.cafe/@evgandr/115985853500057386) — looks like I found a much (MUCH!) simpler solution 
I wanted to automatically switch between wired and wireless networks when I plug-in (or disconnect) my Ethernet cable. First, because I was a newbie in the FreeBSD world, I tried to search for some kind of NetworkManager. Thankfully, I didn't find any NetworkManager clone ported to the FreeBSD. I found some tries to port NetworkManager from Linux to FreeBSD but all of them are failed (not surprised, lol).
Then, I finally started to read documentation 
. In the section about advanced networking I read about aggregation interfaces. And somehow I managed to aggregate both of em0 and wlan0 to the one lagg0 interface and it works well.
But, looks like (see https://mstdn.social/@erikarn/115986265106931691) it is not the way how the lagg interfaces should work. It is not intended to use wireless interfaces in the aggregate interfaces — so my tricky setup stopped working in the FreeBSD 15.0.
BUT, since we have a beautiful devd daemon, which listens for various system events and able to execute actions when event is happened — I just wrote 23 lines of shell script to learn my laptop how to switch between interfaces when the Ethernet cable (dis)connects, lol. Solution is very simple:
First, we already have /etc/devd/dhclient.conf, which starts dhclient when some interface appeared in the system. I modified it, so it calls the sPeCiAL script, each time when em0, or wlan0, or ue0 interface appeared in the system, or when em0 is disappeared:
notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifup";
};
notify 0 {
match "system" "IFNET";
match "type" "LINK_DOWN";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifdown";
};
notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "802.11";
action "/root/bin/unfuck_network.tcsh $subsystem";
};
notify 0 {
match "system" "ETHERNET";
match "type" "IFATTACH";
match "subsystem" "ue0";
action "/root/bin/unfuck_network.tcsh ue0";
};
Then, the main magic happens in the /root/bin/unfuck_network.tcsh:
— When Ethernet cable is connected — it destroys the wlan0 interface and starts dhclient for em0 to talk with DHCP server.
— When Ethernet cable is disconnected — it makes all to remove route using em0 from routing table (removes em0 interface completely, flush routing table, etc — somehow em0 still stays in the routing table if interface is not destroyed; btw system will create it anyway later, in some point) and recreates the wlan0 interface.
— When wlan0 device is created — it starts dhclient for it.
Script contents (for tcsh):
#!/bin/tcsh
switch ( $1 )
case "em0":
if ( $2 == "ifup" ) then
service netif quietstop wlan0
service dhclient quietstart em0
else if ( $2 == "ifdown" ) then
service dhclient quietstop em0
ifconfig em0 delete
route flush
service routing restart
service netif quietstart wlan0
endif
breaksw;
case "wlan0":
service dhclient quietstart wlan0
breaksw;
case "ue0":
service dhclient quietstart ue0
breaksw;
endsw
So, after I met problems with iwlwifi driver and my attempts to aggregate both em0 and wlan0 interfaces to the one lagg0 interface (https://mastodon.bsd.cafe/@evgandr/115985853500057386) — looks like I found a much (MUCH!) simpler solution
I wanted to automatically switch between wired and wireless networks when I plug-in (or disconnect) my Ethernet cable. First, because I was a newbie in the FreeBSD world, I tried to search for some kind of NetworkManager. Thankfully, I didn't find any NetworkManager clone ported to the FreeBSD. I found some tries to port NetworkManager from Linux to FreeBSD but all of them are failed (not surprised, lol).
Then, I finally started to read documentation . In the section about advanced networking I read about aggregation interfaces. And somehow I managed to aggregate both of em0 and wlan0 to the one lagg0 interface and it works well.
But, looks like (see https://mstdn.social/@erikarn/115986265106931691) it is not the way how the lagg interfaces should work. It is not intended to use wireless interfaces in the aggregate interfaces — so my tricky setup stopped working in the FreeBSD 15.0.
BUT, since we have a beautiful devd daemon, which listens for various system events and able to execute actions when event is happened — I just wrote 23 lines of shell script to learn my laptop how to switch between interfaces when the Ethernet cable (dis)connects, lol. Solution is very simple:
First, we already have /etc/devd/dhclient.conf, which starts dhclient when some interface appeared in the system. I modified it, so it calls the sPeCiAL script, each time when em0, or wlan0, or ue0 interface appeared in the system, or when em0 is disappeared:
notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifup";
};
notify 0 {
match "system" "IFNET";
match "type" "LINK_DOWN";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifdown";
};
notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "802.11";
action "/root/bin/unfuck_network.tcsh $subsystem";
};
notify 0 {
match "system" "ETHERNET";
match "type" "IFATTACH";
match "subsystem" "ue0";
action "/root/bin/unfuck_network.tcsh ue0";
};
Then, the main magic happens in the /root/bin/unfuck_network.tcsh:
— When Ethernet cable is connected — it destroys the wlan0 interface and starts dhclient for em0 to talk with DHCP server.
— When Ethernet cable is disconnected — it makes all to remove route using em0 from routing table (removes em0 interface completely, flush routing table, etc — somehow em0 still stays in the routing table if interface is not destroyed; btw system will create it anyway later, in some point) and recreates the wlan0 interface.
— When wlan0 device is created — it starts dhclient for it.
Script contents (for tcsh):
#!/bin/tcsh
switch ( $1 )
case "em0":
if ( $2 == "ifup" ) then
service netif quietstop wlan0
service dhclient quietstart em0
else if ( $2 == "ifdown" ) then
service dhclient quietstop em0
ifconfig em0 delete
route flush
service routing restart
service netif quietstart wlan0
endif
breaksw;
case "wlan0":
service dhclient quietstart wlan0
breaksw;
case "ue0":
service dhclient quietstart ue0
breaksw;
endsw
The Weight of a Millimeter
A distracted driver, a motorcycle crash, and the terrifying wait to see if I would ever walk again.
https://my-notes.dragas.net/2026/02/02/the-weight-of-a-millimeter/
#MyNotes #Blogging #Life #Reflections #Memories #Blogging #WiFi #Hacking
So it seems that one of my wifi access points on my home network has died.
Can't say it owes me much, it's about 9 years old.
What's a good brand for wifi access points these days? My old one was TP Link, which gave me 9 years of trouble-free wifi, so I would be fine with getting another one, but I'm open to other suggestions.
Briar keeps Iran connected via Bluetooth and Wi-Fi when the internet goes dark
https://briarproject.org/manual/fa/
#HackerNews #Briar #Iran #Bluetooth #WiFi #Connectivity #InternetAccess
Two new Xfinity techs are here. They took a look at the wording behind the coaxial wall plate; It was ancient and apparently there was an incredible amount of signal noise. They replaced it.
But it's still a mystery as to why rebooting the router fixed the problem about 70% of the time. So we're going to have to wait and see what happens. If it starts crashing again, it may be that the router is being interfered with by electrical noise that's not on the coax, but on the power supply. But it's plugged into a UPS, so that shouldn't be the problem.
It's also possible that one of the four devices connected to the router by Ethernet could be kicking back somehow, but again that's going to take monitoring to figure out.
Right now we're hoping that the problem is solved. They gave us two new CAT 6 cables to connect the modem to the router and the router to my desktop.
And while he was down there, Sebastian discovered several unused USB ports in the back of my computer. Don't know how I missed those before! That makes eight ports total. So now I can hook up several more SSD drives.
Here's hoping this is the end of the matter!
Cress 🏴 🌻
boosted
People who know about internets - my WiFi is still dropping (about every 15 mins on video calls for a few seconds regardless of platform).
We have a repeater thingy now that actually works so I have full strength in my room, so it's not that anymore. And the problem has changed/improved.
Do I need to upgrade the WiFi to more faster better stronger?
What is the problem?
Why does it hate me?
We're with Zen full fibre 100.
Speed test: https://www.speedtest.net/result/18705967157
People who know about internets - my WiFi is still dropping (about every 15 mins on video calls for a few seconds regardless of platform).
We have a repeater thingy now that actually works so I have full strength in my room, so it's not that anymore. And the problem has changed/improved.
Do I need to upgrade the WiFi to more faster better stronger?
What is the problem?
Why does it hate me?
We're with Zen full fibre 100.
Speed test: https://www.speedtest.net/result/18705967157
Dane 🇮🇪🇺🇦🇻🇪🖖⚛️☮️☸️🕉️
boosted
Asking the Fediverse Hive Mind About WiFi routers:
I'm moving to a home where fibre high speed internet is available.
In order to avoid the monthly fee for the service provider's router, I'd like to provide my own.
Are there brands or models you kind folks would recommend?
I'm looking for something offering a good product at a reasonable price. (WiFi 7 seems worth getting.)
Dependable would also be nice.
Thanks to those who would be kind enough to boost.
#FediverseHiveMind #FediTechSupport #FediAnswers #WiFi
I built a quantum internet that runs on your WiFi
https://github.com/mermaidnicheboutique-code/luxbin-quantum-internet
#HackerNews #quantuminternet #WiFi #technology #innovation #hackernews #coding #quantumcomputing