svenvogel edited a comment on issue #3179: Redundant VRouter guest network on wrong interface URL: https://github.com/apache/cloudstack/issues/3179#issuecomment-554639329 @ustcweizhou @weizhouapache thanks for the test. We encounter the problem in 2016 that VPC was working from outside but if we use a NAT with Public IP it was not working. Thats because Public Adress was not set on correct interface (dev id). this was the fixed from @fmaximus for the non-redundant router. two questions: You are sure thats working in your test environment with ovs? (NAT, Firewall ...) if its so then we need to test it without #2304 did you remove #2304 in your ovs test setup and used the change from #3179? can you explain how this commit help 6fc389a in our actually problem? did you test both redundant and non-redundant router? >>However, I insist that we should send IpAssocVpcCommand instead of IpAssocCommand , even it might lead to some issues. like @DennisKonrad wrote above. if we use "IpAssocVpcCommand" we get the issues with the VPC redundant router. they are start up and reboot immediately. that why he ask "Do you think it would be possible to write a mac address map based function for both (ovs and linux bridge)?" thats why we ask can you fix this problem? ```json `{"ip_address":[ {"public_ip":"172.20.20.12","source_nat":true,"add":true,"one_to_one_nat":false,"first_i_p":true,"gateway":"172.20.0.1","netmask":"255.255.0.0","vif_mac_address":"1e:00:d5:00:00:c2","new_nic":false,"nw_type":"Public"}],"type":"ips"}```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
