{"action":"created","issue":{"url":"https://api.github.com/repos/aabc/ipt-netflow/issues/36","labels_url":"https://api.github.com/repos/aabc/ipt-netflow/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/aabc/ipt-netflow/issues/36/comments","events_url":"https://api.github.com/repos/aabc/ipt-netflow/issues/36/events","html_url":"https://github.com/aabc/ipt-netflow/issues/36","id":66222898,"number":36,"title":"Implement MPLS labeled packet receive in promisc mode","user":{"login":"mzi77","id":11790235,"avatar_url":"https://avatars.githubusercontent.com/u/11790235?v=3","gravatar_id":"","url":"https://api.github.com/users/mzi77","html_url":"https://github.com/mzi77","followers_url":"https://api.github.com/users/mzi77/followers","following_url":"https://api.github.com/users/mzi77/following{/other_user}","gists_url":"https://api.github.com/users/mzi77/gists{/gist_id}","starred_url":"https://api.github.com/users/mzi77/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mzi77/subscriptions","organizations_url":"https://api.github.com/users/mzi77/orgs","repos_url":"https://api.github.com/users/mzi77/repos","events_url":"https://api.github.com/users/mzi77/events{/privacy}","received_events_url":"https://api.github.com/users/mzi77/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-04-03T20:33:13Z","updated_at":"2015-04-06T06:44:57Z","closed_at":null,"body":"Please implement MPLS labeled packet receive in promisc mode, should be ease modification of promisc_rcv(), now MPLS labeled unicast IPv6/IPv4 packets are droped. Maybe I will create patch for it."},"comment":{"url":"https://api.github.com/repos/aabc/ipt-netflow/issues/comments/89947181","html_url":"https://github.com/aabc/ipt-netflow/issues/36#issuecomment-89947181","issue_url":"https://api.github.com/repos/aabc/ipt-netflow/issues/36","id":89947181,"user":{"login":"aabc","id":601398,"avatar_url":"https://avatars.githubusercontent.com/u/601398?v=3","gravatar_id":"","url":"https://api.github.com/users/aabc","html_url":"https://github.com/aabc","followers_url":"https://api.github.com/users/aabc/followers","following_url":"https://api.github.com/users/aabc/following{/other_user}","gists_url":"https://api.github.com/users/aabc/gists{/gist_id}","starred_url":"https://api.github.com/users/aabc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aabc/subscriptions","organizations_url":"https://api.github.com/users/aabc/orgs","repos_url":"https://api.github.com/users/aabc/repos","events_url":"https://api.github.com/users/aabc/events{/privacy}","received_events_url":"https://api.github.com/users/aabc/received_events","type":"User","site_admin":false},"created_at":"2015-04-06T06:44:57Z","updated_at":"2015-04-06T06:44:57Z","body":"That's how I understand it right now.\r\n\r\n1. Basically, it would be enough to just decapsulate MPLS packets (promisc related ./configure option), this should be normal for promisc, because it's *promisc* (we are 'promiscing' into MPLS) and it's configurable.\r\n2. Additional to this, MPLS related V9/IPFIX Elements could be reported. I never had example MPLS flows, so my understanding about them is like this:\r\n 1. I don't sure that MPLS info is *allowed* / or *supposed* to go _together_ with it's decapsulation. There could be just MPLS flows w/o underlying IP info. How useful is to report MPLS Elements with decapsulated IP packet? Should MPLS tag be a flow key?\r\n 2. mplsTopLabelIPv4Address(47) and other routing related Elements can not be reported, because it's routing decision related and linux (at least in requested setup) do not route MPLS.\r\n 3. You mentioned two levels of MPLS tags, so, at least, mplsTopLabelStackSection(70) and mplsLabelStackSection2(71) Elements could be used to report first two tags. Also, mplsTopLabelTTL(200) for top tag only, no element for TTL of other tags.\r\n 3. Where is supposed EoMPLS/VPSL info to go I don't know.\r\n"}}