trilobite

How bloody annoying! Trying to move the tree to another VM and exported *.gramps file from other VM where it was working but get the same problem around the database being locked. It means that the GRAMPSWEB_TREE: setting in the compose file makes no difference. Makes no difference whether I try importing as admin. This is also a single tree setup. This issue is really annoying. Wish the docs referenced it.

“I need WhatsApp for almost everything from talking to family and friends to Work. Most of the world does, and the same is true for Facebook.”

Whatsapp and Facebook bring convienence for sure, but you can live without them. All those that know me, know i refuse to use Whatapp. Those that want to keep up with me have installed Signal. I admit that for business it can be tricky but we have to start somewhere?

This is an interesting thread. Seems to make remote access easy. But are you not putting the trust on those that run that pangolin infrastructure? I suspect the answer is to go VPS if you dont trust? Also, are there workable step by step guides to help you set this all up? I find YT giudes a bit fustrating. Prefer reading :-)

Ah, i had missed this … great example of OSS converging on efforts …

Yeah, i got stuck on this a few months ago when trying to set up Vaultwarden. I gave up for the time being. I need a proper guide that walks you through all the steps :-)

I tend to agree. Slight problem is when u r away from home for long periods

Dont u do this by setting the default address book in ur contacts app. I’ve set it to Radicale account. Works like a chatm. Deleted everything else.

How does it compare with K9-mail?

I use Radical with my family. It didnt implement calendar sharing when i i stalled but i think i read somewhere that they either have or will implement. Need to look into it

ran the above and the following pops up. the MAC ending is c3 is the new one I assigned to the 20.91 address on DHCP pfsense server about an hr ago.

EDIT: wondering whether this may be a network manager problem on the VM client? See here

EDIT2: Even tried running ip addr flush dev <your_adapter_id> as suggested here but no effect at all

EDIT3: This is now solved. It was a client problem. Somewhere buried in the system, a static IP had been set up on this machine in the past I image.

Image

When running ntmui, the 106 address was configured as static address. Deleted it and now only sees the 91 address. Didn’t realise you coudl set two IPs against same interface. This is the page that helped following advice from @nibbler@discuss.tchncs.de of runnign dhclient -v ens18; for i in $(seq 60); do ip a s dev ens18; sleep 1; done

a) turned off VM b) deleted the static mapping and recreated c) change the MAC on the VM and then the same MAC on pfSense d) checked /var/dhcpd/var/db/dhcpd.leases and there is no sign of any 192.168.20.XX lower than 20.110 (from 110 I leave the space availble for occasional wifi access of devices not in my home) e) Rebooted pfSense

absolutely the same problem again :-(

don’t I have not configure proxy arp on PVE. the only arp is what I see cached by pfSense. tried flushing the table in pfSense with not luck … the VM is still hooking up to 106 and this is confirmed in the pfSense ARP table even after flushing, despite the DHCP lease table saying that the VM is hooked to 91.

Can I just check with @tiptoes@sh.itjust.works and @Eggymatrix@sh.itjust.works that what I’m doing is what you are saying.

I’m not setting static IPs at client level. Would be a nightmare. What I do is assign IPs on the DHCP server i.e MAC address on VM1 is XX:XX:XX:XX so I set this MAC address in DHCP to correspond to IP 192.168.20:XX so that the machine gets a unique IP all the time. Is this what you meant? I thought everyone would be doing this nowadays as it so easy to manage, except when something goes wrong like in this case.

Maybe I’m misunderstanding but what I mean is that I assign static IP via DHCP based on the MAC. I’m not setting static IPs at client level. i.e MAC address on VM1 is XX:XX:XX:XX so I set this MAC address in DHCP to correspond to IP 192.168.20:XX so that the machine gets a unique IP all the time. Is this what you meant?

No netplan folder under either /etc/ or /var/run/

See message above. I doubt it. I would have had this problem a lot earlier with other machines.

What a surprise … if I were to believe this I would file for madness state support. Image Look like the VM is having a nice chat with the DHCP sever and both agree that the IP should be 192.168.2’.91. Then one of the two cheat, and actually work on 106. Logs in DHCP server a showing nothing. I even told pfSense to ignore the machine ID and it had no effect whatsoever. Image If there was another DHCP server hiding somewhere, dhclient would have picked that up presumably.

Just to be clear, this is what is in the ARP table on pfSense: Image and this is what is in the DHCP lease table in pfSense. Image What I’ve concluded is that the DHCP sees the VM is online, it probably offered the 91 IP, and just shows it online. The ARP table is showing what the actual assigned IP is (106) and SSH login attempts confirm this. There is no 106 entry in the DHCP table. I would ignore the VM2 element of the equation i described above for now. I added just to describe the conflict that arose when I switched it on. I woudl also say that VM1 was backed up on another Proxmox server I had runnina and then restore it on this new Proxmox server I have with a bigger NVMe.

But if there was another DHCP server hiding somewhere, i would have had this problem years ago with all the other machines that are using the same router/DHCP server?

Well, because its all managed in one place rather than having to go and configure loads of machines

I hadn’t realised that matter was making such progress. I was about to start installing KNEX stuff at my home, which I would later integrate with Zigbee or the other stuff.

You need to share your setup then … :-) I wanted to set this up next.

I’ve been using OpenHab2 for several years now but it only collects data from a few esp sensors I built during covid. I need to get it updated and use it more seriously