1. Configure the network (static IP).


sudo apt-get update


3.  Edit /etc/hosts The installation will take the domain name of the line

Server.m4dom.local server 127.0.1.1

4. It is advisable to change the hostname in / etc / hostname to match the way you made ​​to / etc / hosts.
5. Install the LDAP server. During the installation we will be asked for the password of the administrator of the LDAP tree.

sudo apt-get install slapd ldap-utils

6. Verify the correct operation of LDAP

ldapsearch-x-LLL-b dc = m4dom, dc = local

7. Install the phpldapadmin

sudo apt-get install phpldapadmin

8. Properly configure phpldapadmin. Edit /etc/phpldapadmin/config.php and replace dc = example, dc = tld our domain name (dc=example,dc=com). Restart Apache

service apache2 restart

9. We can manage to enter the domain through the URL http://sserver/phpldapadmin. We login with
User: cn = admin, dc = m4dom, dc = local
password: entry during the installation of slapd

Continue

Webhosting with HA and with kloxo NFS, Rsync, Heartbeat

Comming Soon Subscrice through Email within few days I will update

Continue

No Matter what people think about UNITY/UBUNTU but it seems that ubuntu community is adding a WOW factor to the SYSTEM in terms of speed, stability, design, smoothness and the best thing is that unity is getting mature day by day by the release of newer version you can note the changes in unity from 11.04 to 13.04 unity/ubuntu has grown really well and its getting my favourite interface.

Ubuntu 13.04 is released.
Well when people talk about features in newer version of any thing though its a OS or a CAR they first see the changes in design and hardly note the improvements in core/functionality of that particular thing.Today i am going to talk about my personal experience with ubuntu as a END user.

What is my experience as an END USER?
END USER ? whats that??? :O
Well let me explain by end user, I mean that i am using ubuntu 13.04 for the first time and I love music, I love surfing internet, I love fast system ETC.

so, My first reaction was
WOOOWW its DAMN fast.

My End User Experience In Terms Of Speed.
BOOTING TIME ----------------- Fast
Iniciating Session ------------------ Fast
Firt time opening Mozilla/chrome after login -------------- Normal
HERE STARTS FUN
Opening Filemanger ------------------------- Cooool Fast
Open any other program --------------- Taking really less time

In terms of speed ubuntu 13.04 amazed me and all time I say wow.

My End User Experience In Terms Of Design.
Well design is not that changed but i am liking the way we can manage files in Nautilus and start menu of ubuntu/unity i liked from the first day and its also really improved. There is not much to talk on design but there are alot of new customization options in UNITY A few icons are new and what i liked in design are two things
1. File manager sidebar

Look at the cool sidebar icons i love these icons they are so simple and clean

2. Top bar in file manager

in Top bar we have new features in search within folders and arange icons and new style buttons these are cool looking buttons.

3. Changes in Start MENU UNITY

If you righ click any APP in start menu of unity/ubuntu your will see the description of the app and its really cool.

THATS ALL ABOUT DESIGN FOR ME

But at the end i must say I am using ubuntu from past 1 month and i have no issue of compatibilty and I got no Error its so stable to me i use VirtualBOX and mutliple machines to practice my networking and i use as web server as well i have no issue with this at all I have installed SUBLIME editor free version and its just so cool

Here is a screenshot of SUBLIME editor for Ubuntu

Thanks for reading , If you like that topic please comment , share and subscribe.

Continue

This is how to setup Node.js on windows

--Links-- 

http://nodejs.org/#download

Continue

Node.js is a server-side software system designed for writing scalable Internet applications, notably web servers.[1] Programs are written on the server side in JavaScript, using event-driven, asynchronous I/O to minimize overhead and maximize scalability. 
Node.js is a packaged compilation of Google's V8 JavaScript engine, the libUV platform abstraction layer, and a core library, which is itself primarily written in JavaScript. Node.js was created by Ryan Dahl starting in 2009, and its development and maintenance is sponsored by Joyent, his former employer. Dahl's original goal was to create web sites with push capabilities as seen in web applications like Gmail. After trying solutions in several other programming languages he chose JavaScript because of the lack of an existing I/O API. This allowed him to define a convention of non-blocking, event-driven I/O.[5] Similar environments written in other programming languages include Tornado and Twisted for Python, Perl Object Environment for Perl, libevent for C, Vert.x for Java, Akka for Java and Scala, EventMachine for Ruby and vibe.d for D. Unlike most JavaScript programs, it is not executed in a web browser, but instead as a server-side JavaScript application. Node.js implements some CommonJS specifications.[6] It provides a REPL environment for interactive testing.

