Yes, I was referring to the ability to custom configure your DHCP server on Android. Can you do that without a rooted phone and custom app? That was what I meant, I'd be curious to learn if you can do such granular configuration without a custom app/rooted phone.
This is great, this seems like exactly what MetalizeYourBrain actually needs.
The fact that there are two different subnets involved does not matter at all, since I see you are slightly confused about that.
The part that your missing in your Interfaces configuration file is this:
iface home inet static address 192.168.0.X gateway 192.168.0.X netmask 255.255.255.0
The RP is now connected to the home wifi and instead of the 192.168.0.15 I said it to take is on 192.168.0.13.
Interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback
iface eth0 inet manual
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
allow-hotplug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
iface home inet static
address 192.168.0.15
gateway 192.168.0.1
netmask 255.255.255.0
iface phone inet static
address 192.168.43.15
gateway 192.168.43.1
netmask 255.255.255.0
DHCPCD
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
interface eth0
static ip_address=192.168.0.16/24
static routers=192.168.0.1
static domain_name_servers=192.168.0.1
I left the ethernet static IP settings because I thought it has nothing to do with wi-fi so I should not have any problem with that setting being there.
P.S. someone having the same problem and didn't manage to solve.
I see you have 2 wlan interfaces, still should work. insted of wpa-conf the answer has wpa-roam to point to the wpa_supplicant.conf are there any other configs in /etc/network/interfaces.d ?
also this kinda bugs me a little:
# Persist interface configuration when dhcpcd exits. persistent
i hope you did restart after changing configs (or maybe only ifdown ~ ifup )
I did a restart and don't ask me why I have two wlans because I don't know and has been like that since the first I've booted into this installation of Raspbian. No additional settings, I just copied you the entire readout. I can't do ifdown and ifup because I'm through SSH so I went for a reboot.