Looking for HELP!

Just let me know if you have any problem related to my posts -- twitter: @ahsantasneem

This is default featured post 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured post 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured post 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured post 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

Monday 11 October 2010

Multicast Stream – Tandberg MXP 990

Make sure that the PC is connected to the same LAN (or multi-cast enabled WAN) as the codec that is to be streaming

Note: The entire configuration related to my IP settings are erased or replaced with ‘X’. Please let me know if you face any problem, and keep following @ahsantasneem for more

Step 1: Static Public IP assignment, entering in all the IP fields for address, subnet mask, and gateway and DNS.




Step 2: Go to Endpoint Confiuration -> Streaming



Address: is defined as the IP-address of a streaming client, streaming server or a multicast address. Giving an address in the range 224.0.0.1-239.255.255.255 will broadcast the stream to any host that has joined the specified multicast group. Specifying normal broadcast address 255.255.255.255 will broadcast to any members on the LAN.

Address Port: If several codecs are streaming to the same IP-address, different ports have to be used in order for the client to know which stream to receive. In this case 22232

Source -> Auto: Enables streaming of both local and far end video. Selection of which site to be streamed is done using voice switching (the site that speaks is streamed).

Streaming Password : Set password so that only participants entering correct password will be able to view the streaming session. Entering a password will prevent unauthorized people from accessing the streaming session





Step 3: Click -> Overview -> Streaming and press the link “Start Streaming” to start the stream.

A new webpage is opened with the streaming view displayed within the page. You can also open your web-browser directly to the streaming page by entering this URL into the browser(In this case): http://124.x.x.x/stream.sdp where 124.x.x.x would be the IP of your streaming device (Tandberg mxp 990). If a streaming client is successfully installed on the computer, a window will start up and soon show the incoming streamed information as shown below:




Step 4: To receive the stream directly from within QuickTime Player, launch QuickTime
player, and under the File Menu select ‘Open URL’ and enter http://124.x.x.x/stream.sdp where 124.x.x.x would be the IP of your codec.

SDP file
When streaming, the codec will generate a SDP file 'stream.sdp' which can be retrieved through the codecs web-interface (by http). This file describes what type of media is used (G.711 / H.261) and which (multicast or unicast) address the streaming is sent to. The clients (QuickTime and RealPlayer) use this information to listen for the stream.











Step 5: To end the streaming session, just press the “Disconnect Call” button on remote control or click the ‘Stop Streaming’ icon on the web page provided the ‘Allow Remote Start’ is set to on.



Note: That just closing the web application will not end the streaming session, as other codec’s still might be able to receive the streamed information.

Supported Streaming clients
Cisco IP/TV, QuickTime version 4 or greater, RealPlayer version 7 and VIC
Cisco IP/TV http://www.cisco.com
QuickTime version 42 or greater http://quicktime.apple.com
VIC http://www-mice.cs.ucl.ac.uk/multimedia/software/vic/
RealPlayer7 or greater http://www.real.com


Thursday 7 October 2010

New Facebook 'Groups' Designed to Completely Change the Way You Use Facebook

Facebook has just revealed a new version of Groups at its live press conference in Palo Alto, California. Facebook Groups are a shared space where members can participate in communal activities like group chat, e-mail lists, document sharing and group photo-tagging.
The new Groups product was built from the ground up; Facebook Founder and CEO Mark Zuckerberg says Groups is an entirely new product that only shares the name in common with the old Groups functionality. The old Groups will continue to remain in place, but moving forward members will only be able to create new Groups.
Groups are closed by default (but can be secret or open) and are designed to be spaces where small groups of friends share information, with each group controlled by the entirety of its members — an important new direction for Facebook. The group chat feature is just as it sounds; members can participate in back-and-forth IM conversations with everyone in the group at the same time.
Once you start participating in Groups, the most-viewed ones will automatically live in the left-hand navigation of the page for easier access.
Facebook has also released a mobile interface and an Open Graph API for Groups, which means that soon Facebook Groups will be accessible in all imaginable capacities.
With everyone in control, Groups will function much differently than before. Facebook asserts that social norms will govern activity. Ultimately, the company believes the new Groups will fundamentally change the way you use Facebook and give you more control over the distribution of your messages.
From our initial tests, we can assert that Groups is, as Zuckerberg promises, something “so simple that everyone on the site will want to interact with it.” And, by design, everyone will use it.
As Facebook clearly stated during the press event, its goals are to map all real-world groups, to ensure that everyone participates and to build something useful in lots of contexts. What this really means is that Facebook wants to fully understand member relationships (an extension of its Open Graph undertaking), and that the company will use your behavior in Groups to better understand these relationships.

Wednesday 6 October 2010

Configuring Cisco Secure ACS for Windows PEAP-MS-CHAPv2 - [Part 2]

Configure the Wireless Network Connection

