title: Metallb multiple ip(nic) in Layer 2 config
body: <p>i have an on-premise kubernetes cluster setup with 1 master and 2 workernodes.
  I have two adress-ranges where master and workernodes having ips in boths nets. Master (192.168.0.10 and 192.168.1.10), node1 (192.168.0.11 and 192.168.1.11), node2 (192.168.0.12 and 192.168.1.12). I can ping from each node to each other node with either ip adress. I can also ping both all adresses 192.168.0.x and 192.168.1.x from external network.</p>
  <p>the adress range named &quot;intnet&quot; is 192.168.0.200-192.168.0.250
  the adress range named &quot;extnet&quot; is 192.168.1.200-192.168.0.250
  services requiering ips from extnet stall in pending state.</p>
  <p>my metallb adress pool config is as follows</p>
  <pre><code>address-pools:
  - name: intnet
    protocol: layer2
    addresses:
    - 192.168.0.200-192.168.0.250
  address-pools:
  - name: extnet
    protocol: layer2
    addresses:
    - 192.168.1.200-192.168.1.250
  </code></pre>
  <p>my service.yml is like the following</p>
  <pre><code>apiVersion: v1
  kind: Service
  metadata:
    name: sth1
    annotations:
      metallb.universe.tf/address-pool: extnet
  spec:
    selector:
      app: local-web
    ports:
      - port: 80
        targetPort: 80
        protocol: TCP
    type: LoadBalancer
   
  </code></pre>
  <p>is not getting an external ip adress kubectl get svc shows &quot;pending&quot; forever. Whereas when i use &quot;intnet&quot; the service get quickly an ip address from intnet.</p>
  <p>Can anyone help here? What do I miss here?</p>