Continue

Node.js is a server-side software system designed for writing scalable Internet applications, notably web servers.[1] Programs are written on the server side in JavaScript, using event-driven, asynchronous I/O to minimize overhead and maximize scalability.
Node.js is a packaged compilation of Google's V8 JavaScript engine, the libUV platform abstraction layer, and a core library, which is itself primarily written in JavaScript. Node.js was created by Ryan Dahl starting in 2009, and its development and maintenance is sponsored by Joyent, his former employer. Dahl's original goal was to create web sites with push capabilities as seen in web applications like Gmail. After trying solutions in several other programming languages he chose JavaScript because of the lack of an existing I/O API. This allowed him to define a convention of non-blocking, event-driven I/O.[5] Similar environments written in other programming languages include Tornado and Twisted for Python, Perl Object Environment for Perl, libevent for C, Vert.x for Java, Akka for Java and Scala, EventMachine for Ruby and vibe.d for D. Unlike most JavaScript programs, it is not executed in a web browser, but instead as a server-side JavaScript application. Node.js implements some CommonJS specifications.[6] It provides a REPL environment for interactive testing.

Continue

In most enterprise networks, DHCP servers are located in a designated services segment in a data center or some other central location. DHCP requests initiated by hosts at the LAN edge are forwarded by edge routers to centralized DHCP servers on behalf of the originating hosts. On Cisco IOS, this functionality is enabled by configuring an IP "helper" address on the edge interface. For example, if we wanted to forward all DHCP requests from VLAN 10 to a DHCP server at 192.168.100.42, we would use the command ip helper-address under the SVI configuration:

interface Vlan10
 ip address 192.168.10.1 255.255.255.0
 ip helper-address 192.168.100.42

By default, this feature forwards not only DHCP traffic, but all UDP-based broadcast traffic, including TFTP, DNS, NTP, and others. The specific protocols (well, ports) which are forwarded can be tweaked using the command ip forward-protocol.

When migrating from IOS to NX-OS, one could be forgiven for assuming this functionality was carried over to the Nexus world. Unfortunately, NX-OS operates a bit differently. While we can of course still forward DHCP requests out of a local subnet, the mechanism NX-OS uses to accomplish this deserves attention.

On IOS, the IP helper feature simply forwarded all UDP broadcasts to the specified IP address. The analagous NX-OS command ip dhcp relay forwards only DHCP broadcasts. More importantly, it forwards all DHCP broadcasts. Here's what the command looks like applied to an SVI on a Nexus switch:

interface Vlan10
 ip dhcp relay address 192.168.100.42

Seems simple enough, right? But let's take a look under the hood with the command show system internal access-list:

Nexus# show system internal access-list vlan 10

slot  1
=======

Policies in ingress direction:
         Policy type              Policy Id      Policy name
------------------------------------------------------------
    DHCP                               5          Relay

No Netflow profiles in ingress direction

Tcam 1 resource usage:
----------------------
 Label_b = 0x801
 Bank 0
 ------
   IPv4 Class
     Policies: DHCP(Relay)  [Merged]
     6 tcam entries

0 l4 protocol cam entries
 0 mac etype/proto cam entries
 0 lous
 0 tcp flags table entries
 1 adjacency entries

No egress policies
No Netflow profiles in egress direction

We can see that an access list has been created for VLAN 10 to match traffic to be relayed. Results are shown per line module; here, only slot one is listed.

We can dig deeper into the access list itself by appending the parameter input config. This yields the structure of the access list itself:

Nexus# show system internal access-list vlan 10 input config

slot  1
=======

Policy id:  5, Type: DHCP, Protocol: IPv4   Name: Relay
  redirect: to sup

redirect udp 0.0.0.0/0.0.0.0  range 67 68  255.255.255.255/255.255.255.255
redirect udp 0.0.0.0/0.0.0.0  255.255.255.255/255.255.255.255  range 67 68
permit ip 0.0.0.0/0.0.0.0  0.0.0.0/0.0.0.0  *

The output is a little unpolished, but we can interpret the ACL easily enough. The first line matches all broadcast UDP traffic sourced from any address on port 67 or 68, and the second line matches all broadcast UDP traffic from any address destined for port 67 or 68. The action for both of these lines is "redirect." The last line is an implicit (denoted by the asterisk) permit statement which allows all other traffic to pass.

Currently, there is no feature available on NX-OS to forward arbitrary UDP traffic like on IOS. Although this may be limiting in some situations, I think it's justified given that the Nexus series is oriented toward datacenter networking.

