I have set up a two-node bare-metal kubernetes cluster configured with weavenet and metallb. I would like services hosted on this cluster to discover and interact with UPnP devices on my home network. I believe that for this to work, the UPnP discovery packets need to be configured to be re-multicasted to my home network. What is the right way to configure re-multicasting between a virtual weavenet network and a local network?
- My home network is on
192.168.1.0/24, with both the master and slave node.
- Kubernetes deploys pods using the default weavenet setup which places all nodes somewhere in the
- I have the ability to deploy services with a metallb LoadBalancer that will provide a LoadBalancer IP somewhere within
What I've tried
I can execute a test discovery script that discovers my UPnP devices using multicast (
220.127.116.11:1900) from any computer on my home network. Once I deploy to the cluster (like this), the UPnP devices are no longer detected. I can see the UPnP packets from other pods in the cluster, but not from my computers directly connected to my home network.
I believe the solution to this problem will involve re-broadcasting the UPnP packets from weavenet to my home network and reverse-proxying the responses… but I don't know how to do something like that with weave net. How can I configure any kind of service/deployment/pod/network that will interact with my UPnP devices the way my test script does when using the host's network?