text:
Have an account?
Need an account?Create an account
Hybrid Remote Edge Access Point (H REAP) is a wireless solution for branch office and remote office deployments. It enables customers to configure and control access points in a branch or remote office from the corporate office through a wide area network (WAN) link without deploying a controller in each office. The H REAP access points can switch client data traffic locally and perform client authentication locally when the connection to the controller is lost. When connected to the controller, H REAPs can also tunnel traffic back to the controller.
Hybrid REAP is supported only on the 1040, 1130, 1140, 1240, 1250, 3500, 1260, AP801, AP802 access points and on the Cisco WiSM, Cisco 5500, 4400, 2100, 2500, and Flex 7500 Series Controllers, the Catalyst 3750G Integrated Wireless LAN Controller Switch, the Controller Network Module for Integrated Services Routers.
The information in this document is based on these software and hardware versions:
Cisco Unified Controllers version 7.0
Control and Provisioning of Access Points (CAPWAP) protocol based 1040, 1130, 1140, 1240,1250, 1260, AP801, AP802 and 3500 series LAPs
Refer to Cisco Technical Tips Conventions for more information on document conventions.
The CAPWAP, on which Cisco's Unified Wireless Network architecture is based, specifies two different primary modes of wireless access point operation:
Split-MAC—In Split-MAC mode, the system shares key functions of the 802.11 specification between the access point and the controller. In such a configuration, the controller is not only responsible for much of the processing of things such as 802.11 authentications and associations, it also acts as the single point of ingress and egress for all user traffic. Split-MAC access points tunnel all client traffic to the controller via an CAPWAP data tunnel (CAPWAP control also follows the same path.).
Local MAC—Local MAC, in implementing full 802.11 functionality at the access point, allows for the decoupling of the data plane from the control path by terminating all client traffic at the wired port of the access point. This allows not only for direct wireless access to resources local to the access point, but it provides link resiliency by allowing the CAPWAP control path (the link between AP and controller) to be down while wireless service persists. This functionality is particularly useful in small remote and branch offices across WAN links where only a handful of access points are needed and the cost of a local controller is not justified.
Note: Before controller release 5.2, Cisco's Unified Wireless architecture was based on LWAPP protocol.
The Hybrid Remote Edge Access Point, or H REAP, is a feature supported by 1040, 1130, 1140, 1240, 1250, 3500, 1260, AP801, AP802 access points and on the Cisco WiSM, Cisco 5500, 4400, 2100, 2500, and Flex 7500 Series Controllers, the Catalyst 3750G Integrated Wireless LAN Controller Switch, the Controller Network Module for Integrated Services Routers. The H REAP feature is supported only in the Cisco Unified Wireless Network controller release version 4.0 or later, the selectable feature of this software allows for the merging of both Split and Local MAC CAPWAP operations for maximum deployment flexibility. Client traffic on H REAPs can either be switched locally at the access point or tunneled back to a controller, which depends on each WLAN configuration. Further, locally switched client traffic on the H REAP can be 802.1Q tagged in order to provide for wired side separation. During a WAN outage, service on all locally switched, locally authenticated WLANs persists.
This is a diagram of a common H REAP implementation:
As this diagram indicates, H REAP has been designed and is intended specifically for remote and branch office deployments.
This document outlines the H REAP theory of operations, controller and access point configuration, and network design considerations.
There are a few different modes by which H REAP functionality operates in order to provide for both local and central switching, as well as WAN link survivability. The mixture of these two sets of modes, while providing an array of functionality, also carries differing limitations depending on pairing.
These are the two sets of modes:
Central vs. Local Switching
WLANs (suites of security, QoS, and other configuration parameters tied to SSIDs) on H REAPs may either be set to require all data traffic be tunneled back to the controller (called central switching) or WLANs may be configured to drop all client data locally at the H REAP's wired interface (known as local switching). Locally switched WLANs may optionally carry 802.1Q tagging to allow such WLANs to be segmented over the wired network at the Ethernet port of the access point.
Connected vs. Standalone
A Hybrid-REAP is said to be in the Connected mode when its CAPWAP control plane back to the controller is up and operational, meaning the WAN link is not down. Standalone mode is specified as the operational state the H REAP enters when it no longer has connectivity back to its controller.
Note: All H REAP security authentication processing (such as backend RADIUS authentication and pairwise master key [PMK] derivation) happens at the controller while the access point is in the connected state. All 802.11 authentication and association processing happens at the H REAP, no matter which mode the access point is in. When in Connected mode, H REAP proxies these associations/authentications to the controller. In Standalone mode, the access point cannot inform the controller of such events.
H REAP functionality varies depending upon its mode of operation (whether an H REAP is in the Connected or Standalone mode), how each WLAN is configured for both data switching (central or local) and wireless security.
When a client connects to an H REAP access point, the access point forwards all authentication messages to the controller and, upon successful authentication, its data packets are then either switched locally or tunneled back to the controller, according to the configuration of the WLAN to which it is connected. With respect to client authentication mechanism and data switching operation, WLANs on H REAP can be in any one of the following states depending on the WLAN configuration and the state of the access point/controller connectivity:
central authentication, central switching—In this state, for the given WLAN, the access point forwards all client authentication requests to the controller and tunnels all client data back to the controller, as well. This state is valid only when the access point's CAPWAP control path is up. This means the H REAP is in Connected mode. Any WLAN that is tunneled back to the controller is lost during WAN outage, no matter the authentication method.
central authentication, local switching—In this state, for the given WLAN, the controller handles all client authentication, and the H REAP access point switches data packets locally. After the client authenticates successfully, the controller sends an CAPWAP control command to the H REAP instructing the access point to switch that given client's data packets locally. This message is sent per client upon successful authentication. This state is applicable only in Connected mode.
local authentication, local switching—In this state, the H REAP access point handles client authentications and switches client data packets locally. This state is valid only in Standalone mode and only for authentication types that can be handled locally at the access point. When a hybrid-REAP access point enters standalone mode, WLANs that are configured for open, shared, WPA-PSK, or WPA2-PSK authentication enter the local authentication, local switching state and continue new client authentications.
Note: All Layer 2 wireless data encryption is always handled at the access point. All client authentication processes occur on the controller (or upstream from the controller, depending on WLAN and controller configuration) while the AP is in the connected state.
authentication down, local switching—In this state, for the given WLAN, the H REAP rejects any new clients that try to authenticate, but it continues to send beacons and probe responses to keep existing clients properly connected. This state is valid only in Standalone mode.
If a locally switched WLAN is configured for any authentication type that is required to be processed on (or north of) the controller (such as EAP authentication [dynamic WEP/WPA/WPA2/802.11i], WebAuth, or NAC), upon WAN failure, it enters the authentication down, local switching state. Previously it would have been in the central authentication, local switching state. Existing wireless client connectivity is maintained and access to local wired resources persist, but no new associations are allowed. If a user's web session times out when using WebAuth or, if a user's EAP key validity interval expires when using 802.1X, and requires re-keying, existing clients lose connectivity and are denied connectivity (this duration is RADIUS server-specific and thus, non-standard). Also, 802.11 roaming events (between H REAPs) trigger full 802.1X re-authentications and thus, will represent the point at which existing clients are no longer allowed connectivity.
When such a WLAN's client count equals zero, the H REAP ceases all associated 802.11 functions and no longer beacons for the given SSID, thus moving the WLAN to the next H REAP state: authentication down, switching down.
Note: In controller software release 4.2 or later, WLANs that are configured for 802.1X, WPA 802.1X, WPA2 802.1X, or CCKM, can also work in Standalone mode. But these authentication types require that an external RADIUS server be configured. More details on this is provided in the sections to come. But, from controller software release 5.1, the H REAP itself can be configured as a RADIUS server.
authentication down, switching down—In this state, the WLAN on a given H REAP disassociates existing clients and stops sending beacons and probe responses. This state is valid only in Standalone mode.
When an H REAP access point enters standalone mode, it disassociates all clients that are on centrally switched WLANs. For web-authentication WLANs, existing clients are not disassociated, but the H REAP access point no longer sends beacons when the number of associated clients reaches zero (0). It also sends disassociation messages to new clients that associate to web-authentication WLANs. Controller-dependent activities such as network access control (NAC) and web authentication (guest access) are disabled, and the access point does not send any intrusion detection system (IDS) reports to the controller.
Note: If your controller is configured for NAC, clients can associate only when the access point is in connected mode. When NAC is enabled, you need to create an unhealthy (or quarantined) VLAN so that the data traffic of any client that is assigned to this VLAN passes through the controller, even if the WLAN is configured for local switching. After a client is assigned to a quarantined VLAN, all of its data packets are centrally switched.
The hybrid-REAP access point maintains client connectivity even after it enters standalone mode. However, once the access point re-establishes a connection with the controller, it disassociates all clients, applies new configuration information from the controller, and reallows client connectivity.
Because the H REAP has been designed specifically to operate across WAN links, it has been optimized for such installations. Though H REAP is flexible when it comes to these remote network design scenarios, there are still a few guidelines that need to be honored when architecting a network with H REAP functionality.
An H REAP access point can be deployed with either a static IP address or a DHCP address. In the case of DHCP, a DHCP server must be available locally and must be able to provide the IP address for the access point at bootup.
H REAP supports up to four fragmented packets or a minimum 500-byte maximum transmission unit (MTU) WAN link.
Roundtrip latency must not exceed 300 milliseconds (ms) for data and 100 ms for voice and data between the access point and the controller, and CAPWAP control packets must be prioritized over all other traffic.
The controller can send multicast packets in the form of unicast or multicast packets to the access point. In H REAP mode, the access point can receive multicast packets only in unicast form.
In order to use CCKM fast roaming with H REAP access points, you need to configure H REAP groups.
H REAP access points support multiple SSIDs.
NAC out-of-band integration is supported only on WLANs configured for H REAP central switching. It is not supported for use on WLANs configured for H REAP local switching.
Note: During an upgrade, each AP needs to retrieve a 4 MB code update across the WAN link. Plan upgrades and change Windows accordingly.
In order to ensure that support for this stated latency limitation is in place, it is strongly recommended that between the access point and controller, priority be configured in the intermediary infrastructure to elevate CAPWAP (UDP port 5246) to the highest priority queue available. Without priority placed on CAPWAP control, spikes in other network traffic can very likely cause H REAP access points to frequently shift from connected to Standalone modes as WAN link congestion prevents access point/controller messages (and keep-alives) from being delivered. It is highly recommended to Network designers, who plan to deploy H REAP AP over WAN links, to test all their applications.
Frequent H REAP flapping causes serious connectivity issues. Without proper network prioritization in place, it is prudent to place controllers at remote sites to ensure consistent and stable wireless access.
Note: Whether H REAP is configured to tunnel client traffic back to the controller or not, the CAPWAP data path is used to forward all 802.11 client probes and authentication/association requests, RRM neighbor messages, and EAP and web authentication requests back to the controller. As such, ensure that CAPWAP data (UDP port 5247) is not blocked anywhere between the access point and controller.
In order to better organize and manage your H REAP access points, you can create H REAP groups and assign specific access points to them. All of the H REAP access points in a group share the same CCKM, WLAN, and backup RADIUS server configuration information. This feature is helpful if you have multiple H REAP access points in a remote office or on the floor of a building and you want to configure them all at once. For example, you can configure a backup RADIUS server for an H REAP group rather than having to configure the same server on each access point.
Controller software releases 126.96.36.199 and later contain two new H REAP group features:
Backup RADIUS server—You can configure the controller to allow an H REAP access point in standalone mode to perform full 802.1X authentication to a backup RADIUS server. You can configure a primary RADIUS server or both a primary and secondary RADIUS server.
Local authentication—You can configure the controller to allow a H REAP access point in standalone mode to perform LEAP or EAP FAST authentication up to 20 statically configured users. With Controller software release 5.0 onwards, this has been increased to 100 statically configured users. The controller sends the static list of usernames and passwords to each H REAP access point when it joins the controller. Each access point in the group authenticates only its own associated clients. This feature is ideal for customers who migrate from an autonomous access point network to a CAPWAP H REAP access point network and do not need to maintain a large user database nor add another hardware device to replace the RADIUS server functionality available in the autonomous access point.
Controller software releases 22.214.171.124 and later contain these new H REAP group features:
Local authentication—This feature is now supported even when H REAP access points are in Connected Mode.
OKC Fast Roaming—H REAP Groups are required for CCKM/OKC fast roaming to work with H REAP access points. Fast roaming is achieved by caching a derivative of the master key from a full EAP authentication so that a simple and secure key exchange can occur when a wireless client roams to a different access point. This feature prevents the need to perform a full RADIUS EAP authentication as the client roams from one access point to another. The H REAP access points need to obtain the CCKM/OKC cache information for all the clients that might associate so they can process it quickly instead of sending it back to the controller. If, for example, you have a controller with 300 access points and 100 clients that might associate, sending the CCKM/OKC cache for all 100 clients is not practical. If you create an H REAP Group comprising a limited number of access points (for example, you create a group for four access points in a remote office), the clients roam only among those four access points, and the CCKM/OKC cache is distributed among those four access points only when the clients associate to one of them. This feature, along with Backup Radius and Local Authentication (Local-EAP), ensures no operational downtime for your branch sites.
Note: CCKM fast roaming among H REAP and non-H REAP access points is not supported.
Refer to the Configuring Hybrid-REAP Groups section of Cisco Wireless LAN Controller Configuration Guide, Release 7.0 for more information on how to configure H REAP groups.
H REAP access points may be connected to 802.1Q trunk links or untagged access links. When connected to a trunk link, H REAP access points send their CAPWAP control and data traffic back to the controller via the native VLAN. Locally switched WLANs may then have their traffic dropped on any available VLANs (native, or otherwise). When set to operate on an access link (with no 802.1Q visibility), H REAPs forward all CAPWAP messages and locally switched user data out to the single, untagged subnet to which it is connected.
General guidelines for the selection of the switchport mode for H REAPs are as follows:
Use a trunk link if more than one WLAN is configured for local switching and if traffic on these SSIDs needs to be dropped on different subnets. Both the access point and the upstream switchport need to be configured for 802.1Q trunking. The configuration of H REAPs for 802.1Q trunking is the most common configuration and provides the most flexibility. Native VLAN also needs to be configured on the switchport that the H REAP is connected to as all CAPWAP communication between the AP and the WLC is on the native VLAN.
Use an access link when H REAPs either do not have more than a single locally switched WLAN or have multiple locally switched WLANs that do not require wired-side separation. Be aware that a trunk link can still be desirable under these conditions if separation between CAPWAP messaging and user data is desired. But, this is neither a configuration requirement, nor a security risk.
Note: H REAP access points default to operate on untagged, access link interfaces.
H REAP supports every controller discovery mechanism characteristic of access points in Cisco's Unified Wireless Network architecture. Once the access point has an IP address (provided either dynamically via DHCP, or through static addressing) it attempts to discover controllers in the system via IP broadcast, DHCP option 43, DNS, and over-the-air provisioning (OTAP). Finally, H REAPs remember the IP addresses of the controller to which they were previously connected. Refer to Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC) for information on the different methods that a LAP can use to register with a WLC.
There are a few caveats to keep in mind in regards to controller discovery. These considerations apply to all Aironet access points and not just H REAPs.
DHCP option 43 is only a viable discovery mechanism for H REAP if the access point receives its IP addressing through DHCP.
OTAP only works for Aironet access points that have already connected to a controller and downloaded code. They ship without radio firmware, so OTAP does not work directly out of the box. OTAP also requires that other nearby access points have found and connected to a controller on which OTAP is enabled. This feature is obsolete from WLC 6.0 release onwards.
An access point on which H REAP functionality is supported does not support LWAPP CAPWAP Layer 2 mode. Controllers must be set to operate with Layer 3 LWAPP CAPWAP .
Refer to Deploying Cisco 440X Series Wireless LAN Controllers for more information on access point/controller discovery. operations
Beyond these traditional controller discovery mechanisms, software release 4.0 and later allows Aironet access points with console ports to now support manual provisioning through the console CLI. Access points can now be manually configured for static IP addressing, hostname assignment, and the IP addresses of the controllers to which the access points should connect. This means that at sites where other discovery mechanisms are not available, access points can be configured with all necessary connectivity configuration manually through the console port.
Although this feature is supported on every Aironet access point with a console port, not just those configured for H REAP, this functionality is particularly useful for H REAPs because they are more likely to find themselves installed in sites that are not equipped with DHCP servers and controller discovery mechanisms, such as in a branch office. As such, this new console access obviates the need to ship H REAPs twice: once to a central site for provisioning and a second time to the remote site for installation.
Because H REAP access points are designed to be placed across WAN links from controllers, not only are there design considerations that need to be kept in mind when architecting a wireless network with H REAPs, but there are also some features that are completely or in-part unsupported.
There is no deployment restriction on the number of H REAP access points for each location.
Refer to H REAP Feature Matrix for more information on the features supported with H REAP.
Security support on the H REAP varies, which depends on the modes and states previously mentioned. Any security type that requires control over the data path such as VPN, does not work with traffic on locally switched WLANs because the controller cannot exercise control over data that is not tunneled back to it. Any other security type works on either centrally or locally switched WLANs, provided the path between the H REAP and the controller is up. When this conduit is down, only a subset of these security options allow new clients to connect to locally switched WLANs.
As previously mentioned, in order to support 802.1X EAP authentication, H REAP access points in standalone mode need to have their own RADIUS servers to authenticate clients. This backup RADIUS server can be the one used by the controller. You can configure a backup RADIUS server for individual H REAP access points through the controller CLI or for H REAP groups through either the GUI or CLI. A backup server configured for an individual access point overrides the RADIUS server configuration for an H REAP group.
WLC Version 188.8.131.52 and later support fast secure roaming with Cisco Centralized Key Management (CCKM). H REAP mode supports Layer 2 fast secure roaming with CCKM. This feature prevents the need for full RADIUS EAP authentication as the client roams from one access point to another. In order to use CCKM fast roaming with H REAP access points, you need to configure H REAP groups. CCKM works in standalone mode for already connected clients but not for new clients.
Refer to the Configuring Hybrid-REAP Groups section of Cisco Wireless LAN Controller Configuration Guide, Release 7.0 for more information on how to configure H REAP groups.
With H REAP in Connected mode, the controller is free to impose client exclusion/blacklisting in order to prevent some clients from associating to its access points. This function can happen either in automated or manual fashion. According to global and per-WLAN configurations, clients can be excluded for a host of reasons, which ranges from repeated failed authentication attempts to IP theft, and for any given amount of time. Clients can also be entered into this exclusion list manually. The exercising of this feature is only possible while the access point is in Connected mode. But, clients that have been placed on this exclusion list remain unable to connect to the access point, even while it is in Standalone mode.
Note: WLANs that use MAC Authentication (local or upstream) are no longer allow additional client authentications when the access point is in Standalone mode, identical to the way a similarly configured WLAN with 802.1X or WebAuth would operate in the same mode.
Internal Web Authentication, hosted on the Wireless LAN Controller, is supported for WLANs that are either centrally or locally switched. However, External Web Authentication is only supported on a centrally switched WLAN.
Note: Neither Web Authentication method is supported while an H REAP is in Standalone mode.
Because of the fact that many remote deployments have only a small handful of H REAPs, full Radio Resource Management (RRM) functionality might not be supported at each H REAP site. Full RRM code is present in H REAP, but the Transmit Power Control (TPC) algorithms in RRM are not triggered until four or more access points are within range of each other. So, some H REAP installations might never power their radios down. As such, without ever being able to power down their radios in the first place, H REAPs do not adjust transmit power upward to compensate in the event of a coverage hole detection.
In Standalone mode, RRM functions on H REAPs that require controller processing are not supported.
Refer to Radio Resource Management under Unified Wireless Networks for more information and operational details of RRM.
Dynamic Frequency Selection (DFS) is supported in both connected and Standalone modes.
Location Tracking
The ability to provide for accurate device location determination varies greatly from location to location, based greatly on the number, density, and placement of H REAPs. Location accuracy hinges heavily on the richness of device signal information collection, which directly correlates with the number of access points that are able to hear a given device. Because H REAP deployments vary in scope, this location information may be greatly reduced and thus location accuracy might suffer accordingly. While H REAP deployments attempt to indicate the location of devices with the highest confidence possible, Cisco's stated location accuracy claims are not supported in such environments.
Note: H REAP was not designed to provide location services. Therefore, Cisco cannot support stated location accuracy claims in H REAP deployments.
L2 and L3 Mobility
Regular Layer 2 roaming is supported for locally switched WLANs. In order to provide for such roaming, ensure the VLANs assigned to locally switched WLANs are consistent across all H REAPs between, which roaming is required. This means that clients are not required to re-DHCP upon roaming events. This helps to decrease the latencies associated with such roams.
Roaming events between H REAPs on locally switched WLANs may take between 50 ms and 1500 ms, which depend on WAN latency, RF designs and environmental characteristics, as well as security types and client-specific roaming implementations.
Layer 3 roaming is not supported for locally switched WLANs, but is supported for centrally switched WLANs.
NAT and PAT are not supported for H REAP access points.
Other H REAP Limitations
H REAPs do not support WGB.
If you have configured a locally switched WLAN, then Access Control Lists (ACLs) do not work and are not supported. On a centrally switched WLAN, ACLs are supported.
Any changes to a locally switched WLAN configuration on the Controller cause a temporary loss in connectivity as the new configuration is applied to the H REAP. As such, any clients on these locally switched WLAN get temporarily disconnected. The WLAN is enabled right away and the clients re-associate back.
The controller can send multicast packets in the form of unicast or multicast packets to the access point. In hybrid-REAP mode, the access point can receive multicast packets only in unicast form.
Note: If the H REAP is connected to 802.1Q trunk link and there are locally switched WLANs configured for VLAN, then the order of the WLAN configuration becomes important due to a limitation in the design. If you change the order of the WLAN for example WLAN 1 is configured for ssid wlan-a and WLAN 2 is configured for ssid wlan-b and their order is changed through configuration WLAN 1 becomes ssid wlan-b and WLAN 2 becomes ssid wlan-a, then both the WLANs lose their VLAN mapping that is configured from the WLC.
Note: The same issue applies of an H REAP that joins a different controller that has different order of the same WLANs. The primary and secondary controllers for a hybrid REAP access point must have the same configuration. Otherwise, the access point can lose its configuration, and certain features, such as WLAN override, AP group VLANs, static channel number, and so forth, can potentially not operate correctly. In addition, make sure to duplicate the SSID of the H REAP access point and its index number on both controllers.
H REAP Fault Tolerance allows wireless access and services to branch clients when:
H REAP Branch APs lose connectivity with the primary controller.
H REAP Branch APs are switching to the secondary controller.
H REAP Branch APs are re-establishing connection to the primary controller.
H REAP Fault Tolerance, along with the Local EAP as outlined above, together provide zero branch downtime during a network outage. This feature is enabled by default and cannot be disabled. It requires no configuration on the controller or AP. However, to ensure Fault Tolerance works smoothly and is applicable, this criteria should be maintained:
WLAN ordering and configurations have to be identical across the primary and backup controllers.
VLAN mapping has to be identical across the primary and backup controllers.
Mobility domain name has to be identical across the primary and backup controllers.
It is recommended to use controller platform as both primary and backup controllers.
H REAP will not disconnect clients when the AP is connecting back to the same controller provided there is no change in configuration on the controller.
H REAP will not disconnect clients when connecting to the backup controller provided there is no change in configuration and the backup controller is identical to the primary controller.
H REAP will not reset its radios on connecting back to the primary controller provided there is no change in configuration on the controller.
Supported only for H REAP with Central/Local Authentication with Local Switching.
Centrally authenticated clients require full re-authentication if the client session timer expires before the H REAP AP switches from Standalone to Connected mode.
Primary and backup controllers must be in the same mobility domain.
The first step to deploying an H REAP network is to configure the switch to which the H REAP will connect. This example switch configuration includes a native VLAN configuration (the subnet on which H REAPs will communicate with the controller with CAPWAP) and two subnets on which the data from the clients of two locally switched WLANs will terminate. If IP addressing is not provided to access points and to clients of locally switched WLANs via the upstream switch (as shown below), then either DHCP services need to be provided via other means, or addressing needs to be provided statically. Although DHCP is recommended, some will likely opt to static access point addressing and provide wireless users addresses via DHCP. Superfluous switch configurations have been removed from this example for simplicity.
ip dhcp excluded-address 10.10.10.2 10.10.10.99 ip dhcp pool NATIVE network 10.10.10.0 255.255.255.0 default-router 10.10.10.1 ! ip dhcp pool VLAN11 network 10.10.11.0 255.255.255.0 default-router 10.10.11.1 ! ip dhcp pool VLAN12 network 10.10.12.0 255.255.255.0 default-router 10.10.12.1 ! interface FastEthernet1/0/1 description H REAP Example Config switchport trunk encapsulation dot1q switchport trunk native vlan 10 switchport trunk allowed vlan 10,11,12 switchport mode trunk ! interface Vlan10 ip address 10.10.10.1 255.255.255.0 ! interface Vlan11 ip address 10.10.11.1 255.255.255.0 ! interface Vlan12 ip address 10.10.12.1 255.255.255.0 end
Note: The actual IP addressing in this example and all subsequent configurations is purely for illustrative purposes. As such, IP addressing MUST be planned with each individual network and need in mind.
In this configuration example, the H REAP is connected to the first FastEthernet interface and receives IP addressing via DHCP from the switch on the native VLAN (VLAN 10). Unnecessary VLANs are pruned from the trunk link connected to the H REAP in order to limit the processing of extraneous packets. VLANs 11 and 12 have been prepared to provide IP addressing to clients of the two WLANs that are tied to them.
Note: The switch to which H REAPs connect needs upstream connectivity to routing infrastructure. H REAP best practices dictate that remote-site/WAN routing infrastructure prioritize CAPWAP control (UDP port 5246).
Here is a sample configuration of a upstream router where the H REAP AP was connected in order to prioritize CAPWAP traffic.
ip cef ! frame-relay switching ! class-map match-all 1 match access-group 199 ! policy-map mypolicy class 1 bandwidth 256 ! interface Serial0/0 ip address 10.1.0.2 255.255.255.0 encapsulation frame-relay frame-relay interface-dlci 101 frame-relay intf-type dce service-policy output mypolicy ! access list 199 permit udp any any eq 5246
H REAPs will most commonly discover upstream controllers via DHCP option 43 or DNS resolution. Without either of these methods available, it may be desirable to provide detailed instructions to administrators at remote sites so that each H REAP may be configured with the IP address of the controllers to which they should connect. Optionally, H REAP IP addressing may be set manually as well (if DHCP is either not available or not desired).
This example details how an H REAP's IP address, hostname, and controller IP address may be set through the console port of the access point.
AP_CLI#capwap ap hostname ap1130 ap1130#capwap ap ip address 10.10.10.51 255.255.255.0 ap1130#capwap ap ip default-gateway 10.10.10.1 ap1130#capwap ap controller ip address 172.17.2.172
Note: Access points must run the LWAPP-enabled IOS® Recovery Image Cisco IOS Software Release 12.3(11)JX1 or later in order to support these CLI commands out of the box. Access points with the SKU prefix of LAP (for example, AIR-LAP-1131AG-A-K9), shipped on or after June 13, 2006 run Cisco IOS Software Release 12.3(11)JX1 or later. These commands are available to any access point that ships from the manufacturer running this code level, has the code upgraded manually to this level, or is upgraded automatically by connecting to a controller running version 6.0 or later.
These configuration commands are only accepted when the access point is in Standalone mode.
When an access point has never been connected to a controller before, access points have the default CLI password of Cisco. Once access points are connected to a controller, no CLI configurations may be made through the access point's console until the password is changed. This CLI-only command is entered at the controller with this syntax:
(WLC_CLI)>config ap username <user-id> password <passwd> {all | <AP name>}
For the above access point, this command might be used:
(WLC_CLI)>config ap username admin password pass ap1130
Note: Although this command requires the creation of a username, this field is not presently implemented and is reserved for future use.
Note: All show and debug commands will operate fine without the access point's default passwords being changed.
Once the H REAP has discovered and joined the controller, all H REAP configurations are done through the controller's web or command-line interfaces (alternatively, configuration may be done centrally through the Wireless Control System [WCS]). The H REAP configurations in this section are performed through the controller graphical interface.
Start by creating and configuring the desired WLANs. For this example configuration, the WLANs are as follows (tailor configurations as necessary):
In order for an H REAP access point to operate as an H REAP, the controller to which it is connected must have at least one locally switched WLAN (without this, H REAP's high-availability functionality will not be realized).
Complete these steps in order to configure a locally switched WLAN:
Go to the main page of the controller, choose WLANs, and click New.
Assign the WLAN a name, which is also used as the SSID, and click Apply.
In the WLAN > Edit page, click the Security tab. Under Layer 2 Security, select the security type.
For this example, WPA2-PSK is desired. Choose WPA+WPA2.
Check WPA2 Policy in order to specify the WPA operations of the WLAN.
Check AES in order to set the encryption method.
Under Auth Key Mgmt, choose PSK from the drop-down menu.
Depending on the desired key format, the choice here hinges on ease of use and client support, select either ascii or hex. Ascii is typically easier because alphanumeric characters are accepted. Choose ascii and enter the desired pre-shared key.
Click the Advanced tab. Check H REAP Local Switching and ensure the WLAN is enabled for operation.
Without this step, the WLAN does not allow data to be terminated locally at H REAP access points or is not offered at all when the access point is in Standalone mode.
Note: Access points not configured to operate in H REAP mode ignore the H REAP Local Switching setting and all client traffic is tunneled back to the controller.
With the H REAP WLAN setup complete, the access point can then be configured to operate in H REAP mode.
After the access point has discovered and joined the controller, go to the controller web GUI under the Wireless heading and click Detail next to the access point of choice.
By the AP Mode heading, choose H REAP from the drop-down menu in order to change the access point from its default Local Mode operation to function in H REAP mode.
Click Apply. The access point needs to reboot for the mode configuration to take effect.
The access point reboots, rediscovers the controller, and joins the controller again.
Return to the Wireless heading of the controller GUI and select the same access point Detail link, as done before.
By default, the H REAP is not configured to operate on a trunk link. Though the switchport to which it is connected can be set to a trunk link, the access point still communicates with the controller over the native VLAN. If the switchport is a trunk link and it is desired to have the H REAP operate in this mode, VLAN support must be enabled.
Click the H REAP tab. Check VLAN Support.
Based on the configuration of the switchport to which the H REAP is connected, input the Native VLAN ID number of the access point next to the heading with the same name (in this example, VLAN 10).
Click Apply in order to enact the changes.
Because the H REAP resets the configuration of its Ethernet port based on the given configuration parameters, the access point can briefly lose connectivity with the controller. A popup window warns of this possibility. Click OK.
Note: As the popup warning indicates, there is a slight chance the access point will rejoin the controller in the Disabled state. Reselect that access point's Details link from the Wireless heading of the controller. Then select Enable next to Admin Status. Apply the setting and continue with the configuration.
Enter the Detail page of the desired access point, select the H REAP tag again, and click VLAN Mapping in order to configure the 802.1Q tagging per locally switched WLAN.
Set the VLAN per locally switched WLAN on which the client traffic must be terminated.
Note: WLANs not configured to support H REAP Local Switching do not allow the 802.1Q tag to be configured here. The VLAN configuration for these WLANs is set in the global settings of the controller because client data is tunneled back to the controller for termination.
Note: Locally switched WLANs can all share the same VLAN ID or can have discrete assignments. There are no limitations here, provided the assigned VLAN is present at the switchport of the H REAP.
Click Apply in order to save the changes.
WLAN service is disrupted momentarily while the VLAN/WLAN mapping is changed. Click OK to acknowledge this.
The necessary WLANs are created and configured, access points set to operate in H REAP mode, VLAN support enabled, and VLANs configured per locally switched WLAN. Provided DHCP services are available on each VLAN, clients must be able to connect to each WLAN, receive addresses on their respective VLANs, and pass traffic. The H REAP configuration is now complete.
There are a few common scenarios and situations that arise and prevent smooth H REAP configuration and client connectivity. This section provides a few such situations with their suggested remedies.
This can occur for several reasons. Start by checking the following:
Each H REAP needs to be properly IP addressed.
If DHCP is used through the console of the access point, verify that the access point obtains an address.
AP_CLI#show dhcp lease
If static addressing is used through the console of the access point, check to make sure the correct IP addressing is applied.
AP_CLI#show capwap ip config
Ensure the access point has IP connectivity and can ping the controller's management interface.
Once IP addressing is verified, check to make sure the access point can communicate with the controller by pinging the management IP address of the controller. Use the ping command through the console of the access point with this syntax:
AP_CLI#ping <WLC management IP address>
If that is not successful, ensure the upstream network is properly configured and that WAN access back to the corporate network is available. Verify the controller is operational and is not behind any NAT/PAT boundaries. Ensure that UDP ports 5246 and 5247 are open on any intermediary firewalls. Ping from the controller to the access point with the same syntax.
Verify there is CAPWAP connectivity between the access point and controller.
Once IP connectivity between the H REAP and the controller is verified, perform CAPWAP debugs on the controller to confirm CAPWAP messages are communicated across the WAN and to identify related problems. On the controller, first create a MAC filter to limit the scope of the debug output. Use this command in order to limit the output of the subsequent command to a single access point.
AP_CLI#debug mac addr <AP's wired MAC address>
Once set to limit debug output, turn on CAPWAP debugging.
AP_CLI#debug capwap events enable
If no CAPWAP debug messages are seen, ensure the H REAP has at least one method by which a controller can be discovered. If such methods are in place (like DHCP option 43 or DNS), verify they are properly configured. If no other discovery method is in place, ensure the IP address of the controller is entered into the access point through the console CLI.
AP_CLI#capwap ap controller ip address <WLC management IP address>
Check CAPWAP operations on both the controller and the H REAP.
If at least a single controller discovery method is available to the H REAP, verify CAPWAP messages are sent from the access point to the controller. This command is already enabled by default.
AP_CLI#debug capwap client errors
Further information about which controllers the access point communicates with can be seen by the IP addresses of the UDP message it sends. View the source and destination addresses of each packet that traverses the IP stack of the access point.
AP_CLI#debug ip udp
If it appears from the console of the access point that it communicates with a controller, it is possible that it has joined another controller in the cluster. In order to verify if the H REAP is connected to a controller, use this command.
AP_CLI#show capwap reap status
Verify that the access point has joined the correct controller.
If other IP addresses of the controller are handed to the access point during the discovery phase, the H REAP can have joined another controller. Verify the controller IP address made available by the discovery mechanism is correct. Identify the controller to which the access point has joined.
AP_CLI#show capwap reap status
Log into that web GUI of the controller. Ensure all of the IP and MAC addresses of the controllers are entered into the Mobility List of the controller and that they all share the same Mobility Group Name. Then, set the access point's primary, secondary, and tertiary controllers to dictate which controller the access point joins. This is done through the Details link of the access point. If the problem rests with the H REAP joining another controller, this can be greatly eased by using the WCS system-wide access point management capabilities.
Troubleshoot certificate issues if the access point is attempting to join the controller, but fails.
If CAPWAP messages are seen on the controller, but the access point fails to join, this likely is a certificate issue. .
Any configuration commands (either setting or clearing of the configuration) performed through the H REAP CLI return the ERROR!!! Command is disabled message. This can happen for one of two reasons:
H REAP access points that are in the Connected mode will not allow the setting or clearing of any configurations via the console. When the access point is in this state, configurations must be done through the controller interface. If access to configuration commands at the access point is required, ensure the access point is in Standalone mode before attempting to enter any configuration commands.
Once the access point has connected to a controller at any point (even if the H REAP has moved back to Standalone mode), the access point's console will not allow configuration commands until a new password is set. Each H REAP's password needs to be changed. This can only be set through the CLI of the controller to which the access point is connected. This command syntax can be used at the controller to set either an individual access point's console password or the password to all the controller's access points:
(WLC_CLI)>config ap username <user-id> password <passwd> {all | <AP name>}
Note: For an access point that has not had its console passwords set, be aware that this configuration is only sent to the access point at the point the command is entered at the controller. Any access points that subsequently join to this will require the command be entered again.
Even once the access point has both been given a non-default password and the access point is in Standalone mode, the access point will still not allow access to these commands. In order to make changes to the H REAP's configuration, the removal of pre-existing static IP addressing and controller IP address configurations is required. This configuration is called the CAPWAP Private Configuration and will need to be removed before any new access point CLI commands may be input. In order to do this, enter this command:
AP_CLI#clear capwap private-config
Note: Alternatively, the AP can be returned to factory defaults while it is joined to a controller. Click the Clear Config button in the AP's details page under the Wireless heading in the WLC GUI. The AP's configuration is wiped and it is rebooted.
Note: All show and debug commands will continue to work even without a non-default password being set and with the AP in Connected mode.
Only at this point may any CAPWAP configurations be made.
Complete these steps:
Verify that the access point has properly joined the controller, the controller has at least one properly configured (and enabled) WLAN, and ensure the H REAP is in the Enabled state.
On the client's end, verify that the WLAN's SSID is available (at the controller, configuring the WLAN to broadcast its SSID may help this troubleshooting process). Mirror the WLAN's security configuration on the client. Client-side security configurations are where the vast majority of connectivity problems reside.
Ensure clients on locally switched WLANs are properly IP addressed. If DHCP is used, make sure an upstream DHCP server is properly configured and providing addresses to the clients. If static addressing is used, ensure the clients are properly configured for the correct subnet.
In order to further troubleshoot client connectivity issues at the H REAP's console port, enter this command.
AP_CLI#show capwap reap association
In order to further troubleshoot client connectivity issues at the controller and to limit the output of further debugging, use this command.
AP_CLI#debug mac addr <client's MAC address>
In order to debug a client's 802.11 connectivity issues, use this command.
AP_CLI#debug dot11 state enable
Debug a client's 802.1X authentication process and failures with this command.
AP_CLI#debug dot1x events enable
Backend controller/RADIUS messages can be debugged using this command.
AP_CLI#debug aaa events enable
Alternatively, to enable a complete suit of client debug commands, use this command.
AP_CLI#debug client <client's MAC address>
Q. If I configure LAPs at a remote location as H REAPs, can I give those LAPs a primary and secondary controller?
Example: There is a primary controller at site A and a secondary controller at site B.
If the controller at site A fails, the LAP does failover to the controller at site B. If both controllers are unavailable does the LAP fall into H REAP local mode?
A. Yes. First the LAP fails over to its secondary. All WLANs that are locally switched have no changes, and all that are centrally switched just have the traffic go to the new controller. And, if the secondary fails, all WLANs that are marked for local switching (and open/pre-shared key authentication/you are doing AP authenticator) remain up.
Q. How do access points configured in Local mode deal with WLANs configured with H REAP Local Switching?
A. Local mode access points treat these WLANs as normal WLANs. Authentication and data traffic are tunneled back to the WLC. During a WAN link failure this WLAN is completely down and no clients are active on this WLAN until the connection to the WLC is restored.
Q. Can I do web authentication with Local switching?
Yes, you can have an SSID with web-authentication enabled and drop the traffic locally after web-authentication. Web-authentication with Local switching works fine.
Q. Can I use my Guest-Portal on the Controller for an SSID, which is handled locally by the H REAP? If yes, what happens if I lose connectivity to the controller? Do current clients drop immediately?
Yes. Since this WLAN is locally switched, the WLAN is available but no new clients are able to authenticate as the web page is not available. However, the existing clients are not dropped off.


text:
Roasted Garlic Butternut Soup
Total TimePrep: 35 min. Cook: 20 min.
Makes9 servings (2-1/4 quarts)
- 1 whole garlic bulb
- 1 teaspoon olive oil
- 1 medium butternut squash (3 pounds), peeled and cubed
- 1 medium sweet potato, peeled and cubed
- 1 large onion, chopped
- 2 tablespoons butter
- 3-1/4 cups water
- 1 can (14-1/2 ounces) reduced-sodium chicken broth
- 1 teaspoon paprika
- 1/2 teaspoon pepper
- 1/4 teaspoon salt
- 9 tablespoons crumbled blue cheese
- Preheat oven to 425°. Remove papery outer skin from garlic (do not peel or separate cloves). Cut top off garlic bulb. Brush with oil; wrap in heavy-duty foil. Bake 30-35 minutes or until softened. Cool for 10-15 minutes.
- Meanwhile, in a Dutch oven, saute squash, sweet potato and onion in butter until crisp-tender. Add water, broth, paprika, pepper and salt; squeeze softened garlic into pan. Bring to a boil. Reduce heat; cover and simmer 20-25 minutes or until vegetables are tender. Cool slightly.
- In a food processor, process soup in batches until smooth. Return all to pan and heat through. Ladle into bowls; top with blue cheese.
Nutrition Facts1 cup soup with 1 tablespoon blue cheese: 144 calories, 6g fat (3g saturated fat), 13mg cholesterol, 340mg sodium, 21g carbohydrate (6g sugars, 5g fiber), 4g protein. Diabetic Exchanges: 1 starch, 1 fat.
Recommended Video
Nov 26, 2012
Made it for Thanksgiving dinner, have already made it again. The second time, I added 1/2 T of brown sugar to give it just a hint of sweetness...perfecto!
Mar 12, 2012
the flavor is good, but is better as a side soup, vs a main dish
Dec 24, 2011
This is good, but it could use a little something extra. I served it with cornbreaad muffins that had a little cumin in them, and it went well together.
Oct 18, 2011
this is very good soup! I added a little bit of cumin, curry powder, and sugar, plus extra salt and paprika, and a generous splash of sherry. the flavors are delicious but very subtle, so I suggest you pair this with a mild side dish. I had a bold spinach/walnut/apple/blue cheese salad, and it overpowered the soup's flavors. I'll make it again, but it needed those few extra things!

subset: commoncrawl


text:
Press Releases
Hardee's New Loaded Biscuit 'N' Gravy Ups the Ante on a Breakfast Favorite
Apr 19, 2010
Limited-time menu item transforms a classic breakfast side dish into a hearty meal
ST. LOUIS – April 19, 2010 – It's simple math: Two is always greater than one. So how do we make a classic like Hardee's® Biscuit 'N' Gravy even better? Double it up. The new Loaded Biscuit 'N' Gravy starts with a classic Hardee's Made From Scratch™ buttermilk biscuit, which is split with a folded egg and a sausage patty topping each half and the whole thing covered with Hardee's famous sausage gravy. That's down-home.
"After making buttermilk biscuits from scratch for over a quarter of a century, no other fast-food restaurant chain knows biscuits – or sausage gravy – like Hardee's does," said Brad Haley, executive vice president of marketing for Hardee's Food Systems, Inc. "In fact, our Biscuit 'N' Gravy has been one of our best-selling breakfast items for such a long time that we wanted to see if we could give people even more of a good thing by loading it up with eggs and sausage to make it more of a full breakfast. Breakfast lovers looking to fill up on flavor won't be disappointed."
The Loaded Biscuit 'N' Gravy consists of two folded eggs and two sausage patties served open-faced on a freshly baked Made From Scratch™ buttermilk biscuit and covered with a generous serving of hot sausage gravy. It is available at participating Hardee's restaurants for $2.99 or in a small combo for $4.69, including crispy Hash Rounds™ and a beverage. Prices may vary by location.
About Hardee's
Celebrating 50 years in the quick-service industry, Hardee's Food Systems is a wholly owned subsidiary of CKE Restaurants, Inc. (NYSE: CKR) of Carpinteria, Calif. As of the end of fiscal 2010, CKE Restaurants, Inc., through its subsidiaries, had a total of 3,141 franchised, licensed or company-operated restaurants in 42 states and in 14 countries, including 1,224 Carl's Jr. restaurants and 1,905 Hardee's restaurants. For more information, or to find a Hardee's near you, go to www.ckr.com or www.hardees.com. Hardee's social media sites include www.facebook.com/hardees, www.twitter.com/hardees and www.youtube.com/hardees.


text:
Dr. Grumpy: "I need a new iPhone case, one with a belt clip. Mine wore out and broke."
Commission Guy: "I can help you with that. You want one that lights up when you're talking?"
Dr. Grumpy: "No. Don't get me started on that."
Commission Guy: "All right, how about this one. It's on sale!"
Dr. Grumpy: "It's kind of thick... Not sure I need that."
Commission Guy: "It's a great deal, though! Normally $289, this week only $199!"
Dr. Grumpy: "ONLY $199? Uh, no, I just need something to protect it from scratches and stuff, like this $15 one here. Hey, do you have this kind in black? And with a belt clip?"
Commission Guy: "Yeah, but that won't protect your iPhone. You just said your last case broke. You need something sturdier."
Dr. Grumpy: "Maybe, but I'm not paying $199 for an iPhone case."
Commission Guy: "Your phone could get wet or dropped or something. Look at this case as an investment."
Dr. Grumpy: "Okay, I'm taking this one for $15 and going to check out. Thank you."
Commission Guy: "Wait! This $199 case is a great deal! It's bullet proof!"
Dr. Grumpy: "BULLET PROOF?"
Commission Guy: "Well, against a small caliber handgun, I mean. Couldn't you use that in an iPhone case?"
Dr. Grumpy: "I wear my phone on the right side of my belt. So, yes, if I'm worried about someone sneaking up and shooting me in the right hip I suppose it's useful. But I think I'll take my chances with the $15 case."
Commission Guy: "But..."
Dr. Grumpy: "Besides, if someone is shooting at me, the safety of my iPhone is the least of my worries."
I left and went to another store, where I got a cheap case. Upon getting home my curiosity got the best of me, and I looked online. The only bullet proof iPhone case I found was $650, and didn't look anything like what he was trying to sell me.
And then I had these visions of Linda Carter, in a 1977 Wonder Woman outfit, using an iPhone instead of her magic bracelets to deflect bullets while fighting bad guys.


text:
|If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.
|Thread Tools
|Display Modes
Derogatory baby language (and veterans)
Where is Homeland Security?
See below.
Pregnant women: OBs are closing birth canals up to 30% and keeping birth
canals closed when babies get stuck...
It's easy to allow your birth canal to OPEN the "extra" up to 30%.
See the very end of this post.
OPEN LETTER (archived for global access; see below)
Tory Brecht
Quad-City Times
(563) 383-2329
I saw your article about Homeland Security arresting and jailing the doctor
of chiropractic accused of making harrassing telephone calls to the VA...
You quoted Homeland Security Agent Wil Calvey:
"We were looking at the messages and while there were no direct threats, the
language was abusive and derogatory and seemed to be getting worse."
http://www.qctimes.com/internal.php?...&c=2,103 8961
BABIES no doubt use "abusive and derogatory" BABY language as
federally-funded obstetricians close birth canals up to 30% and keep birth
canals closed when babies get stuck.
OBs are lying to cover-up the obvious felony...
See Make birth better: Dan Rather, before you leave CBS...
Homeland Security Agent Wil Calvey told you:
"When you let things go, and people are not punished, they get worse and you
have an increased chance of an incident where someone is injured or killed."
OBs themselves have indicated that closing the birth canal FAR LESS than 30%
can KILL.
Maybe Homeland Security has jurisdiction over obstetrics because Medicare
pays billions per year to hospitals to train recently graduated medical
Don't get me wrong Tori: I'm not being abusive or derogatory here - and I
don't want Agent Calvey to arrest any OBs unless they continue to close
birth canals.
I just want OBs to stop closing birth canals.
Dr. Gastaldo
Tori, I was glad to see you speculate at the very end of your article as to
the REASON the doctor of chiropractic was allegedly harrassing the VA...
"According to federal court records, Tennant filed a lawsuit in 1998
disputing a denial of disability insurance benefits and Supplemental
Security Income. After a two-year legal battle, the U.S. Court of Appeals
Eighth Circuit upheld the denial."
I know this sounds crazy Tori... But what if this veteran was hurt serving
his country and really is disabled - really *does* have a legitimate claim
for disability benefits - and the executive and judicial branches of
government are colluding to deny him those benefits?
Certainly government collusion to deny veterans benefits is not any crazier
than federally-funded OBs closing birth canals up to 30% and KEEPING birth
canals closed when babies get stuck.
THINK ABOUT IT OBs are being allowed to deny BABIES federal benefits...
Or maybe it is LEGAL for OBs to use federal funds to train recently
graduated medical students to deny babies benefit of maximal outlet area at
I don't think so....
The federal government is funding the training of MDs in mass child abuse.
Where is Homeland Secuirty?
PREGNANT WOMEN: It is easy to offer your baby the "extra" up to 30% of
outlet area by simply rolling onto your side as you push your baby out.
JUST BEWA Some OBs and CNMwives let you "try" alternative delivery
positions - but move you back to semisitting or dorsal (close your birth
canal) for
the actual delivery.
ALSO BEWA It is STANDARD PRACTICE for OBs to keep birth canals closed
when babies get stuck - i.e. - OBs are pulling with forceps and vacuums -
birth canals senselessly closed...
Talk to your OB or CNMwife about this today.
This post will be archived for global access within 24 hours in the Google
usenet archive. Search http://groups.google.com for "Derogatory baby
language (and veterans)"
|Thread Tools
|Display Modes
Linear Mode


text:
Founded in 2008, Chalk carries dozens of lines, specializing in modern tailoring with minimalistic accents. The clothes speak for themselves. Kane defines the store as "smart fashion," allowing every client to find something that fits their price point and personal style.
Echoing their mantra of "a smart approach to styling" is the interior of Chalk. Streamlined and white, with touches of a warm ambiance from sweet smelling candles and perfumes, the store is welcoming, making it a nice departure from the somewhat pressures of downtown designer shopping.Both owners are passionate about the use of eco-friendly items whether it be in the store itself or in carrying lines such as 88 Orange, Susan Woo or in accessories like nature inspired glass Tre rings by Casey Kettleson. Adding to its uniformed aesthetic, clothes are displayed by color rather than by brand. This allows the shopper to mix and match styles and designers, rather than buying brand specific pieces. You will notice a lot of black, but don't be fooled. Chalk is far from dull. While the color is understated, the fine attention to detail in each item makes for an interesting and one of a kind garment.
With accolades from numerous Chicago publications, Chalk has made a name for itself on the North Shore as a go-to for fashion lovers who crave distinctive items. Whether it's just stopping in to browse or by special appointment, Chalk employees want customers to leave the store with a sense of confidence in themselves and their purchases.
As we browsed the store with complimentary iced coffee in hand, Kane updated us on the hottest late summer/early fall trends. She also told us that Chalk isn't just for women; men looking to update their wardrobe can also rely on the store's variety of options. Casual chambray button downs, tailored black jeans and broken in sneakers highlight this season's shift from summer to fall.
For women, you will find anything from a Current/Elliot military jacket to a breathtaking red, ruffled chiffon mini skirt by Giambattista Valli. Super comfortable basics await you from brands like Mary-Kate and Ashley Olsen's line The Row. Soft knits and leather leggings lend a downtown vibe to the most suburban dwellers. Throw on a vibrant, standout accessory like a belt from designer Meredith Wendell whose buckles add a touch of color to any outfit and top off your look with a jaunty cap in black or grey by Hache and you'll be ready to hit the streets!
Specifics to look for this season? Paris street style is all the rage, bringing back fur, military jackets, shades of cranberry and electric blue, Current/Elliot soft denim and Rick Owens leather jackets. As for our personal obsessions... Chris Benz' sheer, cream blouse, Blouson Noir's tweed fringed suit and MiH skinny jeans, paired with a pair of simply fabulous suede Balenciaga boots.
Upon leaving the store, we could not help but feel like we just been a part of something unique. Few stores can leave such an impression like that of Chalk and there's no doubt that we'll be back for another high-fashion fix!
Photo Credit: Ellen Hager and Aimee Rancer
Chalk Boutique
2611 Prairie Avenue
Evanston, IL
Phone: 847.424.0011
Email: [email protected]
Hours: Monday—Saturday 10 to 5


text:
This sport has been so good to me! I still love to swim and compete. At this point in my life, I get even more satisfaction giving back to the sport by coaching high school swimmers in my community. This blog will include workouts that i do when time permits
I may also from time to time include some observations from the deck as a coach of my swimmers. Feel free to share any thoughts that you have!


text:
William Gibson
Jump to navigation Jump to search
William Ford Gibson (born 17 March 1948) is an American-Canadian writer who has been called the "noir prophet" of the cyberpunk subgenre of science fiction. Gibson coined the term "cyberspace" in his short story "Burning Chrome" and later popularized the concept in his debut novel, Neuromancer (1984).
- On the most basic level, computers in my books are simply a metaphor for human memory: I'm interested in the hows and whys of memory, the ways it defines who and what we are, in how easily memory is subject to revision. When I was writing Neuromancer, it was wonderful to be able to tie a lot of these interests into the computer metaphor. It wasn't until I could finally afford a computer of my own that I found out there's a drive mechanism inside — this little thing that spins around. I'd been expecting an exotic crystalline thing, a cyberspace deck or something, and what I got was a little piece of a Victorian engine that made noises like a scratchy old record player. That noise took away some of the mystique for me; it made computers less sexy. My ignorance had allowed me to romanticize them.
- Interview with Larry McCaffery in Storming the Reality Studio : A Casebook of Cyberpunk and Postmodern Science Fiction, Duke University Press (December 1991)
- The future is already here — it's just not very evenly distributed.
- He is reported to have first said this in an interview on Fresh Air, NPR (31 August 1993) {unverified}, he repeated it, prefacing it with "As I've said many times…" in "The Science in Science Fiction" on Talk of the Nation, NPR (30 November 1999, Timecode 11:55). See also The future has arrived... - Quote Investigator.
- The NET is a waste of time, and that's exactly what's right about it.
- Name of an article he wrote for New York Times Magazine (14 July 1996)
- In 1977, facing first-time parenthood and an absolute lack of enthusiasm for anything like "career," I found myself dusting off my twelve-year-old's interest in science fiction. Simultaneously, weird noises were being heard from New York and London. I took Punk to be the detonation of some slow-fused projectile buried deep in society's flank a decade earlier, and I took it to be, somehow, a sign. And I began, then, to write.
And have been, ever since.
- The future is not google-able.
- Comments at A Clean Well-Lighted Place for Books, San Francisco, California (5 February 2004)
- There is always a point at which the terrorist ceases to manipulate the media gestalt. A point at which the violence may well escalate, but beyond which the terrorist has become symptomatic of the media gestalt itself. Terrorism as we ordinarily understand it is innately media-related.
- Loss is not without its curious advantages for the artist. Major traumatic breaks are pretty common in the biographies of artists I respect.
- Interview in The New York Times Magazine (19 August 2007)
- The most common human act that writing a novel resembles is lying. The working novelist lies daily, very complexly, and at great length. If not for our excessive vanity and our over-active imaginations, novelists might be unusually difficult to deceive.
- Naps are essential to my process. Not dreams, but that state adjacent to sleep, the mind on waking.
- Interview in Paris Review Summer 2011
- This perpetual toggling between nothing being new, under the sun, and everything having very recently changed, absolutely, is perhaps the central driving tension of my work.
- At the Booksmith, reading from Distrust That Particular Flavor. (19 January 2012).
- We no longer grow the full beef of bohemia, It's all veal now.
- Intelligence Squared on 'Zero History' with Cory Doctorow (5th October 2010)
Johnny Mnemonic (1981)[edit]
- Page numbers from the reprint in Joe Haldeman ed. Nebula Award Stories 17, paperback edition published by Ace. Story originally published in Omni magazine.
- We're an information economy. They teach you that in school. What they don't tell you is that it's impossible to move, to live, to operate at any level without leaving traces, bits, seemingly meaningless fragments of personal information. Fragments that can be retrieved, amplified...
- "As broker, I'm usually very careful as to sources."
"You buy only from those who steal the best. Got it." (p. 91)
- "You have no idea," said Ralfi, suddenly sounding very tired, "the depths of shit you have just gotten yourself into." (p. 92)
Burning Chrome (1982)[edit]
- The street finds its own uses for things.
Neuromancer (1984)[edit]
- The sky above the port was the color of television, tuned to a dead channel.
- They damaged his nervous system with a wartime Russian mycotoxin. Strapped to a bed in a Memphis hotel, his talent burning out micron by micron, he hallucinated for thirty hours. The damage was minute, subtle, and utterly effective. For Case, who'd lived for the bodiless exultation of cyberspace, it was the Fall.
- Night City was like a deranged experiment in social Darwinism, designed by a bored researcher who kept one thumb permanently on the fast-forward button. Stop hustling and you sank without a trace, but move a little too swiftly and you'd break the fragile surface tension of the black market; either way, you were gone, with nothing left of you but some vague memory in the mind of a fixture like Ratz, though heart or lungs or kidneys might survive in the service of some stranger with New Yen for the clinic tanks.
- They'd left the place littered with the abstract white forms of the foam packing units, with crumpled plastic film and hundreds of tiny foam beads. The Ono-Sendai; next year's most expensive Hosaka computer; a Sony monitor; a dozen disks of corporate-grade ice; a Braun coffee maker.
- "Hey," he'd said, "it's me. Case."
The old eyes regarding him out of their dark webs of wrinkled flesh.
"Ah," Ratz had said, at last, "the artiste."
The bartender shrugged. "I came back."
The man shook his massive, stubbled head. "Night City is not a place one returns to, artiste," he said, swabbing the bar in front of Case with a filthy cloth, the pink manipulator whining.
- Wintermute was hive mind, decision maker, effecting change in the world outside. Neuromancer was personality. Neuromancer was immortality. Marie-France must have built something into Wintermute, the compulsion that had driven the thing to free itself, to unite with Neuromancer.
- The cutting of Sense/Net's ice took a total of nine days. "I said a week," Armitage said, unable to conceal his satisfaction when Case showed him his plan for the run. "You took your own good time." "Balls," Case said, smiling at the screen. "That's good work, Armitage." "Yes," Armitage admitted, "but don't let it go to your head. Compared to what you'll eventually be up against, this is an arcade toy."
- A year here and he still dreamed of cyberspace, hope fading nightly. All the speed he took, all the turns he'd taken and the corners he'd cut in Night City, and he'd still see the matrix in his sleep, bright lattices of logic unfolding across that colorless void… The Sprawl was a long strange way home over the Pacific now, and he was no console man, no cyberspace cowboy. Just another hustler, trying to make it through. But the dreams came on in the Japanese night like livewire voodoo, and he'd cry for it, cry in his sleep, and wake alone in the dark, curled in his capsule in some coffin hotel, his hands clawed into the bedslab, temperfoam bunched between his fingers, trying to reach the console that wasn't there.
- Cyberspace. A consensual hallucination experienced daily by billions of legitimate operators, in every nation, by children being taught mathematical concepts… A graphic representation of data abstracted from banks of every computer in the human system. Unthinkable complexity. Lines of light ranged in the nonspace of the mind, clusters and constellations of data. Like city lights, receding...
- Don' 'stand you, mon, but we mus' move by Jah Love, each one
- "Hate," Case said. "Who do I hate? You tell me." "Who do you love?" the Finn's voice asked.
- "Dix," Case said, "I wanna have a look at an AI in Berne. Can you think of any reason not to?"
"Not unless you got a morbid fear of death, no."
- The drug hit him like an express train, a white-hot column of light mounting his spine from the region of his prostate, illuminating the sutures of his skull with x-rays of short-circuited sexual energy. His teeth sang in their individual sockets like tuning forks, each one pitch-perfect and clear as ethanol. His bones, beneath the hazy envelope of flesh, were chromed and polished, the joints lubricated with a film of silicone. Sandstorms raged across the scoured floor of his skull, generating waves of high thin static that broke behind his eyes, spheres of purest crystal, expanding...The anger was expanding, relentless, exponential, riding out behind the betaphenethylamine rush like a carrier wave, a seismic fluid, rich and corrosive.
- The lane to the land of the dead. Where you are, my friend. Marie-France, my lady, she prepared this road, but her lord choked her off before I could read the book of her days. Neuro from the nerves, the silver paths. Romancer. Necromancer. I call up the dead. But no, my friend," and the boy did a little dance, brown feet printing the sand, "I am the dead, and their land." He laughed. A gull cried, "Stay. If your woman is a ghost, she doesn't know it. Neither will you."
- He came in steep, fueled by self-loathing. When the Kuang program met the first of the defenders, scattering the leaves of light, he felt the shark thing lose a degree of substantiality, the fabric of information loosening. And then — old alchemy of the brain and its vast pharmacy — his hate flowed into his hands. In the instant before he drove Kuang's sting through the base of the first tower, he attained a level of proficiency exceeding anything he'd known or imagined. Beyond ego, beyond personality, beyond awareness, he moved, Kuang moving with him, evading his attackers with an ancient dance, Hideo's dance, grace of the mind-body interface granted him, in that second, by the clarity and singleness of his wish to die.
- He found work.
He found a girl who called herself Michael.
- Somewhere, very close, the laugh that wasn't laughter.
He never saw Molly again.
About Neuromancer[edit]
- So it's entirely fair to say, and I've said it before, that the way Neuromancer-the-novel "looks" was influenced in large part by some of the artwork I saw in 'Heavy Metal'. I assume that this must also be true of John Carpenter's 'Escape from New York', Ridley Scott's 'Blade Runner'", and all other artefacts of the style sometimes dubbed 'cyberpunk'. Those French guys, they got their end in early.
Count Zero (1986)[edit]
- Because he had a good agent, he had a good contract. Because he had a good contract, he was in Singapore an hour after the explosion. Most of him, anyway.
- On Turner, in Ch. 1
- In Heathrow a vast chunk of memory detached itself from a blank bowl of airport sky and fell on him. He vomited into a blue plastic container without breaking stride. When he arrived at the counter at the end of corridor, he changed his ticket.
- Ch. 1, Turner begins to recall his past.
- And, for an instant, she stared directly into those soft blue eyes and knew, with an instinctive mammalian certainty, that the exceedingly rich were no longer even remotely human.
- Ch. 2, Marly's sensory link conversation interview with Herr Virek.
- The stick-on holograms had actually had some effect on Bobby, because religion was now something he felt he'd considered and put aside. Basically, the way he figured it, there were just some people around who needed that shit, and he guessed there always had been, but he wasn't one of them, so he didn't.
- Ch. 6
- The Gothick girl regarded Bobby with mild interest but no flash of human recognition whatever, as though she were seeing an ad for a product she'd heard of but had no intention of buying.
- Ch. 6
- Stim was a medium she ordinarily avoided, something in her personality conflicting with the required degree of passivity.
- On Marly Krushkhova, in Ch. 23
- "Honey," Jammer said, "you'll learn. Some things you teach yourself to remember to forget."
- Spoken to Jackie, Ch. 28
- "As I luxuriate in the discovery that I am no special sponge for sorrow, but merely another fallible animal in this stone maze of a city, I come simultaneously to see that I am the focus of some vast device fueled by an obscure desire."
- On Marly Krushkhova
Mona Lisa Overdrive (1988)[edit]
- He'd grown up in white Jersey stringtowns where nobody knew shit about anything and hated anybody who did.
- Ch. 2
- Viewing them induced a mild but not unpleasant vertigo, one of the rare times she was able to directly grasp the fact of her fame.
- Ch. 12
- That's interesting in itself, because it shows you how adept they were at obscurity. They used their money to keep themselves out of the news.
- Ch. 12
- Have you ever considered the relationship of clinical paranoia to the phenomenon of religious conversion?
- Ch. 13
- Found this picture of Angie laughing in a restaurant with some other people, everybody pretty but beyond that it was like they had this glow, not really in the photograph but it was there anyway, something you feel. Look, she said to Lanette, showing her the picture, they got this glow.
It's called money, Lanette said.
- Ch. 19
- "You were hurt," Kumiko said, looking at the scar.
Sally looked down. "Yeah."
"Why don't you have it removed?"
"Sometimes it's good to remember."
"Being hurt?"
"Being stupid."
- Ch. 22
- Your saving grace, Danielle, is that you make the rest of your kind look vaguely human.
- Ch. 25
No Maps for These Territories (2000)[edit]
- I think the last time...the last time I had one of those "CNN moments," where I was slammed right up against the windshield of — of the present — would have been flipping on the television one day, and seeing that Federal Building in Oklahoma City lying there in its own … crater, and listening to a little bit of the audio, and … and getting the idea that something, something bad had happened in Middle America. And I had … some … very, very deep within me, something seemed to say, "Everything is different from now on. Something, something very fundamental has changed, here." … Whenever something like this happens, and I have one of these moments, it ups the ante on being a science-fiction writer. It changes … it changes the nature of the game.
- Another example — maybe a better one, in a way — was when it was confirmed that Michael Jackson was going to marry Elvis Presley's daughter. [loud, game-show buzzer noise] A good friend of mine in the States faxed me, and he simply … he said, "This makes your job more difficult." And I knew exactly, I knew exactly what he meant. 'Cos something … a scenario that seemed to belong to the universe of the late Terry Southern, was suddenly, suddenly real. It's that truth-is-stranger-than-fiction factor keeps getting jacked up on us on a fairly regular, maybe even exponential, basis. I think that's something peculiar to our time. I don't think our grandparents had to live with that.
- I'd buy him a drink, but I don't know if I'd loan him any money.
- When asked what he would say about the man who wrote Neuromancer.
- I think of Neuromancer as being, in a good sense, an adolescent book. It's a young man's book. It was written very young-man's-book. It was written by a man who was not very young, when he wrote it, but who was sufficiently immature.
- It's a world where there aren't families. It's the world of a young person going out into the wilderness, cities, and sort of in a way creating a family. You know, it's kind of like... it's not that it's a "goth book," but it's kind of rather the same stuff that makes kids be goths.
- About Neuromancer
- It had much more to do with my wanting to be with hippy girls and have lots of hashish than it did with my sympathy for the plight of the North Vietnamese people under US imperialism. Much more, much more to do with hippy girls and hashish.
- On dodging the draft and moving to Toronto
- Consequently, when I got to Toronto, much to my chagrin, I really, really couldn't handle hanging out with the American draft dodgers. There was too much clinical depression. Too much suicide. Too much hardcore substance abuse. They were a traumatized lot, those boys. And I just felt frivolous.
- The straight world didn't end. The straight world and the other world had bled into one another and produced the world that we live in today.
- Drugs were absolutely central to that experience, but they weren't essential. I only know that in retrospect. At the time I'm sure I would have said that they were.
- All any drug amounts to is tweaking the incoming data. You have to be incredibly self-centered or pathetic to be satisfied with simply tweaking the incoming data.
- When did you ever go to a drug dealer, and the drug dealer said, "you know, you should come back tomorrow, this is not very pure." It doesn't happen.
- Acceptance. Acceptance of the impermanence of being. And acceptance of the imperfect nature of being, or possibly the perfect nature of being, depending on how one looks at it. Acceptance that this is not a rehearsal. That this is it.
- When asked what will save humanity.
- I think of religions as franchise operations. Like chicken franchise operations. But that doesn't mean there's no chicken, right?
- Referring to his belief that it's possible for religions to help people.
- Seated each afternoon in the darkened screening room, Halliday came to recognize the targeted numerals of the Academy leader as sigils preceding the dream state of a film.
- A sentence that he worked on for years earlier in his career, which eventually went nowhere. Troubled by inexperience in "actually getting the characters to move," he spent so much time on it that he can still remember every word more than 20 years later.
- I became so frustrated with my inability to physically move the characters through the imaginary narrative space, that I actually developed an early form of imaginary VR technology that sort of covered my ass … all they had to do was switch tapes and be in a different place, and I was spared the embarrassment of demonstrating that I didn't know how to get them up and down the stairs.
- All I knew about the word "cyberspace" when I coined it, was that it seemed like an effective buzzword. It seemed evocative and essentially meaningless. It was suggestive of something, but had no real semantic meaning, even for me, as I saw it emerge on the page.
- It will bring about the extinction of the nation-state as we know it... I think it will be as big a deal as the creation of cities.
- Referring to the Internet
- I didn't imagine that art girls in the Midwest would be flashing their tits in cyberspace...but I'm glad that they're doing it.
- Asked whether the Internet is how he imagined it would be
All Tomorrow's Parties (2003)[edit]
- The man steps past them, his cheeks seamed vertically in deep parentheses, as though it has been his habit frequently to smile. They do not see him smile.
The Tao, he reminds himself, is older than God.
- Ch. 4 : Formal Absences of Precious Things, p. 20
- The past is past, the future unformed. There is only the moment, and that is where he prefers to be.
- Ch. 4 : Formal Absences of Precious Things, p. 21
- They sat around accessing media all day and talking about it, and nothing ever seemed to get done.
- Ch. 7 : Sharehouse, p. 33
- If Skinner couldn't tell Fontaine a story about something, Fontaine would make up his own story, read function in the shape of something, read use in the way it was worn down. It seemed to comfort him.
Everything to Fontaine, had a story. Each object, each fragment comprising the built world. A chorus of voices, the past alive in everything, that sea upon which the present tossed and rode. When he'd built Skinner's funicular, the elevator that crawled like a small cable car up the angled iron of the tower, when they old man's hip had gotten too bad to allow him to easily climb, Fontaine had a story about the derivation of each piece. He wove their stories together, applied electricity: the thing rose, clicking, to the hatch in the floor of Skinner's room.
- Ch. 38 : Vincent Black Lightning, p. 191
Spook Country (2007)[edit]
- The old man reminded Tito of those ghost-signs, fading high on the windowless sides of blackened buildings, spelling out the names of products made meaningless by time.
- If Tito were to see one of those announcing the very latest, the most recent and terrible news, yet could know that it had always been there, fading, through every kind of weather, unnoticed until today, that might feel something like meeting the old man in Washington Square, beside the concrete chess tables, and carefully passing him an iPod, beneath a folded newspaper.…
- Sensing an immense patience, and power, Tito imagined that this old man, for reasons of his own, disguised himself as a revenant from Lower Manhattan's past. Each time the old man received another iPod, accepting it the way an ancient and sagacious ape might accept a piece of some not particularly interesting fruit, Tito half-expected him to crack its virginal white case like a nut, and then to draw forth something utterly peculiar, utterly dire, and somehow terrible in its contemporaneity.
- Ch. 2, Ants in the Water
- Organized religion, he saw, back in the day, had been purely a signal-to-noise proposition, at once the medium and the message, a one-channel universe. For Europe, that channel was Christian, and broadcasting from Rome, but nothing could be broadcast faster than a man could travel on horseback. There was a hierarchy in place, and a highly organized methodology of top-down signal dissemination, but the time lag enforced by tech-lack imposed a near-disastrous ratio, the noise of heresy constantly threatening to overwhelm the signal.
- Ch. 23, Two Moors, p. 117
Agency (2020)[edit]
- "You haven't read the nondisclosure agreement?"
"More clauses than I'm used to."
- Ch. 1, The Unboxing
- "He's a criminal?"
"Financial services," Eunice said, "but on the street side."
- Ch. 17, MIG
- "Before you diagnose yourself with depression or low self-esteem, first make sure that you are not, in fact, just surrounded by assholes." — thought to be Gibson's words as a result of Twitter attribution decay, despite repeated disavowals. [2] [3] [4] [5]. The source, according to Gibson, is Steven Winterburn [6] [7]. However, Steven Winterburn is NOT the original creator of that quote. The original quote is the creation of Twitter account holder "@debihope" [8]. See research by quoteinvestigator [9].
External links[edit]
- WilliamGibsonbooks.com – personal website
- Twitter feed
- Works by or about Works by or about William Gibson in libraries (WorldCat catalog)
- Profile at IMDb
- William Gibson at the Internet Speculative Fiction Database
- Project Cyberpunk's biography and links
- Bibliography of Works by William Gibson at Centre for Language and Literature, at Athabasca University
- William Gibson Aleph
- Synaptic Response
- Collection of interviews with William Gibson.


text:
Strawberry Mascarpone Crepes
Total TimePrep: 45 min. + standing Cook: 20 min.
Makes8 crepes
- 3 eggs
- 3/4 cup plus 2 tablespoons milk
- 3/4 cup all-purpose flour
- 5 teaspoons butter, melted
- 1 tablespoon sugar
- 1 teaspoon vanilla extract
- 1/4 teaspoon salt
- 1 cup (8 ounces) Mascarpone cheese
- 2 tablespoons confectioners' sugar
- 3 to 4 teaspoons minced fresh basil
- 1 teaspoon lemon juice
- 1-1/2 cups sliced fresh strawberries
- 2 cups sliced fresh strawberries
- 1/2 cup sugar
- 2 tablespoons orange juice
- 1 teaspoon strawberry or vanilla extract
- Dash salt
- 4 teaspoons butter, divided
- In a blender, combine the batter ingredients; cover and process until smooth. Cover and refrigerate for 1 hour.
- Meanwhile, for filling, in a small bowl, combine the cheese, confectioners' sugar, basil and lemon juice. Gently fold in strawberries. Cover and refrigerate for at least 30 minutes.
- For topping, in a small bowl, combine the strawberries, sugar, orange juice, extract and salt. Let stand for 30 minutes.
- Melt 1 teaspoon butter in an 8-in. nonstick skillet over medium heat; pour about 1/4 cup batter into the center of skillet. Lift and tilt pan to coat bottom evenly. Cook until top appears dry; turn and cook 15-20 seconds longer. Remove to a wire rack. Repeat with remaining batter, greasing skillet as needed. When cool, stack crepes with waxed paper or paper towels in between.
- Spoon filling over crepes; roll up. Serve with strawberry topping.
Nutrition Facts1 each: 334 calories, 20g fat (11g saturated fat), 129mg cholesterol, 175mg sodium, 32g carbohydrate (21g sugars, 2g fiber), 7g protein.
Recommended Video
Aug 4, 2015
These are a frequently requested weekend breakfast meal! I did not add the entire amount of basil and often leave it out completely. In a pinch if I haven't gotten to the grocery, I use a bar of cream cheese instead of Mascarpone cheese. I did not have luck prepping the filling ahead of time, but the topping worked fine to make ahead. Thank you for sharing the recipe!
Apr 7, 2014
This was my first time making crepes and they turned out awesome!!!! My kids loved them and they weren't as difficult as I had thought. Next time, I will try to prep the components the night before as another reviewer mentioned and see if they still turn out. I also will leave the basil out as it didn't really do much for the crepes and they would have been just as delicious without it.
May 25, 2012
Delicious nothing more to say
May 28, 2011
I made these for Mother's Day & it was a big hit. After I mixed together the creams it was a little thick so I added some milk to thin it out and it came out great. I didn't add the basil. Top with strawberries & whipped cream. If any left over just put in the micro for 20-30 seconds, just to heat crepe not the cream and they come out just like you made them fresh. Great recipe to impress your family or friends. Try it, you'll like it.
Feb 13, 2011
I too left out the basil, and made these this morning. Easy to do and the taste was great. I think you could even prepare everything the night before and leave in the refrigerator and then quickly make the next morning so you lave less prep time. Definitely worth trying if you like the taste of cream cheese and strawberries.
Apr 16, 2010
We made it as is, and next time I make it I will definitely eliminate the basil as well. Way to strong. But delicious otherwise!
Feb 14, 2010
These were delicious and easy! I have never made crepes before and they came out perfectly. The only change I made was to eliminate the basil.
Jun 7, 2008
Instead of regular sugar, I used SPLENDA and it turned out wonderfully! Not to mention, it saved A LOT on calories!


text:
DescriptionSwift 3, the newest version of Apple's official coding language, has arrived in the wake of iOS 10, which means it's time for developers to catch up by learning Swift 3 now! In this course, you'll dive into all the updated Swift syntax while reaffirming general programming concepts. Using hands-on demos and examples, you'll learn Swift by using Swift, and get ready to start building apps for iOS 10.
Details & Requirements


text:
New Canaan forecast: Setting the table for a nice Thanksgiving
Today promises to be a pleasant prelude to Thanksgiving, with sunny skies and temperatures rising to the low-50s.
In addition to clear skies across southwestern Connecticut, the National Weather Service predicts there will be a light northeast wind 6 to 8 mph.
Tonight will be mostly clear, with a low temperature in the mid-30s and a northeast wind 3 to 7 mph.
Tomorrow, Thanksgiving Day, also will be sunny, with a high temperature in the mid-50s. Nighttime will be mostly clear, with a low temperature in the mid-30s.
Friday should be sunny again, with the temperature rising to the mid-50s. There is a slight chance of showers Friday night, mainly after 11 p.m., as clouds move in the temperature dips to a low in the upper-30s.
Saturday is expected to be mostly cloudy, with a high temperature in the upper-40s. Saturday night will be partly cloudy, with a low around 30 degrees.
The outlook for Sunday, according to the weather service, is mostly sunny and temperatures in the mid-40s.


text:
The perfect suspect by Vincent Varjavandi(link is external) - Double Bay, N.S.W.: Longueville Media, 2006. 367 p. ; 23 cm.
tags: Crime [Our New Books - LibraryThing(link is external)]
My review of this debut book from a Sydney based author has just been published
Dr Tom Hackett had the perfect life - young, successful and now with a dream job working for a year in New Orleans. All that changes when his wife is murdered there, her body mutilated, the victim of a seemingly random attack.
Desperate to leave those memories behind, he returns home to Australia and accepts a job in Sanctuary, an idyllic resort far from the dark shadows of old New Orleans. But there is no sanctuary from his past, and when a spate of gruesome murders hit the sleepy town, Tom suddenly finds himself the prime suspect - because all of the victims are women he knows, and all are killed with an unmistakable similarity to his wife.
Plunged into a deadly game of cat and mouse with a ruthless assassin, only Jack Maguire, a disgraced homicide Detective with his own demons to battle, seems willing to help. But with Tom's life on the line, can he afford to trust anyone?
With the police and the killer closing in, Tom must uncover Sanctuary's chlling secret, or he will remain the perfect suspect.


text:
Freeport Library temporarily closed
The Freeport Public Library will be closed for the next two weeks while the carpet is being replaced.
The library�s bookmobile will be parked in front of the Freeport Public Library to provide service to anyone needing library books, videos or audio materials. The bookmobile will be available from 9 am. to 5 p.m. Tuesday through Saturday. Regularly scheduled children�s story time programs will be held at the picnic tables beside the library.
Unfortunately, the telephone lines do not extend to the bookmobile, so calls need to be directed to the DeFuniak Springs library at 892-3624 or the Coastal Branch Library at 267-2809.
Sandestin Wine Festival named �Best Annual Event� in Destin area
Sandestin Golf and Beach Resort Wine Festival has been named the �Best Annual Event� in the area by Destin Magazine.
Now in its 27th year, the Sandestin Wine Festival is the most established and continuously running wine festival on the Emerald Coast.
�The Sandestin Wine Festival is one of the most treasured traditions in the area and we are thrilled to receive this recognition,� said Lanier Motes, special events manager for the Village of Baytowne Wharf. �Each year we strive to bring attendees exclusive experiences and this year�s festival will be the best to date.�
The 2013 festival, April 18�21, will feature a wide range of experiences from participating in auctions for rare and distinctive wines to unique culinary demonstrations.
AACFCU donates to Alaqua Animal Rescue
Army Aviation Center Federal Credit Union employees recently donated food, cleaning supplies and other items to the Alaqua Animal Rescue after a company-wide donation drive to help animal shelters in local communities of AACFCU service areas. On two separate days in September, employees donated items in exchange for wearing jeans to work.


text:
Results tagged ' Cloudbreak Group '
Hurricane Sandy relief effort continues
The Yankees in conjunction with the Cloudbreak Group will donate 20 percent of all sales at http://www.nyyankeesfragrance.com during November and December to the American Red Cross for Hurricane Sandy relief efforts. A minimum guarantee of $10,000 will be offered by the Cloudbreak Group, in addition to the dedicated portion made from all sales on the website during the aforementioned months.
"We have had an overwhelming response since the launch of the New York Yankees fragrance collection and are pleased that our loyal fans in the Tri-State area have embraced these products," Cloudbreak Group chief executive officer Thomas Butkiewicz said. "As a member of the Yankees family, we recognize the needs of these individuals during this difficult time and are proud to help support them."
Michael J. Tusiani, Yankees senior vice president of corporate sales and sponsorships, said, "We are very thankful to the Cloudbreak Group and proud of our partner for supporting the Hurricane Sandy relief efforts through its commitment to the American Red Cross."
The motion is part of an organization-wide commitment in helping to rebuild the lives of those who have suffered great losses in the wake of Hurricane Sandy. The Yankees have donated $500,000 to the American Red Cross in support of relief efforts associated with the storm.
In addition to helping the Red Cross, Yankee Stadium's Gate 2 entrance was recently converted into a collection hub in which non-perishable food and household items were donated by the public for those affected. The Yankees have continued to deliver and distribute these items to those in need through various other local charities.
"New York Yankees" and "New York Yankees for Her" both helped usher in the 2012 baseball season by officially launching in April. Originally available exclusively at Yankee Stadium and select department stores, the fragrances have expanded to department stores in multiple international markets. Fans can purchase these and other items and help support the Hurricane Sandy relief efforts by visiting http://www.nyyankeesfragrance.com.