More detail concerning the differences between the IOS and NX-OS implementations of this feature can be found in Cisco's excellent Docwiki.

Continue

Suppose we have the following scenario and want to install the FTP Server service and DNS. The steps are as follows:

1. Configure TCP / IP for both client and server. Remember uncheck IPv6 in the properties window TCP / IP.

2. Check the LAN connection between client and server. If the ping succeeds had to point 3.

3. We add the FTP service on the server:

• <Control Panel> <Enable caracteristicas> <Programas and features on or off Windows Folder <Features> <Add functions> server> <Memory <dns> and Web <Server (IIS)>
•  Within the IIS feature is the FTP.
• To see that this started we will: <Home> <Herramientas administrativas> <IIS>

4. Install Active Directory:

• <execute> <Home> <dcpromo>:
•  Create a new domain in a new forest
•  FQDN: miempresa.com
•  Domain functional level: Windows Server 2003 (ensures compatibility with Windows Server 2008) in Windows Server 2008 change adds no new functionality and does not support Windows Server 2003 in the event that there are more servers in the network.
•  Next, next .....
•  Restart

5. Create a new FTP site:

• Create a new FTP site from the IIS console:
• IP: The server
• Do not isolate users
• directory: C: \ empresaFTP
• Permits: L and E
• Inside the folder empresaFTP put some file.
• In <Properties> Can see the site properties:
• By default the user disconnects inactive 120sec
• Ports used.
• You have enabled logging. See where you save and It stores
• Option to write a welcome message.

 Configuring the DNS to resolve ftp.miempresa.com

• Client PC open a browser and type: ftp://ftp.miempresa.com. We list and download the file but can not write because we have default permissions.

Beware that the Windows Firewall is off, when you reboot the machine back on.

6. Configure FTP site with user access:

• From the Server setup the old site to not allow anonymous access,

• Create user in active directory JR:
• Open console and Equipment Actuve User> Directory>
• Create a new organizational unit called ftpusers.
• Create a user within ftpusers JR.
• 
  
• We include the client PC with the user domain Jr:
• ftp.miempresa.com try to access the site and folder c: \> EmpresaFtp. By default we will read and execute permissions since JR is a user belonging to the Domain Users group

• We eliminate the "user group" in the folder c: \> EmpresaFtp. You can access now? no
•  Right click on the folder, properties, security,

• Advanced Options: (will neceasary this step to remove the inherited permissions of the group)

• Uncheck "Include inheritable permissions ....." and copy. OK, OK

Edit and Remove "Users (MyCompany \ Users)"

• We add the user "JR" permissions to the folder c: \> EmpresaFtp. You can read and write? Write not.
• We give the user "JR" in the security tab of the folder c: \> EmpresaFtp permission.

We found that pq modemos modify the file we downloaded, we modify and upload to the server has become all from Windows Explorer (not from Internet Explorer)

• We will keep JR can save more than 100KB in EmpresaFtp folder.:

• Disco <Display C> <Cuota>:
• Enable quota manager
• Deny space if it exceeds limit
•  Register an event when ......

• <Factory of Cuota> <New>, add user JR and space limits.

Since the client and the user connected with JR, we try to copy more than 100KB of information in the folder EmpresaFtp. If all goes well, we will receive a warning message to the copied 90KB 100KB and if we exceed the error and we will not leave us. We may be seeing the messages in the event screen in <Display C> disk, <Cuotas>, <Factory of Cuota> and select User JR.

Continue

Eric Geier shows how to give Apple iOS devices access to an 802.1X-protected Wi-Fi network, Microsoft Exchange services, VPN access, and more.

If you find more and more users with iPhones, iPod Touches, or iPads, you might consider officially deploying and supporting them on your network. They might already be an essential tool to the users, offering an email client, calendar and scheduler, contacts manager, web browser, and endless other features and functions with third-party apps. They can be even more useful if you support them on your network, instead of leaving it up to the users to try to connect to the Wi-Fi and other network resources.

Apple’s iOS platform—featured on the iPhone, iPod touch, and iPad—is designed to easily integrate within an organization’s network. This can give users easier access to any Microsoft Exchange services (such as email and calendar), VPN servers, or connection to an 802.1X-protected wireless network (WPA/WPA2-Enterprise). It can also help you better control the mobile devices with polices and gives you remote wiping capabilities. Plus, in the long run this can make it easier to set up the Apple iOS devices and reduce support calls.

In this article, we’ll review the deployment steps and see what’s involved in getting Apple iOS devices on a network.

Preparing the Network Services You Want to Support

