{"action":"opened","issue":{"url":"https://api.github.com/repos/Azure/WALinuxAgent/issues/658","repository_url":"https://api.github.com/repos/Azure/WALinuxAgent","labels_url":"https://api.github.com/repos/Azure/WALinuxAgent/issues/658/labels{/name}","comments_url":"https://api.github.com/repos/Azure/WALinuxAgent/issues/658/comments","events_url":"https://api.github.com/repos/Azure/WALinuxAgent/issues/658/events","html_url":"https://github.com/Azure/WALinuxAgent/issues/658","id":220527034,"number":658,"title":"Outbound connectivity from a secondary NIC","user":{"login":"gossion","id":2063764,"avatar_url":"https://avatars3.githubusercontent.com/u/2063764?v=3","gravatar_id":"","url":"https://api.github.com/users/gossion","html_url":"https://github.com/gossion","followers_url":"https://api.github.com/users/gossion/followers","following_url":"https://api.github.com/users/gossion/following{/other_user}","gists_url":"https://api.github.com/users/gossion/gists{/gist_id}","starred_url":"https://api.github.com/users/gossion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gossion/subscriptions","organizations_url":"https://api.github.com/users/gossion/orgs","repos_url":"https://api.github.com/users/gossion/repos","events_url":"https://api.github.com/users/gossion/events{/privacy}","received_events_url":"https://api.github.com/users/gossion/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-04-10T03:12:10Z","updated_at":"2017-04-10T03:12:10Z","closed_at":null,"body":"I met an connection issue on setting up internal load balancer (ILB) on the secondary NIC. Here is the configuration:\r\n\r\n  VM1 has two NICs:\r\n  - VM1NIC1(primary): 10.0.0.5 (subnet 10.0.0.0/24)\r\n  - VM1NIC2(secondary): 10.0.1.5 (subnet 10.0.1.0/24)  #ILB on this NIC\r\n\r\n  ILB:\r\n  - FrondEnd: 10.0.1.4 (subnet 10.0.1.0/24)  #Same subnet with NIC2\r\n  - Backendpool: 10.0.1.5 (VM1NIC2), 10.0.1.6(VM2NIC2)\r\n  - Probe:  -Protocol tcp -Port 80\r\n\r\nWhen I tried to connect to the VM through the ILB frondend 10.0.1.4, it failed. After an investigation, I found that the ILB can't probe the VM through secondary NIC correctly. During probing, the ILB use IP 168.63.129.16 to connect to secondary NICs (10.0.1.5), they are not in same subnet,  so the defalt gateway (10.0.0.1) was used and then it fail to connect. \r\n\r\nAs a workaround, I need to add a custom route for the secondary NIC. The custom route is as below: \r\n```\r\necho 150 custom >> /etc/iproute2/rt_tables \r\n\r\nip rule add from 10.0.1.5 lookup custom\r\nip route add default via 10.0.1.1 dev eth2 table custom\r\n```\r\n\r\nThen the ILB works. I wonder if it is possible that WALA can handle such a situation that traffic from the secondary NIC should go to its gw (10.0.1.1 in this case) rather than use a default gw?\r\n\r\nThanks"}}
{"actor":{"display_login":"gossion"}}