Changes between Version 13 and Version 14 of BaseDemos
- Timestamp:
- Nov 23, 2010, 8:45:33 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BaseDemos
v13 v14 29 29 The main objective of this demo is to show how ariba provides an invariant network substrate to legacy applications while hiding network issues like mobility, NAT, protocol heterogeneity, and network topology dynamics. Like in [2] we consider a heterogeneous network setup as shown in Figure 2 that consists of two LANs, one running IPv4 and one running IPv6, respectively. Furthermore, an IPv4 WLAN access point attached to notebook N1 and a bluetooth device connected to notebook N3 are deployed. The WLAN uses NAT to multiplex the single IP address of the access point to wireless devices. Furthermore, we employ native serial RFCOMM for communication between N3 and P2 (note that P2 is not using IP). Notebooks N2 and N4 are dual-stacked and connected to both IPv4 and IPv6 LANs. 30 30 31 [[Image()]] 32 31 33 In our demonstration we use two off-the-shelf servers as legacy applications: a web server on P2 using bluetooth, and a Jabber server on notebook N1 connected to the IPv4 WLAN access point and the IPv6 LAN. For setting up these servers without ariba several issues have to be addressed: To access those servers from any device participating in the demo is subject to manual configuration and error-prone. For example, to connect to the IPv4 LAN using bluetooth a personal area daemon (pand) is needed. Furthermore, a translation mechanism is required to forward IPv4 packets to the IPv6 network. Servers located behind NAT middleboxes would impose further problems that require manual configuration such as port forwarding. 32 34