Where is nw_proto=11 coming from? Isn't SIP usually over TCP or UDP? On Fri, Jun 24, 2016 at 8:25 AM, Hssan Driss <hssan.dr...@gmail.com> wrote:
> Hi everyone, > > I'm working on SDN lab. When intend to block SIP Client IP. We are pushing > the blocking order based on the Src-ip address to Floodlight controller > through REST API. Which is translated on a switch level : > > # dpctl dump-flows unix:/var/run/dp0.sock > stats_reply (xid=0x79853a73): flags=none type=1(flow) > cookie=45035999707555269, duration_sec=9s, duration_nsec=451000000s, > table_id=0, priority=29999, n_packets=0, n_bytes=0, > idle_timeout=0,hard_timeout=0,ip,nw_src=192.168.2.2,nw_proto=11,tp_src=0,tp_dst=0,actions= > cookie=4503599627370496, duration_sec=39s, duration_nsec=677000000s, > table_id=0, priority=100, n_packets=514, n_bytes=231936, > idle_timeout=5,hard_timeout=0,in_port=4,dl_src=00:21:9b:88:04:66,dl_dst=18:03:73:b5:78:4d,actions=output:3 > cookie=4503599627370496, duration_sec=39s, duration_nsec=677000000s, > table_id=0, priority=100, n_packets=685, n_bytes=383282, > idle_timeout=5,hard_timeout=0,in_port=3,dl_src=18:03:73:b5:78:4d,dl_dst=00:21:9b:88:04:66,actions=output:4 > > SIP Client is on 192.168.2.2 > > The flow rule is placed on the switch flow table. However, the Proxy still > receives the packets from that client. > How can I debug and fix this ? > Below my is topology! > > > > Controller Floodlight > _________|________ > | | | > Netfpga ____OVS ___Netfpga > | | | > SIP Proxy SIP > Client1 Client2 > > > Thanks in advance, > Best Regards, > Hssan > > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
