w XBZIBOETIBLFΓͳ͓͠ɺεϩʔελʔτ࠶ͼʂ Mobile ISP WiFi Mobile Network Internet Destination R1 R2 Cellular Line WiFi Fixed Line Wireless Nodes rmnet0 192.0.2.23 wlan0 203.0.133.24 Home ISP
࠷ۙ8FC35$ͰΘΕ͍ͯ·͢ɻ 4$51PWFS%5-4PWFS6%1XJUI*$& w .PCJMF*1 .PCJMF*1W ଓ͕ΓସΘͬͯݩͷ*1ΞυϨεΛ͍ଓ͚Δ͜ͱͰ5$1ͳͲ͕Εͳ͍Α͏ʹ͢Δ w 5$1'BTU0QFO ଓͨ͜͠ͱ͋ΔϗετؒͰ$PPLJFΛ༻͍Δ͜ͱͰɺXBZIBOETIBLFΛ؆ུԽͯ͠ 4:/ύέοτͱڞʹ%BUBΛૹ͢Δ w 26*$ 6%1্ʹ৴པͰ͖ΔετϦʔϜ੍ޚɺϞόΠϧ౷߹ͳͲΛೖΕɺ41%:)551 ʹ࠷దԽ͞Εͨϓϩτίϧ
All Middleboxes L3 Routers L2 Switches IP Firewalls App. Firewalls Wan Opt. Proxies App. Gateways VPNs Load Balancers IDS/IPS Very Large Large Medium Small Figure 1: Box plot of middlebox deployments for small (fewer than 1k hosts), medium (1k-10k hosts), large (10k-100k hosts), and very large (more than 100k hosts) enterprise networks. Y-axis is in log scale. 2.2 Complexity in Management Figure 1 also shows that middleboxes deployments are diverse. Of the eight middlebox categories we present in Figure 1, the me- dian very large network deployed seven categories of middleboxes, and the median small network deployed middleboxes from four. Our categories are coarse-grained (e.g. Application Gateways in- clude smartphone proxies and VoIP gateways), so these figures rep- resent a lower bound on the number of distinct device types in the network. Managing many heterogeneous devices requires broad expertise and consequently a large management team. Figure 3 correlates the number of middleboxes against the number of networking person- nel. Even small networks with only tens of middleboxes typically required a management team of 6-25 personnel. Thus, middlebox deployments incur substantial operational expenses in addition to hardware costs. Understanding the administrative tasks involved further illumi- nates why large administrative staffs are needed. We break down the management tasks related to middleboxes below. Upgrades and Vendor Interaction. Deploying new features in the network entails deploying new hardware infrastructure. From our Misconfig. Overload Physical/Electric Firewalls 67.3% 16.3% 16.3% Proxies 63.2% 15.7% 21.1% IDS 54.5% 11.4% 34% Table 1: Fraction of network administrators who estimated misconfiguration, overload, or physical/electrical failure as the most common cause of middlebox failure. icy goals (e.g. a HTTP application filter may block social network sites). Cloud-based deployments obviate the need for enterprise administrators to focus on the low-level mechanisms for appliance configuration and focus only on policy configuration. Training. New appliances require new training for administrators to manage them. One administrator even stated that existing train- ing and expertise was a key question in purchasing decisions: Do we have the expertise necessary to use the product, or would we have to invest significant resources to use it? Another administrator reports that a lack of training limits the ben- efits from use of middleboxes: The average very large network in our data set hosts 2850 L3 routers, and 1946 total middleboxes; the average small network in our data set hosts 7.3 L3 routers and 10.2 total middleboxes. w ϧʔλͱಉ͙͡Β͍ͷ.JEEMFCPY͕ల։͞Ε͍ͯΔ w εϞʔϧωοτϫʔΫͰϧʔλΑΓ.JEEMFCPYͷํ͕ଟ͍ 4IFSSZ +VTUJOF FUBM.BLJOHNJEEMFCPYFTTPNFPOFFMTFTQSPCMFNOFUXPSLQSPDFTTJOH BTBDMPVETFSWJDF1SPDFFEJOHTPGUIF"$.4*($0..DPOGFSFODF"$.
Acknowledgment Number Flags Window Checksum Urgent Pointer Options Source Address Destination Address Source Port Destination Port Sequence Number Type of Service Identification Time to Live Protocol Total Length Fragment Offset Header Checksum
Acknowledgment Number Flags Window Checksum Urgent Pointer Options Source Address Destination Address Source Port Destination Port Sequence Number Type of Service Identification Time to Live Protocol Total Length Fragment Offset Header Checksum Version IHL Flags Offset Reserved Payload Acknowledgment Number Flags Window Checksum Urgent Pointer Options Source Address Destination Address Source Port Destination Port Sequence Number Type of Service Identification Time to Live Protocol Total Length Fragment Offset Header Checksum