search

christgau / wsdd

A Web Service Discovery host daemon.
MIT License
860 stars 101 forks source link

Hostname keeps disappearing on win client (Ubuntu VM on Proxmox) #195

Open skywatcher78 opened 10 months ago

skywatcher78 commented 10 months ago

Hello all,

I have already read the statement in the readme (https://github.com/christgau/wsdd?tab=readme-ov-file#tunnelbridge-interface) and I think I don't have the same situation. Having a computer with pve (proxmox) installed and created a vm in pve. I have installed ubuntu 22.04 server on the vm and then installed samba and wsdd, both via ubuntu package managemt (apt install samba wsdd). Wsdd is configured this way in /etc/default/wsdd: WSDD_PARAMS="-4 -i 172.16.10.222"

After a while (I coudn't figure out how long it takes) the name disappears in network view on all my win11 clients. Immediately after restarting via systemctl restart wsdd in shows up again.

On the ubuntu vm I have installed docker engine (ce) which generates multiple new network interfaces (docker0, br-, veth1) in ubuntu. Does this have to do something with this disappearing?

Would it change the behaviour of disappearing when changing the WSDD_PARAMS to "-4 -i ens18" ?

What have I done wrong? Is there any solution to this problem? Or set up a cronjob for restarting wsdd every hour or six or so?

christgau commented 10 months ago

I have already read the statement in the readme (https://github.com/christgau/wsdd?tab=readme-ov-file#tunnelbridge-interface) and I think I don't have the same situation.

Are you sure? I'm not familiar with pve and how is networking handled here. Usually VM managers either create virtual networks and the host acts as router (NAT!? Check the README for that as well), or share a network interface or do something else.

To get an idea on my side: Is the IP(v4) address space in your local network (i.e. the real "physical" one) the same as for the interface you bind to inside the Ubuntu VM (172.16.10.222).

skywatcher78 commented 9 months ago

Hi christgau and thanks for answering.

Are you sure? I'm not familiar with pve and how is networking handled here. Usually VM managers either create virtual networks and the host acts as router (NAT!? Check the README for that as well), or share a network interface or do something else.

pve is just a hypevisor, so think of it the same way as vmware's esxi hypervisor. The guest vm's are added to the underlying network card and become a member of the host networked.

To get an idea on my side: Is the IP(v4) address space in your local network (i.e. the real "physical" one) the same as for the interface you bind to inside the Ubuntu VM (172.16.10.222).

Yes, the ipv4 is on the same network which is 172.16.10/24. That is why i don't understand the wsdd name disappearing in network neighborhood.