The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,861 other subscribers

Archive for the ‘WiFi’ Category

Ubiquity UniFi SDN – Server status “UniFi Controller is starting up… Please wait a moment”

Posted by jpluimers on 2019/02/22

When your UniFi Cloud Key web interface shows this [Archive.is] after upgrading:

 

UniFi Controller is starting up…

Please wait a moment

 

Then you just ran into a bug which seems to occur most with 5.9.29 of the UniFi software: [Archive.is] “UniFi Controller is starting up…” “Please wait a moment” “5.9.29” – Google Search

The easiest way is to restore from a backup: this usually works.

For that you need ssh access, which usually is with the ubnt user. But you could have made life more complicated when you followed these:

Steps from [WayBack] UniFi Controller is starting up… Please Wait A Moment – Ubiquiti Networks Community (thanks [Archive.is] About mrfoxdk – Ubiquiti Networks Community!):

  1. SSH to the Unifi CloudKey
  2. dpkg -P unifi
  3. Open a browser and browse the URL of CloudKey
  4. Login
  5. Press “Install” under UniFi
  6. Wait for the process to complete, and then wait a bit for the service to be brought online.
  7. Recover the configuration backup from the latest backup

Removing and reinstalling the UniFi software, then restore from backup

Step 2 above will purge the unifi software of the cloud key as per dpkg --help:

Read the rest of this entry »

Posted in *nix, Power User, Ubiquiti, WiFi | Leave a Comment »

Linus Torvalds – Google+: Working gadgets: Ubiquiti UniFi collection (and a whole bunch of Unifi/Ubiquiti/Ubtn links).

Posted by jpluimers on 2019/01/21

