4.05-2. Generalized forwarding: specifying a flow table entry (b). Consider the three-node network below, that uses flow-based generalized forwarding (e.g. as in OpenFlow) in the network's routers. In...


4.05-2. Generalized forwarding: specifying a flow table entry (b). Consider the three-node network below, that uses flow-based generalized forwarding (e.g. as in OpenFlow) in<br>the network's routers. In the question below, we'll want to create match+action entries in the flow table at router r2, with three ports labelled 1,2.3 (in black). In the question,<br>matches are constrained to be over only four fields: the IP source address, the IP destination address, the upper-layer protocol field of the IP datagram, and the destination port<br>number of the transport-layer segment. The actions are either to drop or to forward(i). that is, to forward a matching packet on port i. The default action (uniess stated othenwise) is<br>that if a packet doesn't match a rule, it will be dropped.<br>OpenFlow<br>controller<br>128.119/16<br>4<br>3<br>53.106/16<br>22.33/16<br>1<br>match<br>action<br>source IP<br>dest. IP<br>protocol<br>dest. port<br>ТСР<br>(b) Suppose we want to implement the following behavior, and that the default configuration is that all traffic from 22.33/16 should be allowed to be forwarded by r2 to the outside<br>network. However, we also want to implement a higher priority rule (which would be earlier in the table, for example) so that users within the 22.33/18 network are never allowed<br>to connect to an external web server on port 80. Specify the flow table row entries to implement this rule, by indicating the column entries below. The * is a wildcard match, which<br>matches everything - you should use * over more specific answers whenever possible.<br>(Note: You can find more exarmples of problerrs simiar to this here<br>|In the

Extracted text: 4.05-2. Generalized forwarding: specifying a flow table entry (b). Consider the three-node network below, that uses flow-based generalized forwarding (e.g. as in OpenFlow) in the network's routers. In the question below, we'll want to create match+action entries in the flow table at router r2, with three ports labelled 1,2.3 (in black). In the question, matches are constrained to be over only four fields: the IP source address, the IP destination address, the upper-layer protocol field of the IP datagram, and the destination port number of the transport-layer segment. The actions are either to drop or to forward(i). that is, to forward a matching packet on port i. The default action (uniess stated othenwise) is that if a packet doesn't match a rule, it will be dropped. OpenFlow controller 128.119/16 4 3 53.106/16 22.33/16 1 match action source IP dest. IP protocol dest. port ТСР (b) Suppose we want to implement the following behavior, and that the default configuration is that all traffic from 22.33/16 should be allowed to be forwarded by r2 to the outside network. However, we also want to implement a higher priority rule (which would be earlier in the table, for example) so that users within the 22.33/18 network are never allowed to connect to an external web server on port 80. Specify the flow table row entries to implement this rule, by indicating the column entries below. The * is a wildcard match, which matches everything - you should use * over more specific answers whenever possible. (Note: You can find more exarmples of problerrs simiar to this here |In the "source IP" column, the flow table entry should be: |In the "dest. IP" column, the flow table entry should be: |In the "dest port" column, the flow table entry should be: |In the "action" column, the flow table entry should be: A. 80 B. 22.33/18 C. 53.108/16 D. 128.119/18 E. drop F. UDP G. forward(1) H.* I. forward(2)
Jun 07, 2022
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here