Consider the $4-$router network shown in Fig. $3,$ where packet forwarding is controlled by flow tables $($e$.$g$.,$ configured via OpenFlow in an SDN controller$),$ rather than by a forwarding table computed by a routing algorithm. The addresses of networks attached to each of the router is also shown. The interfaces at each of the routers are also as indicated. Suppose we want the following forwarding behavior of packets to be implemented:

UDP packets coming from the source network attached to $3$ and destined to the network attached to $s2$ should be forwarded along the path: $s3->1>>$ s$2.$ UDP packets coming from the source network attached to $s2$ and destined to the network attached to $s4$ should be dropped. Any packet arriving at a router that does not more specific matching rule in the table will be forwarded to the controller for further inspection.

Complete the match$-$plus$-$action tables in each of the routers, s$1,$ s$2,$ s$3,$ and s$4,$ that implement these forwarding behaviors. Your rules should be as strict as possible $($should only allow these behaviors, and no other forwarding behaviors$).$ You can assume that any packet arriving at a router that does not match a rule in that table will be dropped.