Creative Constant Development Workgroup

When you have a wire-connected computer with a unused wireless interface, an option is to use the device as an access point to improve the coverage of your WIFI network. This can be done by setting up hostapd, which takes care of wireless interface configuration, authentication and security. However, in order for the wireless traffic to actually go through the wired connection and onto the internet and vice versa, the two interfaces needed to be bridged somehow. There are several scenario for configuring the bridge connection.

For the text-based email client alpine to remember your passwords for email servers, it is required to create a master password to encrypt the .pine-passfile. Sometimes, this is undesirable and there is no official way to disable this requirement.

The home automation system OpenHAB has the ability to coordinate difference networked devices to perform automatic control under different conditions. One of the important conditions is the presence of different residents in the house. Using "Network Health" module of OpenHAB allows the presence test through the detection of devices carried by the residents. One simply create item such as

The NodeMCU v2 firmware for esp8266 only allows one TCP server. Usually, one will use this to serve a status page for the wireless unit. But, sometimes, maybe during development, it is desirable to also have a telnet access to the unit over WIFI to do some tweaking. Here, we achieve this by leaving a backdoor on the http port. By connecting to port 80 with telnet and enter "telnet" as the first input line, the connection is switch to a telnet service allows direct interaction with the Lua interpreter. The actual code is listed below:

esptool.py is your friend. Simply do:

./esptool.py --port /dev/ttyUSB0 write_flash 0x00000 ~/Downloads/nodemcu_float_0.9.6-dev_20150704.bin 

This works for my esp-01 module. However for the NodeMCU v2 module that I have, more options need to be add to the command line:

It seemed that the proto 41 for ipv6 traffic is not forwarded to the DMZ by TP-Link 150Mbps Wireless N Router TL-WR720N. This put out the hope of setting up 6to4 in my apartment. There is a slight chance that the filtering was done by the ISP. However, I had no suitable option to test this.
As it seems, the same is true for TL-WR702N.