Abstract: Techniques are provided to enable a support for guest access of devices in a network. At a controller apparatus in a first mobility sub-domain of a network comprising a plurality of mobility sub-domains, a request message containing a request for guest network access for a device is received from a first access switch in the first mobility sub-domain. The controller apparatus forwards the request message to a guest controller. At a tunneling endpoint apparatus in the first mobility sub-domain, a tunnel is established to the guest controller to carry traffic between the device and the guest controller. Traffic for the device passes in a tunnel between the first access switch and the tunneling endpoint apparatus in the first mobility sub-domain, through the tunneling endpoint apparatus in the first mobility sub-domain and in the tunnel between the routing apparatus in the first mobility sub-domain and the guest controller.

Abstract: Techniques are provided to enable a support for guest access of devices in a network. At a controller apparatus in a first mobility sub-domain of a network comprising a plurality of mobility sub-domains, a request message containing a request for guest network access for a device is received from a first access switch in the first mobility sub-domain. The controller apparatus forwards the request message to a guest controller. At a tunneling endpoint apparatus in the first mobility sub-domain, a tunnel is established to the guest controller to carry traffic between the device and the guest controller. Traffic for the device passes in a tunnel between the first access switch and the tunneling endpoint apparatus in the first mobility sub-domain, through the tunneling endpoint apparatus in the first mobility sub-domain and in the tunnel between the routing apparatus in the first mobility sub-domain and the guest controller.

Abstract: A troubleshooting system. In particular implementations, a method includes collecting, from a first wireless network element, PEM state associated with a wireless client having a connection problem, and collecting log data associated with the wireless client from the first wireless network elements and one or more other wireless network elements. The method further includes correlating the PEM state and log data based on a network security protocol employed by the wireless client, where the network security protocol corresponds to an expected sequence of events. The correlating includes correlating events and messages collected based on the expected sequence of events, and comparing the correlated sequence of events to a data store of diagnostic information to identify one or more possible causes of the connection problem.

Abstract: A troubleshooting system. In particular implementations, a method includes collecting, from a first wireless network element, PEM state associated with a wireless client having a connection problem, and collecting log data associated with the wireless client from the first wireless network elements and one or more other wireless network elements. The method further includes correlating the PEM state and log data based on a network security protocol employed by the wireless client, where the network security protocol corresponds to an expected sequence of events. The correlating includes correlating events and messages collected based on the expected sequence of events, and comparing the correlated sequence of events to a data store of diagnostic information to identify one or more possible causes of the connection problem.

Abstract: A user gains access to a private network by connecting to a network, either through a hardwired or wireless connection, and then initiates an Internet access request targeting any website. If the user is not already authorized for Internet access, then the user is sent to a first predetermined website that points the user to an authentication server accessible via the Internet. The authentication server sends the user an HTTP form pages requesting authentication information. When the user responds, a network monitoring device within the private network alters the form page to include the user's hardware address and an encoded ID based on the network's location. The authentication server forwards this data to a gate keeper server, which authenticates the new user and transmits an unblock message along with another encoded ID based on the network's location and the user's hardware address.

Abstract: A user gains access to a private network by connecting to a network, either through a hardwired or wireless connection, and then initiates an Internet access request targeting any website. If the user is not already authorized for Internet access, then the user is sent to a first predetermined website that points the user to an authentication server accessible via the Internet. The authentication server sends the user an HTTP form pages requesting authentication information. When the user responds, a network monitoring device within the private network alters the form page to include the user's hardware address and an encoded ID based on the network's location. The authentication server forwards this data to a gate keeper server, which authenticates the new user and transmits an unblock message along with another encoded ID based on the network's location and the user's hardware address.

Abstract: Disclosed is a system which provides virtual Ethernet and virtual Wireless Ethernet (e.g. 802.11b) interfaces for client using a single host device. Providing virtual Ethernet interfaces for a client requires one physical Ethernet card/interface. Providing virtual Wireless Ethernet interfaces for a client requires two physical wireless Ethernet cards/interfaces. Applications can use these virtual interfaces as if they are real interfaces using socket interfaces.

Abstract: Disclosed is a system which provides virtual Ethernet and virtual Wireless Ethernet (e.g. 802.11b) interfaces for client using a single host device. Providing virtual Ethernet interfaces for a client requires one physical Ethernet card/interface. Providing virtual Wireless Ethernet interfaces for a client requires two physical wireless Ethernet cards/interfaces. Applications can use these virtual interfaces as if they are real interfaces using socket interfaces.