5Ghz WiFi and Windows 10

/dev/null1 Comment

I have been having issues with devices maintaining connections to my 5Ghz SSID on multiple devices. After the latest Android update, it seems my phone is able to maintain reliable 5Ghz connections but my Windows 10 laptop was still having issues. After some searching I decided to update the driver and see if it made a difference. Its still too early tell for sure, but it seems the new driver is doing better. The AP in question is a Synology RT2600ac with SmartConnect disabled, running 2 separate SSIDs for 2.4Ghz and 5Ghz. Support has been of absolutely no use. They repeatedly stated they didn’t see any disconnects in the logfile dumps.

Normally I would only stay connected, if I could connect at all, for a few minutes.

System Manufacturer:LENOVO
System Product Name:20L50017US
BIOS Date:05/22/2018
BIOS Version:N24ET39W (1.14 )
OS Build:17763.1.amd64fre.rs5_release.180914-1434

The driver version I was having an issue with:
Device: Intel(R) Dual Band Wireless-AC 8265
Current driver version: 20.70.11.3
Driver date: 6-29-2019

The latest version in testing:
Device: Intel(R) Dual Band Wireless-AC 8265
Current driver version: 20.70.12.5
Driver date: 8-26-2019

I ran “netsh wlan show wlanreport” to get some insight on what was going on.
BOLD items below are 5Ghz specific errors and warnings. The 2.4Ghz SSID has been working without issue.

Session Success/Failures
Status Count
Successes 2
Failures 10
Warnings 16

Disconnect Reasons
Reason Count
The driver disconnected while associating. 8
The network is disconnected by the driver. 7
The network is disconnected because the user wants to establish a new connection. 4
The network is disconnected by the user. 2

The error I was repeatedly getting while trying to connect to the 5Ghz SSID is:
Failure Reason:The driver disconnected while associating.

The red Xs in the image below are all dropped connections to 5Ghz.

Hits: 181

Fucking w/ TinyDNS

/dev/nullLeave a comment

Getting the serial number/change date for a domain on an authoritative server.

nameserver:/root # tinydns-get soa domain.com
6 domain.com:
193 bytes, 1+1+3+3 records, response, authoritative, noerror
query: 6 domain.com
answer: domain.com 60 SOA ns1.domain.com domain.com 2012043001 10800 3600 604800 3600
authority: domain.com 60 NS ns1.domain.com
authority: domain.com 60 NS ns2.domain.com
authority: domain.com 60 NS ns3.domain.com
<SNIP>

Hits: 60

TS3 Server Create New Token

/dev/nullLeave a comment
  1. Start any telnet client – you can use e.g. PuTTy
  2. Connect to your Teamspeak 3 server IP using Telnet on port 10011
  3. Login using command login serveradmin yOuR_nEwP@ssw0rdpassword in command is the same as the one you set for your serveradmin previously
    1. Select your Teamspeak server instance (if you have only one just this would be your default: use 1 and hit enter
    2. Now it’s time to generate new privilege key, for that use following command:tokenadd tokentype=0 tokenid1=6 tokenid2=0
  4. That will return you token, which you can copy and paste in Teamspeak 3 client under Permissions > Use Privilege Key

Hits: 62

Syslog: Log Levels

/dev/null

0 -> emerg —-> System is unusable.
1 -> alert ——> Should be corrected immediately.
2 -> crit ——–> Failure in the system’s primary application.
3 -> err ———> An application has exceeded storage.
4 -> warning -> An error will occur if action is not taken.
5 -> notice —–> Events that are unusual.
6 -> info ——–> Normal operational messages.
7 -> debug —–> Debug level logging.

Hits: 529