Since software release v126.96.36.1994, WiFi setup should be relatively easy for most common WiFi scenarios.
The one notable exception are captive portals. Captive portal WiFi are commonly seen in trains and coaches, stations, hotels, airports, or large chain cafés. They are WiFi networks that require no password to connect to, but require a web browser to connect to the broader Internet.
Press RM and go to WI-FI: Select SSID
/etc/wpa_supplicant/. I used
deutsche-telekom-root-ca-2.crtin the sample configuration), make sure to upload them as well
/email@example.com) with e.g. vi and extend the ExecStart line with
systemctl restart firstname.lastname@example.org
Caveat: The configuration changes may be lost when the reMarkable updates!
Credit goes to jfreax on reddit/r/RemarkableTablet
To debug connection issues do the following:
systemctl stop email@example.com
wpa_supplicant -C/var/run/wpa_supplicant -c/etc/wpa_supplicant/eduroam.conf -iwlan0
you should see output similar to this:
Successfully initialized wpa_supplicant wlan0: Trying to associate with SSID 'eduroam' wlan0: Associated with 48:ff:36:e5:d1:98 wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=NL/ST=Noord-Holland/L=Amsterdam/O=TERENA/CN=TERENA SSL CA 3' hash=be4dd8c5d8 wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=BE/ST=Oost-Vlaanderen/L=Gent/O=Universiteit Gent/OU=DICT/CN=ugnps.ugent.be' hash=9c442326c372fcd43 wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:ugnps.ugent.be wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:ugnps1.ugent.be EAP-MSCHAPV2: Authentication succeeded EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully wlan0: WPA: Key negotiation completed with 48:ff:36:e5:d1:98 [PTK=CCMP GTK=CCMP] wlan0: CTRL-EVENT-CONNECTED - Connection to 48:ff:36:e5:d1:98 completed [id=0 id_str=] Cwlan0: CTRL-EVENT-DISCONNECTED bssid=48:ff:36:e5:d1:98 reason=3 locally_generated=1 nl80211: deinit ifname=wlan0 disabled_11b_rates=0
The key idea is to establish a SOCKS proxy in your reMarkable, then try to browse the web through this proxy from another device. This will redirect you to the captive portal page, which you can fill out as usual.
-D <port>ssh flag, like so
ssh -D 1337 firstname.lastname@example.org
For Windows PuTTY users, configure ssh port forwarding by going to Connection–>SSH–>Tunnels on the PuTTY Configuration Menu. Once there, add a new forwarded port by making Source code
and select Manual Proxy Configuration. The SOCKS host should be
and the port
Make sure SOCKS v5 is checked too. After you are done with this guide, remember to revert the settings to their original values, or else FireFox will continue to attempt to connect through the proxy. (You can use any browser, just look up how to.)
The Remarkable on-screen keyboard only supports a limited number of characters. If you want to connect to a WiFi network with such a password, you can manually edit
/home/root/.config/remarkable/xochitl.conf via SSH to add your WiFi network configuration. The WiFi configuration part looks something like this:
The value part is encoded by
QSettings from QT5 and contains the WiFi network
ssid (network name),
protocol (not sure which values are supported, at least
psk). https://github.com/pascalw/remarkable-wifi-conf can be used to encode your network settings in the right format.
/lib/systemd/system/wpa_supplicant@.serviceinstead seems to work too