Blog Inforeseau.com – GNU Linux, technologie et autres geekeries

Install your VPN server with pi-hole on OVH VPS in 30 min

Prereqs : You must have an SSH client (native Linux SSH command, or putty on windows… poor you), you must know how to edit a file in command line (using vim or nano, as you like), you must know how to use terminal menu (tab to switch options, space to select, enter to validate)
Port : This tutorial expect to run Openvpn on port 443 (SSL port), if you want to use another one, just replace 443 by the port you wish in the whole tutorial below.

Note : This is done using an OVH VPS, with Debian 9, other cloud VPS might differ if not default debian 9.

Note2 : This will allow all devices on VPN to communicate with each other (client to client options enabled by default, and firewall rules allows this as well) – If you want to block client to client communication, check this pagehttp://blog.inforeseau.com/openvpn-and-pihole-on-ovh-vps-server-faq

Order OVH VPS with latest Debian (VPS SSD, cheapest at CAD $4.49/month ! )
SSH to it. (credentials for SSH root in the email you receive after OS installation)

Update and Install tools we want (editors, firewall, auto updates) :

apt-get update
apt upgrade
apt install aptitude iptables-persistent vim curl unattended-upgrades
 

It should look like this :

(YES to save current IPv4 rules and YES to save current IPv6 fules when install iptables)

Replace /etc/resolv.conf file content with the following

#Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 9.9.9.9

Configure iptables

We add the following content in /etc/iptables/rules.v4 (replace all the content using vim or another tool or remotely with filezilla)

#Generated by ourselves for pivpn and pi-hole
 *filter
 :INPUT ACCEPT [663907:41179802]
 :FORWARD ACCEPT [57036644:76048011107]
 :OUTPUT ACCEPT [5009068:528571183]
 -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
#Don t change the port 443 in the 3 lines below, this is for pihole performance
 -A INPUT -i tun0 -p tcp -m tcp --dport 443 -j REJECT --reject-with tcp-reset
 -A INPUT -i tun0 -p udp -m udp --dport 80 -j REJECT --reject-with icmp-port-unreachable
 -A INPUT -i tun0 -p udp -m udp --dport 443 -j REJECT --reject-with icmp-port-unreachable
#End of don t change these
#Port allowed for VPN, change if you decide to use another port for your VPN server (replace 443 below by whatever you chose)
 -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
 -A INPUT -p udp -m udp --dport 443 -j ACCEPT
#End of port to change if you get your VPN server to run on another port
 -A INPUT -i lo -p udp -m udp --dport 53 -j ACCEPT
 -A INPUT -i lo -p tcp -m tcp --dport 53 -j ACCEPT
 -A INPUT -i tun0 -p udp -m udp --dport 53 -j ACCEPT
 -A INPUT -i tun0 -p tcp -m tcp --dport 53 -j ACCEPT
 -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
 -A INPUT -p icmp -j ACCEPT
 -A INPUT -j DROP
 COMMIT
 #Completed on Sat Apr 27 16:18:39 2019
 #Generated by iptables-save v1.6.0 on Sat Apr 27 16:18:39 2019
 *nat
 :PREROUTING ACCEPT [496992:46323248]
 :INPUT ACCEPT [335723:24234770]
 :OUTPUT ACCEPT [486171:32444728]
 :POSTROUTING ACCEPT [491702:32816107]
 #if you need to use 1 or more other port(s), just add as many line as below, whitout the # so it is actually loaded, ens3 is the NIC of the VPS, adjust if yours differ
 #Below will allow to connect to port 8080 aside of 443. 
 #- A PREROUTING -i ens3 -p udp -m udp --dport 8080 -j REDIRECT --to-port 443
 COMMIT
 #Completed certainly after 2019 Apr 27t

Load the new rules as follow :

 iptables-restore < /etc/iptables/rules.v4

Install pi-vpn
adduser vpn (set a password of your choice)

 curl -L https://install.pivpn.io | bash

(if you have a name resolution issue, type the command again until it moves on)

The installer will transform your Raspberry Pi into an openvpn server (will do for your debian VPS too 😛 ) OK

the PiVPN need a static address, fine we are on VPS with assigned IP, OK

Since we think you are not using raspbian… correct, fine, OK

