# LB IP exposed not accessible

**URL:** <https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604>\
**Category:** SUSE Rancher Prime\
**Created:** [December 5, 2022, 9:00am UTC](https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604 "2022-12-05T09:00:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomas.sec](https://avatars.discourse-cdn.com/v4/letter/t/46a35a/32.png) [@thomas.sec](https://forums.suse.com/u/thomas.sec)\
**Post date:** [December 5, 2022, 9:00am UTC](https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604/1 "2022-12-05T09:00:43Z")

</div>

Hi,  
I begin with rancher 2.7 and I have created a custom k8s cluster v1.24.8 + rke2r1 with ubuntu server 22.10 nodes (3 etcd+cp and 3 workers).

Usually, I install metallb and nginx ingress controller (bare-metal deployment) and I manage to access to my apps deployed in the cluster with a LoadBalancer IP.

My nodes have ip forward enabled, overlay and br\_netfilter, swap off, apparmor and firewalld disabled, no NetworkManager service…

**kubectl get svc -n ingress-nginx**  
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
ingress-nginx-controller LoadBalancer 10.43.29.133 **10.31.44.16** 80:30327/TCP,443:30108/TCP 2d19h  
ingress-nginx-controller-admission ClusterIP 10.43.47.59 443/TCP 2d19h

10.31.44.16 is not attached to any of my network interfaces/nodes.

Does someone have an idea ?

Regards,  
Thomas

---

<div class="post-metadata">

**Author:** ![thomas.sec](https://avatars.discourse-cdn.com/v4/letter/t/46a35a/32.png) [@thomas.sec](https://forums.suse.com/u/thomas.sec)\
**Post date:** [December 5, 2022, 10:11am UTC](https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604/2 "2022-12-05T10:11:41Z")

</div>

Sorry if someone waste his time here, I find a solution… It’s a metallb issue ([MetalLB provides Services with IP Addresses but doesn't ARP for the address · Issue #1154 · metallb/metallb · GitHub](https://github.com/metallb/metallb/issues/1154)).

Thanks anyway.

---

<div class="post-metadata">

**Author:** ![Herman\_Milton\_Maleia](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/herman_milton_maleia/32/9633_2.png) [@Herman\_Milton\_Maleia](https://forums.suse.com/u/Herman_Milton_Maleia)\
**Post date:** [June 20, 2023, 3:20pm UTC](https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604/3 "2023-06-20T15:20:43Z")

</div>

Hi @thomas.sec

I´m facing the same issue.  
What did you exactly changed?  
Ip is aasigned but not reacheble.

---

<div class="post-metadata">

**Author:** ![thomas.sec](https://avatars.discourse-cdn.com/v4/letter/t/46a35a/32.png) [@thomas.sec](https://forums.suse.com/u/thomas.sec)\
**Post date:** [June 21, 2023, 7:00am UTC](https://forums.suse.com/t/lb-ip-exposed-not-accessible/39604/4 "2023-06-21T07:00:04Z")

</div>

Hi

I have an IPAddressPool with name “production” and then I have this L2Advertisement :

```auto
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: l2adv
  namespace: metallb-system
spec:
  ipAddressPools:
  - production

```

After adding a L2Advertisement, I was able to access LB IP address.

Hope this will help you

Regards