# Metallb range unreachable outside of VM scope

**URL:** <https://discuss.kubernetes.io/t/metallb-range-unreachable-outside-of-vm-scope/19339>\
**Category:** microk8s\
**Tags:** metallb, network\
**Created:** [March 14, 2022, 1:45pm UTC](https://discuss.kubernetes.io/t/metallb-range-unreachable-outside-of-vm-scope/19339 "2022-03-14T13:45:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gc\_sebastienle](https://avatars.discourse-cdn.com/v4/letter/g/a6a055/32.png) [@gc\_sebastienle](https://discuss.kubernetes.io/u/gc_sebastienle)\
**Post date:** [March 14, 2022, 1:45pm UTC](https://discuss.kubernetes.io/t/metallb-range-unreachable-outside-of-vm-scope/19339/1 "2022-03-14T13:45:54Z")

</div>

Greetings,

I have 3 microk8s clusters running on hosts using KVM.  
Each cluster has a controller plane and 2 workers nodes, representing 3 VMs. Each VM shares the host network through bridging.  
For instance:  
Host has 192.168.10.10  
VM1 (control plane) has 192.168.10.20  
VM2 (worker1) has 192.168.10.21  
VM3 (worker2) has 192.168.10.22

I have setup the metallb service to provide IPs from the range 192.168.10.30 to 192.168.10.39.

I have set up an ingress controller with externalTrafficPolicy set to local and using 192.168.10.30

From VM1, VM2 or VM3, I am able to reach 192.168.10.30 with HTTPS.

However, from the host 192.168.10.10 or any device connected to 192.168.10.0/24, I am not able to reach 192.168.10.30.

Whot would have I been missing?

Best Regards,