{"action":"opened","issue":{"url":"https://api.github.com/repos/Metaswitch/calico/issues/659","labels_url":"https://api.github.com/repos/Metaswitch/calico/issues/659/labels{/name}","comments_url":"https://api.github.com/repos/Metaswitch/calico/issues/659/comments","events_url":"https://api.github.com/repos/Metaswitch/calico/issues/659/events","html_url":"https://github.com/Metaswitch/calico/issues/659","id":89393247,"number":659,"title":"New felix-INPUT chain prevents exposing service from host","user":{"login":"fasaxc","id":469264,"avatar_url":"https://avatars.githubusercontent.com/u/469264?v=3","gravatar_id":"","url":"https://api.github.com/users/fasaxc","html_url":"https://github.com/fasaxc","followers_url":"https://api.github.com/users/fasaxc/followers","following_url":"https://api.github.com/users/fasaxc/following{/other_user}","gists_url":"https://api.github.com/users/fasaxc/gists{/gist_id}","starred_url":"https://api.github.com/users/fasaxc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fasaxc/subscriptions","organizations_url":"https://api.github.com/users/fasaxc/orgs","repos_url":"https://api.github.com/users/fasaxc/repos","events_url":"https://api.github.com/users/fasaxc/events{/privacy}","received_events_url":"https://api.github.com/users/fasaxc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-18T20:45:10Z","updated_at":"2015-06-18T20:45:10Z","closed_at":null,"body":"Piston Cloud expose more than just the metadata service from the host to VM.  Our tightening up of the rules under #636 has broken that because the packets from VMs hit our \"DENY from tap+\" rule before getting to Piston's own rules.\r\n\r\nIn general, I think we need some supported way to do this.  Ideally, a way that encompasses the special-case of the metadata service in a generic way.  We also need a pragmatic solution for @nbartos for hte short term."}}