Choose user OK, select « vpn » that we just created and OK

It is recommended that you enable « unattended upgrade », OK, we already did this at the beginning

Do you want to enable unattended upgrades of security : NO (it is already done, no need to redo)

We want to use UDP protocol, Select UDP and OK

We modify the port to 443 as this will most likely will be allowed on most networks and OK

Are these settings correct : YES

YES to the next screen about Elliptic curves for key exchanges

Next, i’d recommend at least 384-bit encryption, safer, not crazy overhead. OK

Client can use the public IP, OK, this is totally fine as VPS has static IP (DNS is more useful in case of dynamic DNS use) – It should be the IP of YOUR VPS

Select DNS provider, this is a key point, we want the benefit of pi-hole on our VPN, so we’ll go down the list, and select « Custom » (go down with arrows on keyboard to select custom), then OK

Fill the info with 10.8.0.1 and OK (this will be the IP of the openvpn server on tap0 that we allowed in firewall)

Are these settings ok ? YES

validate the end of installation OK

reboot the VPS – YES and confirm OK

After reboot, SSH again on it

We’ll generate a client certifacte
as root :
pivpn -a
provide a client name (like device name such as myphone1) and a password.
As shown, the client ovpn file will be placed in /home/vpn/ovpns/ (since we use the user « vpn » to handle VPN).

Copy this file using filezilla via SFTP(SSH) or cat on ovpn (cat /home/vpn/ovpns/user-you-chose.ovpn) and copy the content to a local ovpn file.

Open this file with openvpn application on your phone and connect 😀
If on linux,

openvpn --config user-you-chose.ovpn

and it will connect.
You should be connected after providing the chosen password used when creating VPN user, and surf internet (when pi-hole below is installed too 😛 ) from your VPS with pi-hole filtering enabled !
go to http://monip.org to check the IP seen by websites (it should be the IP of your VPS).

Create as many users as you want ! Yes it’s free !
To delete a user : pivpn -r user
To see more options : pivpn

Done on VPN, but now we miss the pi-hole DNS filtering service, here we go (otherwise DNS resolution and filtering won’t work)

Install pi-hole, use the following command :

 curl -sSL https://install.pi-hole.net | bash

(will install needed packages)

Enter on OK to start.

Enter on OK to pass donation page (donate if you want to support pihole project, it is amazing)

Select interface TUN0 (DNS server must listen on VPN interface)
We have a static IP, ok

Pick the DNS server you want above pihole (i pick Quad9, but anything is good as you like) and press ok

Pi-hole third party list, select all and press OK

Select Protocols, leave both IPv4 and IPv6 checked, OK

Do you want to use your current network settings, YES ! ( This should show the IP of YOUR VPS)

IP Conflict, OK…fine fine move on 😛

Do you wish to install the web admin interface : OFF and OK (we don’t need it, we won’t connect to it, won’t open it)

Do you wish to install the web server (lighttpd) ? OFF and OK (not needed)

Do you want to log queries : OFF (no we don’t want to leave tracks…)

Select a privacy mode on FTP : 4 Disabled statistics (we are all about privacy here)

Firewall Detected, Install Pi-hole default firewall rules? NO, they are already in the iptables rules we copied

Configure your devices to use the pi-hole…. OK, we’ll do this in VPN config after.

We then want pi-hole to update its blacklist automatically everyday.
Create the file /etc/cron.daily/piholeupdate with the following content :

#!/bin/bash
/usr/local/bin/pihole -g

Save and make it executable :

chmod +x /etc/cron.daily/piholeupdate

Done for pihole.

Enjoy !

Use the command « pivpn » to generate as many users as devices you have, install openvpn client on it (android, iOS, linux or windows or tunnelblick on MAC), and import the .ovpn file that you generated using the password you entered when creating user.

If one of your device is stolen or lost, revoke the certificate.

You can now browse internet, seen as your VPS, and no one can snoop on your traffic, without adds, without tracking 😛 (still take a canvas randomizer plugin for your browser to avoid device signature).

Security note : By default the OVH VPS is installed with a ROOT account and a password provided to you. Online servers are under attack on a permanent basis.
I recommend that you log on your VPS with an SSH private/public key instead of the password.
To do this, you need to generate a private/public key on your client machine (on linux, usually located in /home/your_user/.ssh/id_rsa.pub). If you have one, you can use it otherwise, generate one with the command « ssh-keygen -t rsa », then you copy the content of your local file id_rsa.pub to your VPS in the file /root/.ssh/authorized_keys)
Then try to ssh to the machine, ssh root@your_server, accepting he signature, you should be logged in without password
Now that we can SSH without password, we’ll disable the password authentication in SSH server. Edit the file /etc/ssh/sshd_config, and add the following line (if not already set) :
PasswordAuthentication no
Save and quit, restart the sshd server : service sshd restart
From this point, you can no longer login with a password, only the SSH key is accepted.
No more dictionary attack or password guessing. If ever you lose your local machine/private key, you can always go in the OVH console,through web management interface, and open the vKVM, to connect on the machine through the console with the root password. Enjoy.

Using raspberry pi 3 as wifi bridge and repeater and firewall

Hi again,

following my raspberry 3 router project (http://blog.inforeseau.com/2018/06/raspberry-3-point-dacces-wifi-avec-filtrage-pub-tracking-access-point-add-tracking-filtering) and the repeater project (http://blog.inforeseau.com/2019/01/raspberry-3-create-a-wifi-repeater-with-usb-wifi-dongle) , i decided to fork these into a wifi repeater and bridge.

The goal is to use this approach in hotels or public wifi, where you wish to use your own router with its pi-hole and firewall. Any device connected behind the raspberry, will be hidden behind a totally blocking firewall.

So, let’s make it simple, i assume you took the image of the router project : http://blog.inforeseau.com/2018/06/raspberry-3-point-dacces-wifi-avec-filtrage-pub-tracking-access-point-add-tracking-filtering
I also assume you have the needed hardware ( a raspberry 3 and a wifi adapter like the canakit or panda as recommended into the linked original post)

You then replace the file /etc/rc.local (available as zip file here rc.local ) in the SD CARD rootfs partition, by the following one, in which you customize the following values :
wifissid which is your access point name, the SSID on which you will connect
wifipass which is the password you’ll have to use to this access point
existingwifissid which is the existing wifi on which the raspberry will connect to (the hotel or public wifi SSID)
existingwifipass which is the existing password of the wifi on which the raspberry will connect to (the hotel or public wifi password)

#!/bin/sh
# removed -e option above, because below command returns some warnings that must be ignored
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
printf "My IP address is %s\n" "$_IP"
fi

# Create Access point wifi raspap other USB adapter
#/usr/bin/create_ap --isolate-clients --daemon --ieee80211n --ht_capab '[HT40+]' -c 44 -w 2 wlxe84e0651e6f6 enxb827eb9446d8 raspappriv welcomepriv2

#in this version, we connect to wan through wifi, so the onboard ethernet will be another LAN
onboardlan=`/root/get-nic.sh`
#since we'll connect to an existing wifi
#if using panda wifi, device is called wlan1, if using canakit, device is called wlx......
#we need to know if we have a wlan1
iswlan1=`/sbin/ifconfig -a|/bin/grep wlan1`;
#defining USB wifi interface name
if [ ! -z "${iswlan1}" ]; then
onboardwan="wlan1"
else
#we need to extract it
onboardwan=`/sbin/ifconfig -a|/bin/grep wlx|/usr/bin/awk -F ":" '{print $1}'`;
fi

#using the canakit wifi, only 2.4Ghz is supported, check before entering SSID in here
existingwifissid="my-wifi-ssid"
existingwifipass="my-wifi-password"
#we make sure default wpa-supplicant is empty
/bin/echo "" > /etc/wpa_supplicant/wpa_supplicant.conf
#we now create the one we need to be used with wlan1
#cleanup of the file
/bin/echo "" > /home/pi/wpa_supplicant.conf
#Populate the file
/bin/echo "ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev" > /home/pi/wpa_supplicant.conf
/bin/echo "update_config=1" >> /home/pi/wpa_supplicant.conf
/bin/echo "network={" >> /home/pi/wpa_supplicant.conf
/bin/echo 'ssid="'${existingwifissid}'"' >> /home/pi/wpa_supplicant.conf
/bin/echo 'psk="'${existingwifipass}'"' >> /home/pi/wpa_supplicant.conf
/bin/echo "}" >> /home/pi/wpa_supplicant.conf
#initiate wifi connection
/bin/echo "" > /home/pi/start-wifi.sh
/bin/echo "#!/bin/bash" >> /home/pi/start-wifi.sh
/bin/echo "/sbin/wpa_supplicant -B -c/home/pi/wpa_supplicant.conf -i${onboardwan} -Dnl80211,wext" >> /home/pi/start-wifi.sh
/bin/chmod +x /home/pi/start-wifi.sh;
/home/pi/start-wifi.sh &

#Identify an other NIC in the raspberry (USB plugged one, to be used as LAN, aside of wifi)
usbnic=`/root/get-2nd-nic.sh`

#Force dhcp on interface
/sbin/dhclient ${onboardwan}

#update the NIC interface in the pi-hole config
#drop interface (last line)
/bin/cat /etc/dnsmasq.d/01-pihole.conf| grep -v interface > /root/01-pihole.conf.tmp
#update file without interface
/bin/cat /root/01-pihole.conf.tmp > /etc/dnsmasq.d/01-pihole.conf
#Add interface
/bin/echo "interface="${onboardwan} >> /etc/dnsmasq.d/01-pihole.conf

#restart the service
#systemctl restart dnsmasq

#Define wifi SSID
wifissid="raspappriv"

#Define wifi password
wifipass="welcomepriv2"

#Define wifi ip-net /24 by default
wifinetip="192.168.12.1"
# For home we keep subnet isolated (no bridge) to be able to force web filtering via pi-hole and we allow communication between devices (default IP for the AP is 192.168.12.1 and we run a pi-hole on it for DNS fo we force DNS server to be itself) using embedded wifi
/usr/bin/create_ap --daemon --dhcp-dns ${wifinetip} --ieee80211n --ht_capab '[HT20+]' -c 11 -w 2 wlan0 ${onboardwan} ${wifissid} ${wifipass}

#Now we want to protect the connected interface assuming this is WAN, and nothing from there should come in
#create_ap brings its own rules already
#I accept only packets that were initiated by the device
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
#If you want to allow ping from outside to your device, uncomment below
#iptables -A INPUT -p icmp -j ACCEPT
#We fix slowlyness due to pi-hole as explained here : https://pi-hole.net/2018/02/02/why-some-pages-load-slow-when-using-pi-hole-and-how-to-fix-it/
iptables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset
iptables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp-port-unreachable
iptables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp-port-unreachable
#If you want to route/NAT a port from outside to an internal machine (which has static IP or reserved IP in /root/udhcpd.conf.master like 192.168.12.200 for the example below) to export a service (if you host nextcloud on a machine in your lan and want to make it available) :
#iptables -t nat -A PREROUTING -j DNAT -i ${onboardwan} -p tcp --dport 9443 --to-destination 192.168.12.200:9443

#now, while your service above is available from outside, like https://your-public-ip:9443, it is sadly not responding from internal wifi, so we allow it as well this way
#iptables -t nat -A PREROUTING -j DNAT -i wlan0 -p tcp --deport 9443 --to-destination 192.168.12.200:9443

#if you want to allow SSH to your device from outside (be careful, you'll get a lot of dictionary attacks and hacking attempts), you may want to uncomment below to open port 22 from outside
#iptables -A INPUT -p tcp -m state --state NEW -m tcp --deport 22 -j ACCEPT

#If we have a second interface (usbnic) then, we assign an IP to it, and we start dhcp server, and add propoer firewall rules
if [ ! -z "${usbnic}" ]; then
#we have an USB NIC, we set it up to handle the LAN connections as well
#defining IP
/sbin/ifconfig ${usbnic} 192.168.13.1 netmask 255.255.255.0 broadcast 192.168.13.255
#starting dhcp server on it
#copy the master config file as base (no interface designed)
/bin/cp /root/udhcpd.conf.master /root/udhcpd.conf
#adding the proper interface
/bin/echo "interface ${usbnic}">>/root/udhcpd.conf
#sending DNS request to the pi-hole on pi-hole proper IP
iptables -t nat -A PREROUTING -j DNAT -i ${usbnic} -p tcp --dport 53 --to-destination ${wifinetip}:5353
iptables -t nat -A PREROUTING -j DNAT -i ${usbnic} -p udp --dport 53 --to-destination ${wifinetip}:5353
#Assuming you opened the port 9443 above on wan and wifi, you also want, if connected your LAN machines to be able to access the service, so you would uncomment
#iptables -t nat -A PREROUTING -j DNAT -i ${usbnic} -p tcp --dport 9443 --to-destination 192.168.12.200:9443
#allow ip forward from this LAN
iptables -A FORWARD -s 192.168.13.0/24 -i ${usbnic} -j ACCEPT
#We NAT the traffic from this LAN
iptables -t nat -A POSTROUTING -s 192.168.13.0/24 -j MASQUERADE
#starting udhcpd
/usr/sbin/udhcpd -S /root/udhcpd.conf

fi

####################
#Because we use the WIFI as WAN, we can use the onbard NIC ($onboardlan) as second LAN CARD
####################
#configure onboard LAN IP
/sbin/ifconfig ${onboardlan} 192.168.15.1 netmask 255.255.255.0 broadcast 192.168.15.255
#create dedicated dhcp server config file
/bin/echo "" > /root/udhcpd2.conf
/bin/echo "start		192.168.15.10" >> /root/udhcpd2.conf
/bin/echo "end		192.168.15.254" >> /root/udhcpd2.conf
/bin/echo "lease_file	/var/lib/misc/udhcpd2.leases" >> /root/udhcpd2.conf
/bin/echo "pidfile	/var/run/udhcpd2.pid" >> /root/udhcpd2.conf
/bin/echo "opt	dns	192.168.15.1" >> /root/udhcpd2.conf
/bin/echo "option	subnet	255.255.255.0" >> /root/udhcpd2.conf
/bin/echo "opt	router	192.168.15.1" >> /root/udhcpd2.conf
/bin/echo "option	domain	local" >> /root/udhcpd2.conf
/bin/echo "option	lease	864000" >> /root/udhcpd2.conf
/bin/echo "# Static leases map" >> /root/udhcpd2.conf
/bin/echo "#static_lease 00:60:08:11:CE:4E 192.168.15.54" >> /root/udhcpd2.conf
/bin/echo "#static_lease 00:60:08:11:CE:3E 192.168.15.44" >> /root/udhcpd2.conf
/bin/echo "interface ${onboardlan}" >> /root/udhcpd2.conf
iptables -t nat -A PREROUTING -j DNAT -i ${onboardlan} -p tcp --dport 53 --to-destination ${wifinetip}:5353
iptables -t nat -A PREROUTING -j DNAT -i ${onboardlan} -p udp --dport 53 --to-destination ${wifinetip}:5353
iptables -A FORWARD -s 192.168.15.0/24 -i ${onboardlan} -j ACCEPT
iptables -t nat -A POSTROUTING -s 192.168.15.0/24 -j MASQUERADE
/usr/sbin/udhcpd -S /root/udhcpd2.conf

#If you decided to open the port for your service on 9443 above (NAT), you need to accept it on the router too, so uncomment below
#iptables -A INPUT -p tcp -m tcp --dport 9443 -j ACCEPT

#I refuse any connection otherwise
iptables -A INPUT -i ${onboardwan} -j DROP

#We also load all the iptables helpers modules
/sbin/modprobe ip_nat_ftp nf_conntrack_netbios_ns xt_conntrack xt_multiport ip_nat_sip ip_conntrack_sip nf_conntrack_ftp nf_nat_ftp

exit 0
Then, when the raspberry boots, it will connect to the existing wifi with the information you’ve configure in the file, and will broadcast your own SSID.

You’ll also be able to connect a device on the LAN port, AND the USB LAN adapter if you have the one used for the router project. It means, 2 clients in ethernet (or more if using a switch) and wifi.
From there, you may consider the use of a VPN on the raspberry itself, yet to be tested, i’ll add comments later on, planning to test sshuttle, openvpn (compatibles with protonvpn), and potentially expressvpn. All are working, just to be tested against existing iptables rules basically.
As usual, this is a post to keep a track, and it should work for you as well.

Faire un lien vers cet article (clic, copier, puis coller sur vos pages) : 


				
								
								
				

					lundi, janvier 21st, 2019
					Technologie
					Pas de commentaire
				
				
				

				
			

Raspberry 3 – create a wifi repeater with USB wifi dongle

Updated on 2019 Jan 11 – tested and working from scratch

What you need to do this :

You need a raspberry pi 3 or raspberry pi 3 B+ if you want to handle wifi 5Ghz.
We need an extra wifi adapter (panda 005 or canakit wifi or any kernel supported adapter) – listed below are 2.4Ghz only
https://www.amazon.ca/gp/product/B00EQT0YK2/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
https://www.amazon.ca/CanaKit-Raspberry-Wireless-Adapter-Dongle/dp/B00GFAN498/ref=sr_1_4?s=electronics&ie=UTF8&qid=1546365634&sr=1-4&keywords=raspberry+pi+wifi
or that
https://www.canakit.com/raspberry-pi-wifi.html

What you need to do then

Deploy original raspbian lite on it (this is a network management device, we don’t want or need a GUI on it). SSH to it or connect on the raspberri pi itself. User pi, password raspberry, sudo bash to be root.

Update the system and install requirements as follow :

apt-get update
apt upgrade
apt-get update
 apt-get install git bash util-linux procps hostapd iproute2 iw haveged dnsmasq iptables vim
 git clone https://github.com/oblique/create_ap
 cd create_ap/
 make install
 cd ..

The above does apply all the latest updates, and clone the create_ap script that allows easy wifi access point creation.

You might want to change keyboard layout, which by default is UK. I do use US layout, so to change, run « raspi-config » -> « 4 – Localisation Options » -> « I3 – change keyboard layout » -> »Generic 103… » -> « Other » -> « English (US) » -> « ok » -> « default » -> « ok » -> « no compose key » -> « ok » -> « finish »
(use TAB to switch between buttons)

We want to handle wpa_supplicant manually, because otherwise we can’t assign proper interface. There is a configuration menu on the raspi-config command, but this is NOT what we want. The default wpa_supplicant use any of the wifi adapters to connect, sometime both. But in our case, we want 1 connected, and 1 access point.

mv /etc/wpa_supplicant/wpa_supplicant.conf /home/pi/wpa_supplicant.conf

Content of wpa_supplicant.conf have to be :

 ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
 update_config=1

network={
     ssid="yourexistingwifi"
     psk="existingwifipassword"
 }

In the above, you have to put the SSID of your main / existing wifi, and the password of it as psk. This will allow the raspberry to connect to this network with 1 of its adapters.

We then create a little script that will do what wee need. Create the file /home/pi/start-relaywifi.sh with the following content :

#!/bin/bash
wpa_supplicant -B -c/home/pi/wpa_supplicant.conf -iwlan0 -Dnl80211,wext
 create_ap -g 172.20.0.1 -c 10 -w 2 wlan1 wlan0 relaywifi relaywifipassword

The above use the wlan0 interface to connect to your existing wifi (using most likely the onboard wifi of the raspberry), and the second line create an access point on the second wifi adapter (the USB one) that shares the connection of the first one.

We then set this to be called at boot from /etc/rc.local by adding the following lines before the last line of rc.local :

 /home/pi/start-relaywifi.sh

We then set the executable bit on our little script :

chmod +x /home/pi/start-relaywifi.sh

All good. Reboot the pi, and it should :

Boot raspbian, execute rc.local which call our script, connect to existing wifi, and appear as access point.

Sidenote : The onboard wifi driver does not support full A/P or bridging mode. Therefore, the extended wifi is using its own IP range, which must be different from the main one.
The IP range used in this example is 172.20.0.x, but you can pick any private IP range and adjust the create_ap command accordingly.
Device on extended wifi can speak to the main wifi, but main most likely won’t be able to see the devices on extended. If you have a printer, or so, it should be on the one.
If you want this to happen you should :
– reserve an IP on your main wifi for the raspberry MAC, so as it always gets the same IP
– add a route on your main router, that state, network 172.20.0.x can be reached via IP-YOU-RESERVED for the raspberry
I won’t go more in details, since the point was to get wifi network extended, and connect your wifi devices from bigger range.

I might add french later one, and will test this and adjust if need be, as i said, i have it running, but did not redo everything from scratch 😀

Happy new year 2019 😀