Network configuration problems

Configuration
1

I ran into several problems configuring Hassio, all related to the network configuration:

The first problem is related to my ISP that only gives out IPv6-Addresses and tunnels all IPv4 requests to a shared IPv4. Therefore I can not configure IPv4 port forwarding in my router. I have tried to get hassio to only use IPv6, but I could not find any documentation on changing this in Hass.io/resinOS, so I tried to set IPv4 to “manual” in the wifi config file and installed hass.io on a second SD card. SSH connects to an IPv6 address, but ifconfig still returns the IPv4-Address of my ISPs tunnel as inet addr

Also I have been using ethernet but want to switch to wifi. How can I configure this without having to reinstall resinOS? I tried a fresh install on a second sd card, but it doesn’t connect. I assume this is because I am using a Raspi 1 with a Belkin F7D1101 v1, which is supposed to be compatible to Raspbian, so it should be possible to make it work with resinOS. I downloaded the driver r8712u.ko, but how do I install it in resinOS?
When I have the drivers installed, how can I add a Wifi connection in RaisinOS after the installation (on my primary sd card)?

Also I ran into a problem configuring the Google Assistant Add-On. The default Port (9324) for Configuring the Web UI seems not to be opened, I keep getting an ERR_CONNECTION_RESET.
Also the emulated hue bridge is not discovered by Google Assistant on my phone, according to netstat -an resinOS is not listening on port 8300.

My final question is not related to the network configuration:
I plan to make a portable smart home box equipped with a powerbank, the raspi, a raspi display, AUX speaker and USB microphone working as a Google Assistant with a HADashboard. To do this, I plan to connect a raspberry pi touchscreen - does this work with Hassio or do I have to use a raspbian image? Also, is there any way on installing a spotify connect API in Hassio (output to AUX speaker)?

Thank you for your help!

2

Google assistant requires ssl on port 443 I believe (its the first blue box on the article). I bet you could find a way to do this outside of 443 but I haven’t tried (it definitely requires ssl though).

This tutorial shows you how to set that up

3

The problem is that I do not have my own IPv4 address thanks to my annoying German ISP so I cannot use DuckDNS. It is not possible to access my server by IPv4, but it is possible by IPv6. Some other customers of my ISP have found a workaround to host a server from with my ISP anyway using a portmapper.

To do so I need to setup the raspberry pi to connect via IPv6 (not via my ISPs IPv4 tunnel). I probably have to enter something like this in the config file, but the Documentation of resinOS/Hassio is really bad and I cannot find an option to do so.

[ipv4]
method=disabled

[ipv6]
addr-gen-mode=never regenerate my ip
method=auto

If nobody can help me here I will try openHAB, they offer a cloud hosting which should work for me although I prefer a self hosted HASS.

4

I have managed to solve the problem. Since DuckDNS can’t detect IPv6 addresses I had to use Cloudflare. For anyone else with Unitymedia/Kabel BW or another ISP that only gives out IPv4 addresses this is how I solved the problem:

1.) I have not managed to adjust the settings in hass.io/resinos, so I installed hassbian instead
2.) Figure out IPv6: Type ifconfig and copy the global inet6 address
3.) Optional if you already have a domain managed by Cloudflare: Register a free domain at dot.tk. Set up a free account with cloudflare.com and point your DNS settings to the Cloudflare name servers.
4.) Paste your IPv6 address from step 2 to an AAAA record in Cloudflare e.g. for a subdomain. Make sure that Cloudflare is enabled so it can portmap the IPv4 address
5.) Set up NGINX as described here. Since you are using Cloudflare, you need to modify the code in step 3: Install the letsencrypt certbot as described here and then enter the command sudo certbot certonly --webroot --webroot-path /var/www/html --renew-by-default --email [email protected] --text --agree-tos -d myhass343204.example.tk

5

this looks like a big fat pain in the ass…

dang.
I am in austria and i have a similar problem.
I do get a ip4 adress for duckdns, but my router has no ip4 port forwarding so i cant get the packages to my PI, also the PI does not listen on a ip6 adress so i am kinda screwed…

6

As a last resort i contacted my ISP to open the ports, now i have to contact them for every hassio addon that requires port forwarding :expressionless: