Hi,
I am trying to setup a kannel sms gateway preferably as a container or, if not possible, as a vm. Still looking for concise documentation.
Modem is a serial device plugged on ttyS0 of the node running proxmox hypervisor.
command entered: qm set 116 -serial0 /dev/ttyS0
result: update VM 116: -serial0 /dev/ttyS0
a new line serial0: /dev/ttyS0 appears on the vm config file.
qm start 116 returns kvm: -chardev tty,id=serial0,path=/dev/ttyS0: warning: The alias 'tty' is deprecated, use 'serial' instead
What is the correct way to pass a serial modem to an lxc container (if possible) or to vm ?
If container with serial modem is possible, what type of container: priviledged or unpriviledged ? features enabled ?
As you may have guessed i prefer an unprivileged container with the minimum features enabled to have just the serial modem "seen" and managed for use with kannel.
I read a warning on one of the posts that this functionality is experimental. Is it still experimental ? Is it stable ?
TIA.
I am trying to setup a kannel sms gateway preferably as a container or, if not possible, as a vm. Still looking for concise documentation.
Modem is a serial device plugged on ttyS0 of the node running proxmox hypervisor.
command entered: qm set 116 -serial0 /dev/ttyS0
result: update VM 116: -serial0 /dev/ttyS0
a new line serial0: /dev/ttyS0 appears on the vm config file.
qm start 116 returns kvm: -chardev tty,id=serial0,path=/dev/ttyS0: warning: The alias 'tty' is deprecated, use 'serial' instead
What is the correct way to pass a serial modem to an lxc container (if possible) or to vm ?
If container with serial modem is possible, what type of container: priviledged or unpriviledged ? features enabled ?
As you may have guessed i prefer an unprivileged container with the minimum features enabled to have just the serial modem "seen" and managed for use with kannel.
I read a warning on one of the posts that this functionality is experimental. Is it still experimental ? Is it stable ?
TIA.
Last edited: