diff options
| author | Dante Catalfamo | 2021-10-12 22:32:42 -0400 |
|---|---|---|
| committer | Dante Catalfamo | 2021-10-12 22:32:42 -0400 |
| commit | 2331661b4282457e9e6a657dfb010239a36589a1 (patch) | |
| tree | 9f462aa597bc0179680f44e2721d418438e5ffdb | |
| parent | 269390e7eea36619843edb96ddf8d491741e7f6d (diff) | |
| download | blog-2331661b4282457e9e6a657dfb010239a36589a1.tar.gz blog-2331661b4282457e9e6a657dfb010239a36589a1.tar.bz2 blog-2331661b4282457e9e6a657dfb010239a36589a1.zip | |
xprinter-wifi: make corrections
| -rw-r--r-- | content/posts/WIP-xprinter-wifi/index.org | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/content/posts/WIP-xprinter-wifi/index.org b/content/posts/WIP-xprinter-wifi/index.org index a566239..8bba537 100644 --- a/content/posts/WIP-xprinter-wifi/index.org +++ b/content/posts/WIP-xprinter-wifi/index.org @@ -22,7 +22,7 @@ anywhere, and I suspect are device-specific. Since booting into Windows every time I want to manage the printer's network settings isn't ideal, I decided to reverse engineer the -WiFi configuration protocol. +WiFi configuration commands. Initially I tried to run the configuration tool in wine, but it couldn't communicate with the printer over USB, which wasn't too @@ -64,7 +64,7 @@ and the printer's socket using Wireshark. [[file:xprinter_wireshark.png]] -In the examples below I've encoded the decimal numbers to hex to make +In the examples below I've encoded the data being sent to hex to make it easier to understand the contents of the packets. Based on the traffic, I was able to come up with the following. @@ -82,7 +82,7 @@ Based on the traffic, I was able to come up with the following. #+RESULTS: | c0 | a8 | 00 | 07 | - Packate contents from wireshark: + Packet contents from wireshark: =0000 1f 1b 1f 22 c0 a8 00 07= @@ -107,7 +107,7 @@ Based on the traffic, I was able to come up with the following. #+RESULTS: | ff | ff | ff | 00 | - Packate contents from wireshark: + Packet contents from wireshark: =0000 1f 1b 1f b0 ff ff ff 00= @@ -132,7 +132,7 @@ Based on the traffic, I was able to come up with the following. #+RESULTS: | c0 | a8 | 00 | 01 | - Packate contents from wireshark: + Packet contents from wireshark: =0000 1f 1b 1f b1 c0 a8 00 01= @@ -151,7 +151,7 @@ Based on the traffic, I was able to come up with the following. - Subnet mask =255.255.255.0= - Gateway =192.168.0.1= - Packate contents from wireshark: + Packet contents from wireshark: =0000 1f 1b 1f b2 c0 a8 00 07 ff ff ff 00 c0 a8 00 01= @@ -188,7 +188,7 @@ Based on the traffic, I was able to come up with the following. #+RESULTS: | 50 | 41 | 53 | 53 | 57 | 4f | 52 | 44 | 5f | 48 | 45 | 52 | 45 | - Packate contents from wireshark (including string representation): + Packet contents from wireshark (including string representation): #+begin_src 0000 1f 1b 1f b3 06 53 53 49 44 5f 48 45 52 45 00 50 .....SSID_HERE.P 0010 41 53 53 57 4f 52 44 5f 48 45 52 45 00 ASSWORD_HERE. @@ -232,7 +232,7 @@ Based on the traffic, I was able to come up with the following. - Key =PASSWORD_HERE= - Key Type =WPA2_AES_PSK= - Packate contents from wireshark (including string representation): + Packet contents from wireshark (including string representation): #+begin_src 0000 1f 1b 1f b4 c0 a8 00 07 ff ff ff 00 c0 a8 00 01 ................ |