If you have Microsoft Exchange setup for the users and want to offer access via Apple iOS devices, ensure you support Exchange ActiveSync (EAS) on Exchange Server 2003 or 2007. This is what connects the devices and the Exchange server together, via the cellular or Wi-Fi connection of the device. For Exchange Server 2007, also make sure the Client Access Role is installed. For Exchange Server 2003, make sure you’ve enabled Outlook Mobile Access (OMA).

If you don’t use Microsoft Exchange, you can still configure the devices for email using IMAP, which also could be Lotus Notes/Domino or Novell GroupWise. Make sure the email server supports both user authentication and SSL. You can also provide a global address directory via a LDAP directory and a global calendar via a calendar server that supports the CalDAV standard.

If you have a wireless network, all the Apple iOS devices can connect. All the Wi-Fi encryption methods (WEP, WPA/WPA2 Personal and Enterprise) are supported. If your network uses 802.1X authentication with WPA/WPA2-Enteprise encryption, ensure you’re using one of the supported EAP types: EAP-TLS, EAP-TTLS, EAP-FAST, PEAPv0, PEAPv1, or LEAP. Also make sure the RADIUS server is up and working and you have any client certificates ready if you want to use a protocol like EAP-TLS.

If you want to offer VPN access, ensure you use one of the supported protocols: Cisco IPSec, L2TP over IPSec, or PPTP protocol. No additional configuration should be needed in order to connect the Apple iOS devices.

If you want to distribute enterprise applications to the devices, you can do so with the iPhone Configuration Utility or iTunes. Keep in mind, updating the applications is easier if users have iTunes installed on their own Mac or PC.

Continue

This chapter enables you to prepare for the deployment of an advanced authorization scheme for your remote users, allowing you to control the level of access granted to them based on such information as their internal department, username, IP address, and so on, using the familiar local group policies that are configured on the ASA device.

This chapter covers the following subjects

• Configuration Procedures, Deployment Strategies, and Information Gathering:This section covers what to consider when deciding whether to deploy an internal AAA server for authorization.
• Configuring Local and Remote Group Policies: This section discusses the differences between ASA local and remote group policies and the configuration required on the ASA for the deployment of each.
• Accounting Methods for Operational Information: This section reviews the accounting methods available on the ASA for connection and user information gathering.

In earlier chapters, you learned how to plan for and configure the various authentication mechanisms available on the Adaptive Security Appliance (ASA) to allow remote users access into your environment. Now that you have given them access, you need to control and account for it.

The information in this chapter will enable you to prepare for the deployment of an advanced authorization scheme for your remote users, allowing you to control the level of access granted to them based on such information as their internal department, username, IP address, and so on, using the familiar local group policies that are configured on the ASA device. This chapter also introduces you to remote group policies, their configuration on the ASA, and their remote server requirements.

After the various ways to authorize remote users into your environment has been explored, the discussion moves on to review the accounting methods available on the ASA device that enable you to track the success or failure of specific authorization settings and connections.

“Do I Know This Already?” Quiz

The “Do I Know This Already?” quiz helps you determine your level of knowledge on this chapter’s topics before you begin. Table 17-1 details the major topics discussed in this chapter and their corresponding quiz sections.

Table 17-1 “Do I Know This Already?” Section-to-Question Mapping

Foundation Topics Section	Questions
Configuring Local and Remote Group Policies	1,2,3,4
Accounting methods for Operational Information	5,6,7

1. Which of the following are available group policy types on the ASA? (Choose all that apply.)
   1. Internal
   2. External
   3. Active
   4. Standby
2. Which of the following are legitimate ways to assign a group policy? (Choose all that apply.)
   1. DAP
   2. Direct user assignment
   3. Connection profile
   4. AAA
3. In what format are the attributes stored in an external group policy?
   1. Text files
   2. A/V pairs
   3. CSV files
   4. XML files
4. Which of the following remote user types are external group policy objects available on? (Choose all that apply.)
   1. LDAP
   2. TACACS+
   3. SDI
   4. RADIUS
5. By default, where is ASA syslog information stored?
   1. External syslog server
   2. Internal syslog server
   3. NetFlow collection service
   4. ASA internal buffer
6. When configuring an AAA server on the ASA, which communication protocol when configured allows for secure (SSL/TLS) communication between the AAA server and the ASA?
   1. UDP
   2. SCEP
   3. SMTP
   4. TCP
7. Which of the following are available actions used for NetFlow flow information creation? (Choose all that apply.)
   1. Created
   2. Denied
   3. Torn down
   4. Dropped

Continue