lxd via snapd - containers have no network and ip address after host upgrade
i did an apt-get upgrade and now none of my lxd containers have an ip address. host is debian testing/bullseye. this is the output of sudo journalctl -u snap.lxd.daemon | cat:

-- logs begin at wed 2019-08-14 15:48:13 sast, end at wed 2019-08-14 22:44:49 sast. --

aug 14 21:46:42 vetkoek systemd[1]: …
nevermind, i recently installed the polipo package and it had automatically installed dnsmasq as a dependency. i just removed those packages and my containers are getting ip addresses again.
you have to forward the sip and rtp ports of the snom. (before the update this was done by a sip application layer gateway, but we had to remove this because it breaks security.)

[image]

[security announcement: mitigating nat slipstreaming - the ipfire blog](https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstreaming)

last autumn, we learned about … From the official Node.js documentation:



> 
> A Node.js package is also available in the official repo for Debian Sid (unstable), Jessie (testing) and Wheezy (wheezy-backports) as “nodejs”. **It only installs a nodejs binary.**
> 
> 
> 


So, if you only type `sudo apt-get install nodejs` , it does not install other goodies such as **npm**. 


You need to type:



```
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt-get install -y nodejs

```


> 
> Optional: install build tools
> 
> 
> To compile and install native add-ons from npm you may also need to install build tools:
> 
> 
> 



```
sudo apt-get install -y build-essential

```

More info: [Docs](https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions-enterprise-linux-fedora-and-snap-packages) hi obin, there is no option to upgrade the vcenter from prism. you will have to use the vmware procedure to upgrade the vcenter. so, you do not need to take any action in prism for the vcenter upgrade and there will be no impact on the nutanix cluster. you can upgrade the esxi hosts from the prism later. i was able to solve this with david’s help.

the issue was on the 43763 node (the one i was trying to connect to). since i have shell access to the remote node 43763 as well, i was able to update the rpt\_extnodes file there. in non-hamvoip asl, this is performed by running the rc.updatenodelist scri… this is now fixed no need to commnet. i checked in with the dns team on this one and we’re actually in the process of changing jump\_start to move to a newer system for scanning dns records which the ui uses already.

if you want to try it (the api is not documented yet), you can do this by creating the zone with jump\_start: false and th… don’t worry, possibly you’re using mediasoup, just the name of the media nodes still being named as kurento media server.

to check if mediasoup is running, just ssh into one of the media nodes machine and execute this:

sudo su

docker ps | grep mediasoup

you should see a container using this image… i now use this procedure to check leaderlogs. it’s easier on the ram/cpu and i haven’t had a fail in a while. you need to make sure cncli.db is in sync.

cardano-cli query stake-snapshot --stake-pool-id your pool id --mainnet >/root/scripts/snapshot.json

cncli leaderlog --pool-id your pool id*

… it looks like the updater was running twice and wiped the kernel from your system.

you will find a backup in /var/ipfire/backup which you can restore after performing a fresh installation. what to do::

docker exec -it gitlab /bin/bash

then

apt install update-manager-core

then

do-release-upgrade