Complete these steps:
  1. Log off and then log on by using the WirelessUser account in the wirelessdemo.local domain.
  2. Choose Start > Control Panel, double-click Network Connections, and then right-click Wireless Network Connection.
  3. Click Properties, go to the Wireless Networks tab, and ensure that the Use Windows to configure my wireless network settingsis checked.
    peap-acs40-win2003-81.gif
  4. Click Add.
  5. Under the Association tab, type Employee in the Network name (SSID) field.
  6. Select WPA for the Network Authentication and ensure that Data Encryption is set to TKIP.

    /image/gif/paws/72013/peap-acs40-win2003-72.gif
  7. Go to the Authentication tab.
  8. Validate that EAP type is configured to use Protected EAP (PEAP). If it is not, select it from the drop-down menu.
  9. If you want the machine to be authenticated prior to login (which allows login scripts or group policy pushes to be applied) checkAuthenticate as computer when computer information is available.
    peap-acs40-win2003-83.gif
  10. Click Properties.
  11. As PEAP involves authentication of Server by the client ensure that Validate server certificate is checked. Also, make sure the CA that issued the ACS certificate is checked under the Trusted Root Certification Authorities menu.
  12. Choose Secured password (EAP-MSCHAP v2) under Authentication Method as it is used for inner authentication.
    peap-acs40-win2003-84.gif
  13. Make sure the Enable Fast Reconnect check box is checked. Then, click OK three times.
    Step - x : Select the option Configure and uncheck the option present there if you want to enter the user and password manually, and ignore the Step - x if you are already logged in with the correct user and password.
  14. Right-click the wireless network connection icon in systray and then click View Available Wireless Networks.
  15. Click the Employee wireless network and click Connect.
    peap-acs40-win2003-85.gif
    These screen shots indicate if the connection completes successfully.
    /image/gif/paws/72013/peap-acs40-win2003-86.gif
    peap-acs40-win2003-87.gif
    peap-acs40-win2003-88.gif
    peap-acs40-win2003-89.gif
  16. After authentication is successful, check the TCP/IP configuration for the wireless adapter by using Network Connections. It should have an address range from the DHCP scope or the scope created for the wireless clients.

    We have also configured the Cellphones (tested on Nokia N79 and Windows Mobile) to connect to the wireless router by adding the certificates on them, and now they are also able to authenticate through RADIUS Server. I'll post all the steps involved in it soon.

    Related Articles:

Configuring Cisco Secure ACS for Windows PEAP-MS-CHAPv2 - [Part 1]

Introduction
 I was working on improving and managing (logging) the security of my wireless network and for this purpose I was searching for steelbelted RADIUS which used to be a freeware, but recently I found that Juniper bought it and its no more freeware now. Therefore I started looking for an alternative and I found one that is Cisco ACS. My plan was to place RADIUS behind the wireless routers placed in my office and authenticate the users trying to connect to Wifi through RADIUS server preventing the unauthorized users access and also generate their logs. Below article helped me in the process I have also specified the changes done by me to make things work. The procedure mentioned below is for the workgroup environment not for the Domain environment.


Do let me know if you face any problem I'll be posting more on this soon keep following @ahsantasneem

[Contd..]



Both PEAP and EAP-TLS build and use a TLS/Secure Socket Layer (SSL) tunnel. PEAP uses only server-side authentication; only the server has a certificate and proves its identity to the client. EAP-TLS, however, uses mutual authentication in which both the ACS (authentication, authorization, and accounting [AAA]) server and clients have certificates and prove their identities to each other.
PEAP is convenient because clients do not require certificates. EAP-TLS is useful for authenticating headless devices, because certificates require no user interaction.

Network Diagram


This document uses the network setup shown in the diagram below.
/image/gif/paws/43486/acs-peap-01.gif

Obtain a Certificate for the ACS Server (Self-Signed Certificate)

The Self signed certificate will be valid for 1 year.







  1. Click System Configuration.
    /image/gif/paws/72013/peap-acs40-win2003-62.gif
  2. Click ACS Certificate Setup.
    /image/gif/paws/72013/peap-acs40-win2003-63.gif
  3. Click Install ACS Certificate.
    /image/gif/paws/72013/peap-acs40-win2003-64.gif
  4. Choose Read certificate file and type the location of the cert in my case it was c:\xxxx.cer

  5. Click Submit.
    peap-acs40-win2003-66.gif
  6. Click System Configuration.
  7. Click Service Control and then click Restart.
    peap-acs40-win2003-67.gif
  8. Click System Configuration.
  9. Click Global Authentication Setup.
  10. Check Allow EAP-MSCHAPV2 and Allow EAP-GTC.
    /image/gif/paws/72013/peap-acs40-win2003-68.gif
  11. Click Submit + Restart.
  12. Click System Configuration.
Follow these steps to restart the service and configure PEAP settings.
  1. Click System Configuration, and then click Service Control.
  2. Click Restart to restart the service.
  3. To configure PEAP settings, click System Configuration, and then click Global Authentication Setup.
  4. Check the two settings shown below, and leave all other settings as default. If you wish, you can specify additional settings, such as Enable Fast Reconnect. When you are finished, click Submit.
    • Allow EAP-MSCHAPv2
    • Allow MS-CHAP Version 2 Authentication
    Note: For more information on Fast Connect, refer to "Authentication Configuration Options" in System Configuration: Authentication and Certificates.
    /image/gif/paws/43486/acs-peap-15.gif

Specify and Configure the Access Point as an AAA Client

Follow these steps to configure the access point (AP) as an AAA client.
  1. Click Network Configuration. Under AAA Clients, click Add Entry.
    /image/gif/paws/43486/acs-peap-16.gif
  2. Enter the AP's hostname in the AAA Client Hostname field and its IP address in the AAA Client IP Address field. Enter a shared secret key for the ACS and the AP in the Key field. Select RADIUS (Cisco Aironet) as the authentication method. When you are finished, click Submit.
    /image/gif/paws/43486/acs-peap-17.gif

Configure the Linksys Wireless Router






And thats it, your Linksys wireless router is configured now with you Cisco ACS RADIUS server.

Related Articles
Configuring Cisco Secure ACS for Windows PEAP-MS-CHAPv2 - [Part 2]