As stated in the KNX association’s “ETS5: Software requirements“, is not supported: “Installing and running ETS5 on a supported operating system in a virtual environment (such as Virtual PC, VM Ware, etc.) and/or via Remote Desktop is not foreseen. Working in such environments is at your own risk.”
As a longtime Macintosh user, I have been running the ETS (version 4 or 5) on different Virtual machine environments over the last 12 years. I started with VMware Fusion on a Mac, moved over to QNAP and ended up on preferring the Proxmox Virtualisation Environment for its ease of backuping and snapshotting. All of these environments worked if you managed to control the following two variables:
Passing through the ETS USB licence key to the Windows host system. This seems straight forward, but I often fought with Windows not recognising the license key. Restarting the Windows system (sometimes even several times) mostly helped. The same was true for the USB-KNX gateway.
The correct network interface settings Connecting the ETS to a KNX IP router / gateway requires setting your virtual machine to bridged network mode (your windows host must receive an IP from your main router). If you omit this, a double-nat might block you from connecting your ETS to your KNX bus. This was the case for me at least.
Do you want to have more control over your network, and maybe separate your IoT devices from your computer and NAS? Then you need to install a router that can handle VLAN’s and gives you more configuration possibilities.
I sorted out my Fritzbox (as a router) and connected my Fiber line (Optical Network Terminal, ONT) to a Unifi Dream Machine Pro (UDMP). Connecting the UDMP directly via SFP+ Fiber module to the Fiber cable entering the house apparently is not supported by the ISP’s in Luxembourg. It seems that they do an additional authentication based on the ONT’s MAC address additionally to the PPPoE authentication.
Internet access configuration
Here’s my setup:
PPPoE configuration for Internet & VoIP
I entered the PPPoE login and password and entered VLAN 35 for incoming traffic. In theory, in Luxembourg Internet access on the WAN side comes through VLAN 35 and VoIP through VLAN 39. But I only configured VLAN 35 and Internet as well as VoIP work on WAN VLAN 35.
This Internet configuration also works with VO’s vDSL Internet access.
You can also activate the IPv6 link using 48 as the prefix. This is experimental. I was able to activate IPv6 but did not (yet) investigate further if it correctly works..
IPv6 configuratiobn
My ISP, Visual Online, provides a public (dynamic) IP as standard. So I do not have a double-NAT situation. Some providers in Luxembourg (like Post) do not offer a public dynamic IP in their standard Fiber package, so these configurations will automatically use a double-NAT situation. If you want to avoid this, you have to book the additional public IP option (NOT the static one but the dynamic public IPv4).
VoIP Phone server configuration
To use VoIP on your phones, you need to have a phone server. Most households in Luxembourg use their FritzBox as the landline VoIP server (if they still have a landline). Alternatively, you might also use FreePBX (or another Asterisk based solution). this is still on my To-Do-list. In the meanwhile, my FritzBox now acts (only) as a Voice over IP phone server behind the UDMP router. Port 1 of the FritzBox is connected to the router, using the internal VoIP VLAN I set up for my phone server and phones. You need to configure this in the Internet / Account information settings. You also have to select other internet provider as your ISP.
Internet account information setup of the FritzBox VoIP server
Here is the working configuration for one of my telephone lines:
Telephony > Telephone Numbers >> Telephone Numbers setting for one of my CID’s
You need to define the Telephony provider, the username, password and FQDN(or IP)/Registrar for your SIP telephony account.
I configured the FritzBox to keep port forwarding enabled every 30 seconds. I do not know if this is absolutely necessary, but with this configuration my VoIP landline works just fine and remains always available.
Keeping the VoIP connection alive
IPTV configuration
I cannot state if IPTV would work using the above configuration as I do not have an IPTV contract.
Note on the FritzBox admin interface access
Normally connecting to the FritzBox’s web interface requires a password only (no username). Be aware, that if you configure the Fritzbox as a normal network client (and not as a router), as in my case, you need to create a user account with username and password to able to access the web interface. If you want to have a backup login possibility, keep the WLAN active, as you should be able to connect through the FritzBox WLAN with the standard admin password without a user login.
Get detailed info on hardware, memory, firmware, mainboard, bus
lshw
Relative to mounted drives:
lshw -class disk
Get that information as html (JSON, XML) page:
lshw -class disk -html
List disks by ID, label, UUID…:
ls -l /dev/disk/by-id
ls -l /dev/disk/by-label
ls -l /dev/disk/by-partlabel
ls -l /dev/disk/by-partuuid
ls -l /dev/disk/by-path
ls -l /dev/disk/by-uuid
sfdisk utility for manipulating disk partitions. List block devices: