CAMNET-FREE

Tuesday, August 9, 2016

Dynamic Routing Protocol (OSPE with Different Area)

First Configure
 Router > en
 Router # conf t
 Router (config) # int loopback0
 Router (config-if) # ip add 2.2.2.2 255.255.255.252
 Router (config-if) # no shut
 Router (config-if) # int s1/0
 Router (config-if) # ip add 192.168.1.1 255.255.255.252
 Router (config-if) # no shut
 Second Configure
 Router (config-if) # router ospf 1
 Router (config-router) # network 2.2.2.0 0.0.0.3 area 0
 Router (config-router) # network 192.168.1.0 0.0.0.3 area 0
Router 2
 First Configure
 Router > en
 Router # conf t
 Router (config) # int loopback0
 Router (config) # ip add 2.2.3.2 255.255.255.252
 Router (config) # no shut
 Router (config) # int s1/0
 Router (config) # ip add 192.168.1.2 255.255.255.252
 Router (config) # no shut
 Router (config) # int s1/1
 Router (config) # ip add 192.168.2.1 255.255.255.252
 Router (config) # no shut
Router (config) # router ospf 1
 Router (config) # network 2.2.3.0 0.0.0.3 area 1
 Router (config) # network 192.168.1.0 0.0.0.3 area 0
 Router (config) # network 192.168.2.0 0.0.0.3 area 1
 Router (config) # area 1 virtual-link 2.2.4.2 authentication
Router 3
 First Configure
 Router > en
 Router # conf t
 Router (config) # int lookback0
 Router (config) # ip add 2.2.4.2 255.255.255.252
 Router (config) # no shut
 Router (config) # int s1/0
 Router (config) # ip add 192.168.2.2 255.255.255.252
 Router (config) # no shut
 Router (config) # int s1/1
 Router (config) # ip add 192.168.3.1 255.255.255.252
 Router (config) # no shut
 Second Configure
 Router (config) # router ospf 1
 Router (config) # network 2.2.4.0 0.0.0.3 area 2
 Router (config) # network 192.168.2.0 0.0.0.3 area 1
 Router (config) # network 192.168.3.0 0.0.0.3 area 2
 Router (config) # area 1 virtual-link 2.2.3.2 authentication
 Router (config) # area 1 virtual-link 2.2.2.2 authentication
Router 4
 First Configure
 Router > en
 Router # conf t
 Router (config) # int s1/0
 Router (config) # ip add 192.168.3.2 255.255.255.252
 Router (config) # no shut
 Second Configure
 Router (config) # router ospf 1
 Router (config) # network 192.168.3.0 0.0.0.3 area 2

Dynamic Routing Protocol (OSPE with Different Area)

CIDR (Classes Inter Domain Routing)

255.0.0.0 /8
255.128.0.0 /9
255.192.0.0 /10
255.224.0.0 /11
255.240.0.0 /12
255.248.0.0 /13
255.252.0.0 /14
255.254.0.0 /15
255.255.0.0 /16
255.255.128.0 /17
255.255.192.0 /18
255.255.224.0 /19
255.255.240.0 /20
255.255.248.0 /21
255.255.252.0 /22
255.255.254.0 /23
255.255.255.0 /24
255.255.255.128 /25
255.255.255.192 /26
255.255.255.224 /27
255.255.255.240 /28
255.255.255.248 /29
255.255.255.252 /30
255.255.255.254 /31
255.255.255.255 /32

DHCP on router

Router0
 First Configure
 Router > en
 Router # conf t
 Router (config) # int f0/1
 Router (config-if) # ip add 10.0.0.1 255.0.0.0
 Router (config-if) # no shut
 Router (config-if) # ip dhcp pool test
 Router (dhcp-config) # network 10.0.0.0. 255.0.0.0
 Router (dhcp-config) # default-router 10.0.0.1
 Router (dhcp-config) # do show dhcp lease
 Router (dhcp-config) # exit
 Router (config) # int f0/0
 Router (config-if) # ip add 20.0.0.1 255.0.0.0
 Router (config-if) # no shut
 Router (config-if) # ip dhcp pool test1
 Router (dhcp-config) # network 20.0.0.0. 255.0.0.0
 Router (dhcp-config) # default-router 20.0.0.1
 Router (dhcp-config) # do show dhcp lease

OSI Model

OSI Model
OSI Model was born 1970
It means to help vender (hardware company) create interoperable network devices and software in the form
of protocol so that different vender network could work with each other
There are 7 Layer of ISO Model

Application
Presentation
Session
Transport
Network
Data Link
Physical

Application Layer
 Provides a user interface.
Ex File, Message, Data encrypt, Data Compress
Presentation Layer
 Present data
 Handle processing such as encryption
Session Layer
 Keep different applications’ data
Transport Layer
 Provides reliable or unreliable delivery
 Perform error correction
Network Layer
 Provides logical addressing, which routes used for best path determine
Ex Router
Data Link
 Combine packet into bytes and bytes into frame
 Provide access to media using MAC
Physical
 Moves bits between devices
Ex Wire Speed, Pin out and Cable

OSI Model

VLSM for ip address 192.168.0.0/27

Router1 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.0 /30
o First IP 192.168.0.1
o Last IP 192.168.0.2
o Broadcast IP 192.168.0.3
 Router2 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.4 /30
o First IP 192.168.0.5
o Last IP 192.168.0.6
o Broadcast IP 192.168.0.7
 Router4 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.8 /30
o First IP 192.168.0.9
o Last IP 192.168.0.10
o Broadcast IP 192.168.0.11
 Government (18 Host)
o Host = 32 = 25
o Customize Subnet = 32 - 5 = 27
o Block Size = 32
o Network 192.168.0.12 /27
o First IP 192.168.0.13
o Last IP 192.168.0.42
o Broadcast IP 192.168.0.43
 House (18 Host)
o Host = 32 = 25
o Customize Subnet = 32 - 5= 27
o Block Size = 32
o Network 192.168.0.44 /27
o First IP 192.168.0.45
o Last IP 192.168.0.74
o Broadcast IP 192.168.0.75
 University (90 Host)
o Host = 128 = 27
o Customize Subnet = 32 - 7 = 25
o Block Size = 128
o Network = 192.168.0.76 /25
o First IP = 192.168.0.77
o Last IP = 192.168.0.202
o Broadcast IP = 192.168.0.203
 Town (132 Host)
o Host = 256 = 28
o Customize Size = 32 - 8 = 24
o Block Size = 256
o Network = 192.168.1.0 /24
o First IP = 192.168.1.1
o Last IP = 192.168.1.254
o Broadcast IP = 192.168.1.255
 Government (180 Host)
o Host = 256 = 28
o Customize Subnet = 32 - 8= 24
o Block Size = 256
o Network 192.168.2.0 /24
o First IP 192.168.2.1
o Last IP 192.168.2.254
o Broadcast IP 192.168.2.255
 Building (200 Host)
o Host = 256 = 28
o Customize Subnet = 32 - 8= 24
o Block Size = 256
o Network 192.168.3.0 /24

VLSM (Variable Length, Sub netting, Masking)

Router1 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.0 /30
o First IP 192.168.0.1
o Last IP 192.168.0.2
o Broadcast IP 192.168.0.3
 Router2 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.4 /30
o First IP 192.168.0.5
o Last IP 192.168.0.6
o Broadcast IP 192.168.0.7
 Router3 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.8 /30
o First IP 192.168.0.9
o Last IP 192.168.0.10
o Broadcast IP 192.168.0.11
 Router4 (2 Host)
o Host = 4 = 22
o Customize Subnet = 32 - 2 = 30
o Block Size = 4
o Network 192.168.0.12 /30
o First IP 192.168.0.13
o Last IP 192.168.0.14
o Broadcast IP 192.168.0.15
 House (8 Host)
o Host = 16 = 24
o Customize Subnet = 32 - 4 = 28
o Block Size = 16
o Network 192.168.0.16 /28
o First IP 192.168.0.117
o Last IP 192.168.0.30
o Broadcast IP 192.168.0.31
 Building (10 Host)
o Host = 16 = 24
o Customize Subnet = 32 - 4 = 28
o Block Size = 16
o Network 192.168.0.32 /28
o First IP 192.168.0.33
o Last IP 192.168.0.46
o Broadcast IP 192.168.0.47
 Government (18 Host)
o Host = 32 = 25
o Customize Subnet = 32 - 5 = 27
o Block Size = 32
o Network 192.168.0.48 /27
o First IP 192.168.0.49
o Last IP 192.168.0.78
o Broadcast IP 192.168.0.79
 Town (32 Host)
o Host = 64 = 26
o Customize Size = 32 - 6 = 26
o Block Size = 64
o Network = 192.168.0.80 /26
o First IP = 192.168.0.81
o Last IP = 192.168.0.122
o Broadcast IP = 192.168.0.123
 University (50 Host)
o Host = 128 = 27
o Customize Subnet = 32 - 7 = 25
o Block Size = 128
o Network = 192.168.0.124 /25
o First IP = 192.168.0.125
o Last IP = 192.168.0.250
o Broadcast IP = 192.168.0.251
 City (63 Host)
o Host = 128 = 27
o Customize Subnet = 32 - 7 = 25
o Block Size = 128
o Network 192.168.1.0 /25
o First IP 192.168.1.1
o Last IP 192.168.1.126
o Broadcast IP 192.168.1.127

Wednesday, July 27, 2016

Destination NAT for a Web Server on the Private Network with Port Translation In

In this example, you want to run a web server on your local area network using a private IP
address but also make a web site available to the general public. On your web server, you run
your company’s Microsoft SharePoint server on port 80 and only want it available to local
hosts. Your company’s public web site runs on port 8080 on the server, and you want
available to the general public outside your firewall on the standard HTTP port 80.
1. Create a new Nat rule using IP button, then Firewall, and then click the NAT tab and
the plus sign.
2. Select the chain “dstnat”, the Dst. Address as the address of the public IP (in this
case 66.76.100.2), the protocol as “TCP”, and the destination port as port 80.
3. On the action tab, select the action “dst-nat”, the destination address as the private IP
of your web server, and the destination port as 8080.
The

Destination NAT with Action Redirect

Each of the actions you set for a NAT rule accomplishes a more complex function in the
background. The masquerade action for instance strips the source IP and applies the router’s
public (outgoing) IP while destination NAT strips the destination IP address or port and
applies a different destination IP address or port. There is another useful action called
“redirect” that is often used for certain applications.
Consider an example. You operate a network and use your upstream provider’s DNS servers
for your customers. Many of your customers have static IP’s and static DNS entries. For
whatever reason the decision is made to change upstream providers, however, your current
provider does not allow DNS resolution from IP’s outside its network. Obviously you could
use a NAT rule with masquerade to masquerade the old provider’s public IP’s and treat them
as private IP’s while you are transitioning over to the new provider, but what about the static
DNS entries? This is where the redirect action can step in.
Think of redirect as a transparent NAT, it transparently applies a NAT action to packets
based on matching criteria. The other important thing to remember for a redirect rule is that it
“captures” the traffic and processes it on the router itself. This is a different action than a
destination NAT rule with an action of destination NAT.
To summarize the difference between these two types of rules, think of it like this: A NAT
rule with an action of destination NAT sends the traffic to a host while a destination NAT rule
with an action of redirect “captures” the traffic and processes it on the router.
Getting back to our example, we can remedy the DNS issue by capturing the DNS requests on
the router and processing them there using the router’s internal caching DNS server. We will
discuss caching DNS later in this book, but let it suffice to say for now we have already
configured caching DNS on the router and it is able to resolve DNS requests from the new
provider’s DNS servers. In this case, simply create a new destination NAT rule with
matchers for protocol TCP, port 53, and an action of redirect to port 53. The second rule we
need is a duplicate of the first with a protocol of UDP. These two rules will capture all DNS
requests trying to go to our old provider’s DNS servers and answer them on the router itself.
We can then take our time doing the IP transition on the network to the new provider’s IP’s.
Another example of using redirect is to create a transparent proxy. If we aren’t familiar with
proxy servers (the most popular one is called Squid), their function is to accept web requests
(HTTP traffic) and then proxy those requests to the public network. These pages fetched may
be stored in memory or on disk for later serving to proxy clients. This speeds up network
access, enables the use of access rules to restrict use of the Internet, and gives the ability to
redirect web pages, or many other useful functions described later in this book under the IP
Web Proxy function.
If we want this function to be applied without the knowledge of your clients or users and
without intervention on their part, again a redirect rule is the answer. In this scenario, create a
new destination NAT rule matching protocol TCP, port 80, with an action of redirect to port
8080 (or whatever port we have IP Web Proxy running on at the router). Once configured, all
HTTP requests to the Internet will be intercepted at the router and handled by the proxy
server.

Firewalls on Mikrotik

Where there are options there is power. Where there is power there also can be complexity
and therefore creating firewalls with RouterOS is often seen as an area of complexity where
users fear to tread. As a result, many either make the decision to forego the firewall and hope
for the best or copy firewalls others have created online and thereby never realize the power
that a properly created firewall can have and the protection it can offer their network or their
network connected devices.
I have often heard it said that the best way to protect a network is to put the hosts inside a
vault, lock the door, post a guard and never connect the network to the Internet. Although this
is a bit extreme, the concept is basic and understandable; access to a network is the means by
which a security breach or attack occurs. Remove the access and you remove the threat.
Equally obvious is the fact that our networks need to be connected to the public Internet so
there is the application for firewalls.

Let’s begin with the input chain. The input chain is designed to protect the router itself.
Consider the following diagram:

Licensing

One of the attributes of RouterOS that delivers the most value is the base feature set, which is
consistent across the entire license range. While many manufacturers require additional fees
to add even standard base features, MikroTik delivers all of the features in all license levels
and simply restricts the number of instances. Licenses are included with RouterBOARDs and
licensing is typically not an area where you will need to spend much time for basic setups.
However, if you need to install RouterOS on a PC or turn a RouterBOARD designed as a
client device into an access point, then this information is important.
For example, with a level 3 license, you can construct a point-to-point link with a single client
but to add multiple clients in ap-bridge mode, a level 4 license is required. On the other hand,
MPLS, an advanced feature, is available across the entire license level spectrum.
The following chart displays the various license levels and their associated features:

Upgrading and Downgrading the Operating System, Package Management

RouterBOARDs come from MikroTik preloaded with RouterOS. MikroTik recommends that
you upgrade your board to the latest version of RouterOS before beginning any configuration.
The operating system is in constant development and new features or bug fixes are frequently
available, sometimes even monthly. The decision to do an upgrade on a production system on
the other hand should be based on some basic logical reasoning such as:

1. Is there a feature I want to add to my device that the new OS will provide?
2. Is there a security vulnerability this version solves?
3. Is there a bug fix this version provides?
4. Do I need to upgrade to provide support for some new hardware?

All of these are valid reasons to upgrade your device. As a friend of mine says, “Every
problem is the result of a previous solution.” and I think that holds true for upgrades. Another
one I am sure you have heard is “if it isn't broken don’t fix it”. I think you get the point here, if
the criteria expressed above doesn’t apply, leave your router alone. It is doing its job and
doesn’t need your help, however, if you need to do an upgrade, read on.

Upgrading the Operating System

1. First, you must download the upgrade package from MikroTik. After web browsing
to the MikroTik site, locate the download section and select the platform you want to
upgrade. See page 36 if you have any questions about which file to download.

2. Download the .npk package to your desktop. Typically the package you want is the
stable version, “combined package”. This single file contains the same features that are
installed by default on the device.

3. Once the package is downloaded (typically around 12 megs), launch WinBox and
access through the device’s IP address, not through the MAC address. As stated before,
the Layer 3 method is the best for all normal router management.

4. Inside WinBox, click the Files button. This will open the Files List showing all the
visible files stored on the router.

5. Next, drag the package from your desktop to the files window. This can be a bit
tedious, depending on how the files are sorted in the files window. Dropping the file
inside a folder will prevent the upgrade from taking place so use care to get it at the top
of the list. One trick here is to click the Backup button in the Files List. This will
produce and save a backup file, which sorts to the top of the list and allows you a little
space in which to drop the upgrade package. The npk file doesn’t have to be the top file
in the list, but make sure it isn’t in a folder.

6. Dropping the file in the area identified by the red arrow will produce the desired
result:

7. Once the file has completely uploaded, issue a reboot command by clicking System
and Reboot.
Note: Pulling the power at this point will not upgrade the router; you must enter a
graceful reboot using the reboot command due to the process RouterOS uses to update
the device.
After

What is WinBox?

WinBox is a Microsoft Windows based GUI that is by far the simplest way to configure a
RouterOS device. It is extremely powerful and allows configuration of 99% of the feature set.
WinBox is a standalone executable, meaning it isn’t necessary to install anything on your PC
other than to download the program, simply save it to your computer and double click it to
start it. If you don’t have WinBox already you can download it from MikroTik.com.
The first time you try to connect to your MikroTik device it may or may not have an IP address
configured on it. One of the great features of WinBox is the ability to “get in” without an
actual IP address but a note of caution here is needed. Access using the MAC address should
only be used in order to configure an IP address on the device. It is not a reliable way of
accessing the router. I hesitate to call it an unreliable method, but it’s not the correct method
and sometimes you may get unexpected results, i.e., configuration pages that don’t properly
populate or frequent disconnections. The feature is meant to be used it in an emergency or for
first time access to configure an IP address on it and then to go back in using the IP.
With WinBox running, simply click the square button with the three dots to scan the local area
network for MikroTik devices.

Then,

What is RouterOS?

In simple terms, RouterOS is routing software that runs on a PC based hardware platform.
Whether it’s a conventional X86 based PC, a RouterBOARD, embedded device, or a virtual
machine, RouterOS is an operating system that will make your device a dedicated router, a
bandwidth shaper, a transparent packet filter, or a wireless enabled device. Have an old PC
lying around? With RouterOS, it can be converted into a powerful router!
RouterOS can also be installed on a virtual machine, VMware/ESX environment, or parallels
if you are using Mac.
RouterBOARD is a hardware platform manufactured by MikroTik. The product can range
from a very small home router to a carrier class access concentrator. If you need features and
power on a budget, then read on. If you are new to MikroTik or RouterOS, this is going to

astound you.

Who or What is MikroTik?

Located in Riga, Latvia, MikroTik was founded in 1995 to develop routers and wireless ISP
systems. Latvia is a member of the European Union and is nestled on the Baltic Sea between
Estonia and Lithuania. With more than seventy employees at the time of this writing, MikroTik
is a growing company with a full-featured router operating system, RouterOS. In 2002,
MikroTik entered the hardware manufacturing field with the brand RouterBOARD.
RouterBOARD continues to develop new designs, targeting small companies, WISPS
(Wireless Internet Service Providers) and wired ISP’s (Internet Service Providers) looking
for high performance, small footprint and a powerful feature set.

Tuesday, February 10, 2015

Having A Successful Job Interview

Having a Successful job interview

                The goal of a job interview is to sell yourself. Many of the same question are asked by interviewer again and again. Therefore, the best way to sell yourself and have a successful interview, is to prepare answer that are honest and tell the interviewer what they need to hear. The good interviewers know which question to ask how the to find out not only about the applicant’s skills, but also about applicant’s thought. Here are some of the question and some of possible responses given by Raymond P. Harrison, a vice president in the Philadelphia Office of Drake Beam Morin Inc., an international consulting firm.

1)      Tell me about you.

Keep your answer to one or two minutes, don’t ramble. Cover four segments

A.     Education

B.     Work

C.     Experience

D.     Recent time

2)      What do you know about our company?

Don’t say you don’t know much. You should stat that you would like you know much.

A.     Products

B.     Size

C.     Income

D.     Reputation

E.      Goal

F.      Problem

G.     Management

H.     Style

I.        Background of their company

3)      Why do you want to work for us?

You wish to be part of a company project; you would like to solve a company problem ; you can make a definite contribution to specific company goals.

4)      What can you do for us that someone else cannot?

Relate past experience that represents success in solving previous employer problem that may be similar to those of the prospective employer.

5)      What do you look for a job?

Keep your answer opportunity-oriented. Talk about the opportunity to perform and be recognized

6)      How long would it take you to make a meaningful contribution to our firm?

Be realistic and say six months to one year

7)      You may be overqualified or too experienced for the position we have to offer

Good companies need useful, experienced people. The employer will get a faster return on investment because you have more experience than required. Emphasize your interest in a long-team association.

8)      Why are you leaving your present job?

Stick to one response. Don’t change answer during the interview. It is possible that

“Our office is closing” or “We agreed to disagree.”

9)      How do you feel about leaving all of your benefits?

“Concerned but not panicked.”

10) How would you evaluate your present firm?

“An excellent company offered me many fine experiences.” it is important not to bad mouth about employers or bosses. Bad mouthing tends to reveal more about you than about those who are the object of your comment

11) Why haven’t you found a new position before new?

Finding a job is easy finding the right job is more difficult.

12) If I spoke to your previous boss, what would he say about your greatest strengths and weaknesses?

This “threat of reference check question almost always produces honesty. it is important, in your response, to “be honest but not too negative.”



13) What are your weak points?

Don’t say you have done. Turn a negative into a positive answer: “I’m sometime important but I try to calm myself.

14) What was the last book you read? Movie you saw? Sporting event you attended?

Talk about leisure books to represent balance in your life.

At some point in every interview, the interviewer would ask the applicant if he has any question. It important that the applicant has some question-and some good ones-because question can reveal as much about the applicant as answers.

            Finally

Ø Here are some good question to ask the interviewer when the time comes:

a.      Why is the position open?

b.      What advantage do you want to see differently from the previous person and the new one who fills this job?

c.       What is the most pressing prose problem? What would you like to see in the next 2 to 3 months?

d.      Where has a person who is successful in this position gone?

Thanks you…!!!