Seems my interest in Ubiquiti needs more research: [WayBackLinus Torvalds – Google+: Working gadgets: Ubiquiti UniFi collection.

Hopefully by now I’ve time to re-design the WiFi coverage in the house and invest in a few of those access points.

Related:

Splitting 5Ghz and 2.4Ghz SSIDs: two ways (I think the second is cleaner)

  1. Either have one WLAN group with a set of SSIDs, then in each access point disable the 2.4Ghz SSID on the 5GHz radio, and disable the 5Ghz SSID on the 2.4Ghz radio
  2. Have different WLAN groups with an SSID (or set of SSIDs) for each frequency, then in each access point select the appropriate group for each radio

For both the first and second one, you need to configure under “Config” -> “WLANs”.

For the second one, you can clone from the first, then change the SSID names.

–jeroen

Read the rest of this entry »

Posted in Power User, Ubiquiti, WiFi | Leave a Comment »

Strange MAC addresses starting FA:8F:CA without OUI in your network? They are Locally Administered Addresses and likely from Google.

Posted by jpluimers on 2019/01/07

A while ago, I write about Locally Administered Addresses: a few series of MAC addresses you can use on your local network: MAC address ranges safe for testing purposes (Locally Administered Address).

A while ago, I found ones in my network and ones in my WiFi SSID survey starting with FA:8F:CA. They did not show up in the Wireshark · OUI Lookup Tool nor their manufacturer database.

But with bit 7 turned off they start with F8:8F:CA which does show up as “F8:8F:CA Google, Inc.”

They appear to be Google devices, in my case Google ChromeCast ones, though they can also be Google Home ones.

Google does “magic” with networks, just look at a few of the links here:

–jeroen

Posted in Ethernet, Google, Internet, Network-and-equipment, Power User, Ubiquiti, WiFi | Leave a Comment »

No more https://www.whatsapp.com/cidr.txt

Posted by jpluimers on 2018/12/11

Not sure when this happened but the CIDR list is no more [WayBackhttps://www.whatsapp.com/cidr.txt:

Dear partners,
Please note that we have migrated the latest IP pools of WhatsApp to Facebook Mobile Partner Portal. Feel free to browse to the Settings page of the portal and download the latest WhatsApp IP pool: https://fb.me/mpp_support 
Further IP pool updates are also done through the portal and are no longer distributed via email or through WhatsApp web site.
If you have not yet registered on the Mobile Partner Portal or have difficulties accessing it - please request access through the following form and we'll be happy to assist: https://fb.me/mpp_access
For any technical requests please contact us through the Support section of the portal: https://fb.me/mpp_support 
WhatsApp team

In the past it was the place to get the CIDR so you could either block or allow WhatsApp traffic: [earlier WayBack]

It is still widely cited as way to regulate WhatsApp traffic, for instance at these places:

Time to find an automated way to get the replacement list. Maybe the below helps (via [WayBackBlock facebook messenger and whatsApp on Dlink router – Super User)

whois -h whois.radb.net '!gAS32934'

–jeroen

Posted in Android Devices, Development, Internet, Network-and-equipment, Power User, routers, SocialMedia, Software Development, Ubiquiti, WhatsApp, WhatsApp for Android, WiFi | Leave a Comment »

Potential wifi drop problem caused by Google devices – Google Product Forums

Posted by jpluimers on 2018/01/15

Sometimes the same problem here on an Asus RT-N66U: Potential wifi drop problem caused by Google devices – Google Product Forums [Archive.is].

Related:

Via [WayBack] Google Cast-apparaten veroorzaken wifi-drop-outs bij verschillende routers – Computer – Nieuws – Tweakers

–jeroen

 

Posted in Power User, WiFi | Leave a Comment »

Kristian Köhntopp – Google+

Posted by jpluimers on 2017/10/18

[WayBack] Kristian Köhntopp – Google+:

The S in IoT is for Security, and the U is for Update Policy.
 –jeroen

 

Posted in Development, Fun, Power User, Quotes, Software Development, WiFi | Leave a Comment »

RSA keys by Infineon chips or libraries can be cracked fast; Severe flaw in WPA2 protocol leaves Wi-Fi traffic open to eavesdropping…

Posted by jpluimers on 2017/10/16

All of our house is wired by ethernet for a reason…

WPA2 Flawed. Once again, it turns out that designing something properly secure is really, really, REALLY hard.

[WayBack] Severe flaw in WPA2 protocol leaves Wi-Fi traffic open to eavesdropping https://arstechnica.com/… – Lars Fosdal – Google+

[Archive.is] If fixes exist, third party firmware will have it in days. Most OEMs, never. I do worry a lot about unfixable flaws in the wifi standards… – Kristian Köhntopp – Google+:

Dave reminds us that there is a reason why people mod the firmware of their Wifi routers, and that reason is actually now more critical than ever.

Via [WayBack] https://www.krackattacks.com/ has a FAQ. Some interesting questions from there:… – Kristian Köhntopp – Google+:

[WayBackKRACK Attacks: Breaking WPA2 : This website presents the Key Reinstallation Attack (KRACK). It breaks the WPA2 protocol by forcing nonce reuse in encryption algorithms used by Wi-Fi.

 

Since we’re talking security, watch your RSA as it is way worse than the WPA2 one: [Archive.is]

We heard you liked the 10 WPA2 CVE’s, so »A 2nd major crypto vulnerability being disclosed… – Kristian Köhntopp – Google+ quoting

[WayBack] Dan Goodin‏ @dangoodin001: 2nd major crypto vulnerability being disclosed Monday involves millions of 1024- and 2048-bit RSA keys that are practically factorizable.

[WayBackROCA: Vulnerable RSA generation (CVE-2017-15361) [CRoCS wiki]

The time complexity and cost for the selected key lengths (Intel E5-2650 v3@3GHz Q2/2014):

  • 512 bit RSA keys – 2 CPU hours (the cost of $0.06);
  • 1024 bit RSA keys – 97 CPU days (the cost of $40-$80);
  • 2048 bit RSA keys – 140.8 CPU years, (the cost of $20,000 – $40,000).

[WayBack] New vulnerabilities found in RSA 1024 and 2048 bit keys. Estimated cost of cracking based on access to the Public key only: 1024 bit: $40 2048 bit: $20k… – Lars Fosdal – Google+

Jan Wildeboer did a nice explanation in laymen terms of both security issues published today:

 

–jeroen

Read the rest of this entry »

Posted in LifeHacker, Power User, Security, WiFi | Leave a Comment »

Amsterdam, 2.4 GHz. 5 GHz is only marginally better. In the city, wired connection is the only option: fiber, cable, dsl.

Posted by jpluimers on 2017/08/25

For me, too often – even at home – mobile internet is faster than WiFi over 2.4 Ghz and sometimes even faster than WiFi at 5 Ghz..

Further below is inside my home. I’ve no idea what these – relatively strong – networks are:

  • SANDS Wi-Fi Network (it has a MAC in the OUI list of Apple and is configured as GB device)
  • venus-HQ17128EGKE-5ae (it has a MAC in the local private range)
  • H368N8D6382 (and a network HZN242961585 that looks similar but is very different – the first has a MAC from ZTE corporation, the last from Samsung Electronics)

From Kristian Köhntopp near work in the city centre:

At my home:

A Google+ profile for Jeroen Wiert Pluimers

Source: at home… +Kristian Köhntopp

–jeroen

Via:

 

 

Posted in Power User, WiFi | Leave a Comment »

Multiple wifi access points / seamless handoff – Spiceworks

Posted by jpluimers on 2017/01/27

These seem to be the brands to look into:

  • Ubiquiti
  • Meraki
  • Ruckus

Source: Multiple wifi access points / seamless handoff – Spiceworks

–jeroen

Posted in Internet, Power User, Ubiquiti, WiFi | Leave a Comment »

Wifi Analyzer – helped me analyse why an original Chromecast failed to see a Buffalo WLAE-AG300N

Posted by jpluimers on 2017/01/06

Brilliant! Helped me to track down why an original 1st generation Chromecast didn’t want to connect to a Buffalo WLAE-AG300N.

The problem there is that the original Chromecast does only 2.4Ghz WiFi and the WLAE-AG300N favours 5Ghz WiFi over 2.4Ghz when set to auto.

The solution is in the last picture: basically force the WLAE-AG300N to use 11n/g/b only which limits it to 2.4Ghz (it cannot use both frequencies at the same time).

Yes, I know the Microwaves drawback, but as the original Chromecast only does 2.4Ghz. I’d rather get the Chromecast Ethernet adapter but Google refuses to ship these outside the USA.

Source: Wifi Analyzer – Android Apps on Google Play

 

Force the WLAE-AG300N to use only 2.4Ghz

Force the WLAE-AG300N to use only 2.4Ghz

Posted in Chromecast, Google, Power User, WiFi | Leave a Comment »