How to connect TP-Link wireless IP camera to router wireless

Before you can configure wireless camera to connect to your router wirelessly, you need to get the following information first. Usually you can find them on your wireless router. If you don’t know how to get it, please contact the representative of your wireless router.

1. The SSID, or the network name of your wireless router
2. Wireless security settings on your wireless router.

After gather the information above, you can follow the steps below to configure the camera.

 

Step 1 Using an Ethernet cable to connect the camera to the LAN port of the wireless router first. We need wired connection to configure the router at the very beginning.

 

Step 2 On a desktop or laptop which is connected to the same wireless router, open Intelligent IP Installer (you can found it in the disk) and then highlight your camera.

Click Link to IE button, IE will automatically started and the login window will be prompted. Type in the username and password, you will be able to see the web configuration interface.

 

 

Or as now you know the IP address of the camera, you can manually type in the IP address in the address bar of other web browser such as Chrome.

 

Step 3 Go to SETTING->BASIC->Network->Wireless page. To enable wireless function, check the option on.

 

 Step 4 Click Refresh button, all the available wireless APs will be listed in the wireless network box. Highlight on your wireless router’s network name. Then fill in following content:
1. Select the corresponding Authentication, Encryption and type in the correct Passphrase or password which should match with the wireless settings in your wireless router.

If you are not sure about the information, please contact with the representative of your wireless router.

 

2. Select Obtain an IP address automatically (DHCP) and Obtain DNS server addresses automatically. Click OK and the camera will start to connect to the router wirelessly.

 

 

Step 5 After connect successfully, you can check the IP address assigned by the wireless router. There are mainly three methods you can use to check it.

Method 1: You can see IP address comes up in the wireless setting page of the IP camera.

 

 Method 2: Use Intelligent IP Installer. A new IP address comes up in the list after the IP camera was connected to the wireless router successfully.

 Method 3: Check the DHCP clients list in the web management page of your wireless router.

 In Step 4, you can also assign an fixed IP address for the camera. Just choose use the following IP address and enter IP address, subnetmask, gateway and DNS information accordingly. Just keep in mind that the IP address you assigned to the camera should not be taken by other devices in your home network.

 

 Step 5 Unplug the Ethernet cable and the camera is now connected to wireless router wirelessly. You can use any of your desktop and laptop in the network to surveillance the camera now.

Read more »

Posted in: Configure Camera

PTZ Configuration Guide for TurboView Systems

This guide assumes that the PTZ camera is showing video; if it is not, double check your video and power connections or call 866-241-3400.
For a PTZ camera to be able to be controlled by a DVR, the camera and controller MUST be speaking the same language (Called "protocol") and speed (called "baud rate"). The two must be physically connected using two-conductor wire running from the RS485+ and - ports on the DVR to the camera. Lastly, the DVR must be sending signals using the correct camera address.

Technical Support Is Available

Should any step of this guide fail or should you require additional assistance please contact technical support at 866-241-3400.

How to connect your PTZ Camera to a TurboView System

Step 1

Begin by verifying the connection from the camera to the controller. Ensure that your two-conductor cable is securely connected to the RS485 wires on the camera side, and that you know for certain which is positive and negative.

Step 2

Power cycle the camera (Unplug power to it, then plug the power back in). All current EZ Watch Pro PTZ cameras will display their current Protocol, Baud Rate, and Address during their powerup cycle. The protocol is typically "PELCO-P" or "PELCO-D" (May be seen as "P-P" or "P-D" respectively). Baud Rate for Pelco-P is normally 9600; for Pelco-D it's usually 2400. Ensure you have the Protocol, Baud Rate, and Address written down.

Step 3

JOYSTICK: (If you are not planning to use a PTZ Joystick and only control the camera from the DVR, please skip to step 7) If you are using a joystick controller, plug the RS485 wires into the joystick controller on the back.
For the EZ Watch Pro AU40E, there will be green terminals you can secure with a screw; slide the RS485 + and - into their appropriate terminals and tighten the screw with a phillips screwdriver.

Step 4

On the back of the AU40E joystick, there is a bank of 8 dip switches. If your camera is using Pelco-P 9600, set switches #3 and #6 to the down, or "on" position. If your camera is using Pelco-D 2400, set switches #1 and #2 to the down, or "on" position. All other switches should be left in the up, "off" position.

Step 5

Plug in power to the joystick, or power cycle the joystick if it's already plugged in. Set the joystick to control the correct camera address by typing in the number then hitting the "cam" button*.
*Note: EZ-TRACK PTZ Cameras that are set to the Pelco-P protocol may incorrectly display their camera address as one lower than it is. If the EZ-TRACK camera shows address 00, then it is controlled as camera 01.

Step 6

The AU40E joystick should now have control. If you have difficulty controlling the camera, double-check all settings and wiring and try again.

Step 7

TurboView DVR : Run two-conductor wire from the back of the joystick (If present) or from the camera into the RS485 ports on the back of the TurboView DVR. RS485+ from the joystick/camera must plug into the TX+ port, while RS485- from the joystick/camera must plug into the TX- port.
To plug a wire into the port, hold in the orange tab with a small flat screwdriver and slide the wire into the green port. Release the orange tab and tug gently on the back of the wire; if you have a good connection, the wire will be unable to pull free from the back.

Step 8

Enter the DVR Menu (Default username is "Admin", default password is "1111"). Go right twice to the "Devices" section, and hit enter on "Camera/PTZ".

Step 9

Check the camera number that the camera appears on in your TurboView Monitor (Note: This can differ from the address). In the "PTZ" section, hit Enter to change the protocol until it matches the one of your camera. Use the arrows next to the ID number to adjust the IDuntil it matches your camera's address. If you do not know the camera's settings please see step 2 above.

Step 10

Highlight the "..." button under Set., and hit enter. Change the Baud Rate to match your camera, then hit OK (Silver units : The OK button is the icon of a diskette).

Step 11

Hit "OK" at the bottom of the Devices screen to save your changes. Exit the menu by hitting "Esc" to return to the admin icon, then choose the "Exit" option from the menu.

Step 12

To control the camera, bring it up fullscreen in front of you. Press the "PTZ" button on the remote control, and a small dome camera icon should appear in the bottom-right corner of the screen. You should now be able to control the camera and adjust the zoom/focus using the buttons on your remote control.

Setup Complete!

You should now be able to control your PTZ camera through the EZWatch Pro software interface.

Read more »

Posted in: Configure Camera

PTZ Camera Controller Setup

Configure PTZ Camera

First, following these setup instructions to configure the PTZ camera.  This link will open up a new window so that you can easily return to this page to continue with the controller setup when you are done.

Configure PTZ Camera Controller

Next, configure the camera controller by following these setup instructions.

1. If you have not already done so, connect the video output of the PTZ camera (BNC connection) to your DVR or video monitor. 

2. Run the other end of your RS 485 cable to the PTZ controller and attach as seen below. *Note: The positive terminal on the controller is on the left. 

3. Adjust the protocol and baud rate switches on your controller to match the pitcure below.

Switches 1,2,4,5 should be set to the Off position.
Switches 3,6,7,8 should be set to the On position.

4. Plug in the PTZ controller into a power source using the power supply that the controller came with.

5.Plug the PTZ controller into a power source using the power supply that the camera came with. 

6. After the camera initializes, type the following into the PTZ keyboard to gain control of the camera that you just configured: 0 (zero), 2 (two), CAM, ON  (in that order as seen below).  This tells your controller that you want to control camera ID #2 that your keyboard is attached to. 

 
Important - Although we configured the address of the camera to be ID #1, your keyboard recognizes the camera as ID #2.  Be sure to increment your ID by one on the controller.  So if your next camera is ID #2, you will control this camera on your PTZ keyboard by initializing camera #3 by pressing: 0 (zero), 3 (three), CAM, ON.

You should now be able to control your camera using your PTZ controller / keyboard.

Read more »

Posted in: Configure Camera

PTZ Camera wiring and setup with DVR (no controller)

Before You Install The Camera:
Test it out!  Do not install the PTZ in its final location until you have tested the power, video signal and functionality (Panning, Tilting, and Zooming) of the PTZ.  It’s much easier and less time consuming to troubleshoot connectivity issues before you do your run than after.
Setting up Video & Power:
You’ll need the PTZ, the 24V power supply that came with your PTZ, a DVR and a coaxial cable with female BNC adaptors on each end and a very small flathead screwdriver to get started.
1)      Connect your PTZ to Channel 1 on your DVR via the coaxial cable.
2)      Using the very small flathead screwdriver, loosen the positive and negative terminals on the ‘Power Input’ coming from the PTZ.
3)      Slide the red end of your 24V power supply into the positive terminal on the PTZ and the black end of your 24V power supply into the negative terminal on the ‘Power Input’
4)      Tighten both terminals with the flathead screwdriver and plug in the power adaptor to a wall outlet.  Your PTZ should power on and you should see and image on Channel 1.
If everything is setup properly the connections from your PTZ should look like the following:

Setting up RS-485 Connections on the Camera:
5)      Using your flathead screwdriver, loosen the middle two terminals on the PTZ’s ‘RS-485 Connector’.  Connect two exposed ends of a twisted pair cable into the terminals.  Connect the solid colored end to the Blue/White D+ terminal and the striped end to the Black D- terminal.  Tighten both terminals on the ‘RS-485 Connector’.
If everything is setup properly the connections from your PTZ should look like the following:

Setting up RS-485 Connections on the DVR:
6)      There are two types of RS-485 connections on iVigil DVRs.  One type is a green sensor panel with two RS-485 ports.  The second type is an I/O (Input/Output) ribbon with two RS-485 cables.  Consult the manual of your DVR or the image below to determine which type of connections you’re working with.  Connect your positive end to Port or Ribbon Cable A and your negative end to Port or Ribbon Cable B.  Again, if you’re stuck check your manual or the image below.
If everything is setup properly the connections from your PTZ should look like the following:

A= Positive   B= Negative
Setting up the DVR:

Silver/Topeka DVR:
7)      On your DVR go to the Main Menu > Link > PTZ and under Channel 1 change:
Model:             PELCO D-TYPE
Speed:                         2400
ID:                    1
8)      Exit the menu saving your changes.  Press the PTZ button on the front of the DVR and if everything is setup properly you should be able to control of your PTZ!
Black DVR:
7)      On your DVR go to the Menu > Main Menu > PTZ & RS-485 Setup and under Channel 1 make sure the ‘Enable PTZ’ checkbox is checked and the following settings match:
Protocol:          Pelco D
PTZ ID:             1
Baud Rate:      2400
8)      Select ‘OK’ to exit the menu and save your changes.  Power on your PTZ, press the PTZ button on your remote and if everything is setup properly you should be able to take control of your PTZ with your remote!
Troubleshooting:
1) I’m not getting any video signal on my DVR:

Double check your video connections on the DVR, the power connections and terminals on your PTZ ‘Power Input’ cable, and your 24V power transformer is plugged into a wall outlet.
If both the video and power connections are sound and the PTZ is turned on you should be getting a video signal.
Make sure your monitor is connected and powered.
2) My PTZ isn’t getting any power / MY PTZ isn’t turning on:

Redo steps 2,3 and 4 from the first section “Setting Up Power & Video” making sure the terminals connecting the power supply to the PTZ are tight.
Try a different wall outlet for the 24VDC adapter and if you’re still having trouble make sure the green piece you can see in Figures 1 & 2 is secure.
Make sure that all fuses are still intact if you’re using a power box to power the PTZ.
3) I cannot control my PTZ

Double and Triple check you’ve followed every step of this guide exactly.  If you miss even one detail of one step you may not be able to control your PTZ.
Check if the positive and negative RS-485 (Twisted Pairs) wires are switched: positive on the DVR goes to negative on the PTZ or vice-versa.  Double check that the solid colored twisted pair is connected to the positive on both ends and the color/white wire is negative.
Gently tug on the twisted pairs at the DVR and PTZ’s terminals to ensure they are secure and snug.
Make sure your settings in the DVR are correct (Protocol, PTZ ID, Baud Rate) and correspond to the dip switch settings in the PTZ (See pages 8-10 in your PTZ manual for more information on dip switch settings).

Read more »

Posted in: Configure Camera

How to configure IP Camera Remote Access

Remote access is often a key factor when choosing a security camera. The ability to monitor a location remotely is a huge benefit for most and is often the main reason for selecting an IP camera.
However, the act of setting up remote access can often be very confusing for non-technical users and can lead to difficulty. The process is actually very simple but does require some explanation.
Remote Access Steps:
1: Basic Camera Networking
2: Gather the right information
3: Set a static IP address
4: Setup Port Forwarding
5: Testing
6: Dynamic IP Addresses
7: Safety concerns - This is all safe… right?
8: Troubleshooting

1: Basic Camera Networking
Firstly we need to cover the basic setup of an IP camera.

Most people will connect their IP camera to a standard Ethernet router alongside other computers and network devices. All devices will then gain access to the Internet through the router. There are no restrictions on outgoing data unless you set them within your router.
However the same is not true in the opposite direction. Routers contain a firewall which prevents anyone using the Internet from accessing your local network. This keeps your computer and local devices safe from attack by hackers but also means that you can’t connect to your camera.
Port forwarding (sometimes called port mapping or virtual servers) is the method which tells your router that you want to allow access from the Internet to a device on your network without allowing access to other devices.
2: Gather the right information
In order to set up port forwarding you will need to gather some network information, namely the IP address of your camera, internal IP address of your router, external IP address of your router and the port number to be used. Use the following techniques.
Internal IP address of your router and subnet mask
To access this information in Windows XP, go to the Start menu and click on “Run”. In the box that opens, enter “cmd” and click “OK”. In Windows Vista and Windows 7, click the Windows icon and in the search box enter “cmd” and press enter.
The Windows command window should now appear. Type in “ipconfig” and press enter. The computer will then churn out your network information for your computer. If you are using a wireless connection between your computer and router look for “Ethernet adaptor local Wireless connection”; if you are connected by a wire then look for “Ethernet adaptor local area connection”.
Once you have the right area, look for the default gateway. It should be something similar to 192.168.0.1. If you find more than one and cannot decide which one is correct, try entering the IP address into a web browser. Whichever is the correct IP address should bring up your routers web page.
In the command window you will also see the subnet mask. Make note of this as you will need it later.
This is specified from within the camera’s web interface in the settings page. By default the port number should be set to 80. If you are using more than one then you need to change this but otherwise I would leave it alone. If you do want to change the port number it is best to choose a number over 8000.

External IP address of your router
To get the current external IP address of your router, go to www.whatismyip.com . Watch out though as this may change. See dynamic DNS below for details.
3: Set a static IP address
If you do not know what your camera’s IP address is you can usually find out by using the manufacturers search software. However, by default most IP cameras use DHCP to locate themselves on your network. This provides quick setup but also means that the IP address of the camera can change at any point. Once your port forwarding rule is set up, any changes in the IP address will break the rule and you will not be able to access remotely.
To prevent this, you need to set a static IP address in your camera. To do this, log into your camera and go into the network settings page. There should be an option there that says something similar to “Obtain an IP address automatically”. Un-tick this and enter a suitable IP address.
If you don’t know which IP address to use we would advise using the one that the camera is currently on. To check this, have a look at the address bar at the top of your page when logged into your camera. The address should be something similar to 192.168.0.253.
In addition to your IP address you need to specify a subnet mask and default gateway. You gathered this information earlier so enter it as required.
You may also be asked to enter a primary and secondary DNS server. Unless you have been told differently by your ISP, enter the IP address of your default gateway address into the primary DNS server box. You can leave the second server blank.
Once you have all the information entered, save the changes and restart the camera. Test the IP address by typing it into a web browser once the camera has fully powered up.
4: Setting up port forwarding
Obviously we can’t go through configuration on all routers, the keyboard wouldn’t take it. However, there is a common way to set up port forwarding on all routers.
Think of the port forwarding table on your router as a phone book. When you want to know which number to call you scan through the names until you find one that matches and dial that number. In this case the router scans through the port numbers until it finds one that matches and then sends the information onto that address.
When entering a port forwarding rule you are often asked to enter the start and end ports. With the camera being on a single port just make them identical. The same goes for external ports if you are asked for them. Some will also ask you what type of traffic you want to allow, either TCP or UDP. You should allow TCP.
Be aware that sometimes you have to set up a rule in two steps. In these instances you have to create a service first which just adds a name for your ports before you specify IP address. Additionally you can have a look at Portforward.com.This website offers visual walkthroughs of most common routers. Just select your model and select the default guide for a basic walkthrough of how it is done.
5: Testing
Once the rule is created you need to test it. To access your camera remotely type http://external_ip_address:port into a web browser. Note that if you are using port 80 you can leave out the “:port” and still access your camera.
Don’t try to connect yourself. You may encounter an effect called NAT loopback. Some routers do not allow you to access a local device using the external IP address of your router and will act as if the rule is incorrect.
The best way to check that port forwarding is set up correctly is to try from a friend or relative’s computer. Alternatively you can check using a GPRS Internet connection or cell phone but be aware that these can sometimes provide inaccurate results.
6: Dynamic IP addresses
We get the same question a lot here at Network Webcams Tech HQ; Do I need a static IP address on my Internet connection? The answer in most occasions is no. Most cameras come with a dynamic DNS client which allows you to set up a unique name which will always point to your current IP address.
7: Safety concerns - This is all safe… right?
Allowing access through my firewall? That doesn’t sound safe! Well, although you are allowing access through your firewall, you are doing so in a very controlled manner. Anyone accessing from the Internet will only have access to the devices you have set up on the port forwarding screen and even then will only be able to access on certain ports. For example, if you only allow access on port 80 you can’t access the same device on port 21.
However, because you have opened your camera up to the Internet you do need to make sure that a secure password is used. Don’t leave the default password on your camera as it really isn’t that difficult to work out which camera is being used and try the default password.
8: Troubleshooting
No matter how many times you have set up port forwarding sometimes things do go awry. Double check the settings you have entered and if necessary restart the router. If you still have problems take a look at the following areas.
Default Gateway
The default gateway is essentially the place where your camera will look to access the Internet. If this setting in your camera is missing or incorrect, the camera doesn’t know where to send Internet information to. In 99% of all network configurations the default gateway is the internal IP address of your router. To confirm this address, check the network settings by using the cmd window as shown above.
Hopping Port Forwarding
I have seen a number of occasions where people have been using more than one router on the same connection. It’s always a bad idea using more than one router per Internet connection unless you are a very advanced user. Keep things simple and it’ll be a lot easier to port forward.
If you must use more than one router then you need to set up port forwarding on each device to pass information from one router to the next. This is very tricky and should only be used as a last resort.
Satellite links / ISP blocking
There are ISPs out there that block remote access on certain ports. It’s very common on GPRS and satellite links and will often prevent access from the Internet completely. If you have a lot of trouble accessing it’s a good idea to give the ISP a call to confirm with them what you are doing is possible. Sometimes a change of port number to something other than 80 can sort things out.
NAT Loopback
A very common fault is encountered when people try to use the external IP address of the router to access their camera while accessing through the same router. This is often not possible due to NAT loopback.
NAT loopback happens when you try to access a local device using the external IP address or domain name. Some routers allow you to do this and some don’t. Check the user manual for your router as it should give you some indication. If Loopback isn’t supported then it will appear as if the system isn’t working.
The best way to check that the port forwarding is working correctly is to view from an external network such as one belonging to a friend or relative, or to use a GPRS connection or mobile phone web browser.

Read more »

Posted in: Configure Camera

How to Remote Camer Security over the internet or network

What is the difference between local and Internet / remote network surveillance?

Local network surveillance uses applications or web browsers over a Local Area Network (LAN) to access video from network-enabled video devices. The video signals are not transmitted over the Internet, and there is no special setup required.

 

A LAN is a group of associated computers and devices which generally shares one connection to the Internet. In the figure above, the DVR system and IP camera on the left are connected to the LAN. The computer and laptop on the right are connected to the same LAN through the same router, so they can both access video from the devices on the left without having to connect over the Internet. Devices can share the same LAN using either wired or wireless connections.
Remote network surveillance generally uses the same applications or web browsers to access video, but from a remote location that is not connected to the LAN. The video signals must be transmitted over the Internet, and remote access setup is required.

In the figure above, the DVR system and IP camera are connected to the Internet via the router. This enables the computer and the mobile phone to connect to the system from a remote location over the Internet. The DVR system, IP camera, and the router must be configured to share the video signal over the Internet. The computer and mobile phone must have Internet access and the appropriate application or web browser to connect to the devices.

How do I configure my Lorex system for Internet / remote network surveillance?

For Lorex products, instruction to set up connectivity over a local network or the Internet are in the Quick Start Guide. After the steps in the Quick Start Guide are followed, you can connect to your system from any compatible computer, smart phone, or tablet over the Internet to view the video from anywhere in the world.
The setup process varies from product to product, but the process to configure your Lorex system for Internet connectivity generally entails the following steps:

1. Connect your Lorex system to your router and connect to it over the Local Area Network (LAN).
2. Configure your router or Internet gateway for port forwarding.
3. Create a Lorex DDNS account to create a permanent web address for your system.
4. Connect to your system over the Internet.

How do I port forward my gateway or router?

This question depends on the particular model of router you have. Nearly all models support some form of inbound TCP/IP routing, or port forwarding, and there are many resources to help you to forward an incoming connection to your video device. We provide an exclusive Auto Port Forwarding Wizard (for PC only) that automates the port forwarding process and is compatible with a large number of router models and versions. You can also check our Port Forwarding a Router guide for instructions on how to manually configure your router or gateway or www.portforward.com for details on a large variety of routers.
NOTE: The information on www.portforward.com is not maintained or supported by Lorex. Please check the instruction manual for your Lorex system to determine which ports must be configured to enable a remote connection.

How do I find the model number and version of my router?

On most routers, the model and version number can be found underneath the router, printed on a sticker.

How can I test my port forwarding configuration?

There are third-party websites that provide free port forwarding testers, such as http://canyouseeme.org/ and the Port Forwarding Tester at http://www.yougetsignal.com/ These websites will find your external IP address and test if specified ports are open at that address.
NOTE: These websites are not supported by Lorex.

What is port forwarding?

Computers, DVRs, and other devices inside your network can only communicate directly with each other within the internal network. Computers and systems outside your network cannot directly communicate with these devices. When a system on the internal network needs to send or receive information from a system outside the network (i.e. from the Internet), the information is sent to the router.
When a computer on the Internet needs to send data to your internal network, it sends this data to the external IP address of the router. The router then needs to decide where this data is to be sent to. This is where setting up port forwarding becomes important.
Port forwarding tells the router which device on the internal network to send the data to. When you set up port forwarding on your router, it takes the data from the "external IP address:port number" and sends that data to an "internal IP address:port number" (for example, Router External IP 216.176.57.75:80 to DVR Internal IP 192.168.1.102:80).

What is Lorex DDNS?

Lorex DDNS allows you to assign a permanent web address or URL (Uniform Resource Locator) to your Lorex system. This means when you connect to your Lorex system, you use the Lorex DDNS address (for example, http://tomsmith.lorexddns.net), rather than your system's IP address.
This has two advantages over using an IP address to connect to your system:

1.   unless you have a static IP address, your IP address will change from time to time. Lorex DDNS service ensures that when the IP address of your system changes, it will automatically update the DDNS server with your system's new IP address. Please note that whenever your IP address changes, it takes a short time, typically a few minutes, for the DDNS servers to update with the new IP address.
2. You can connect to your system using an easy-to-remember web address, rather than a numerical IP address.

What is DDNS?

Dynamic Domain Name Service (DDNS) is a service used by a host system (such as a Lorex video surveillance system) to register its current external IP address (as provided by the Internet Service Provider) with the external DDNS system. The DDNS system associates the host system with a Universal Resource Locator (URL) to enable remote systems to connect to the system over the Internet.

What software do I need to remotely access video from my system on my computer?

This depends on which Lorex system you have. On the PC, all Lorex Vantage systems that support remote access are compatible with Internet Explorer. Some systems are bundled with remote client software, and some are compatible with other Internet browsers. Please note that you may need to install plugins to remotely access your system using an Internet browser.
On Mac, some systems are compatible with the Safari browser and some are bundled with client software. Please note that you may need to install plugins to remotely access your system using the Safari browser.
All Lorex remote client software is provided free of charge and is available as a free download from your system's product page. Check the Remote Connectivity Compatibility Chart and App List for a detailed list of browsers and client software applications that are compatible with each system.

Can I connect to my system using a smart phone or tablet?

Yes, smartphone and tablet applications are available for most Lorex systems. Check the Remote Connectivity Compatibility Chart and App for a detailed list of smartphone and tablet applications that are available for each system, as well as download links and how-to-videos.
Lorex smartphone and tablet applications are provided free of charge, but you need a mobile data plan from your service provider to access your Lorex system over a mobile network. When using a mobile network, data charges may apply. Check with your service provider for details.
Please note that you must complete the process to set up remote viewing that is detailed in the Quick Start Guide before you can access your system using a smartphone or tablet. Also, features vary between different smartphone or tablet applications.

How do I find my system's IP and MAC address?

In most Lorex systems, you can find your system's IP and MAC address using the System Information screen. This is often available by pressing the Enter button () on the front panel of DVR systems; however, this varies between systems. Check your system's instruction manual for more details.

What is a MAC address?

The Media Access Control (MAC) Address is your device’s 12-digit hardware address that identifies the device on a LAN. A MAC address is unique to each network device.
MAC Addresses follow a specific format: mm-mm-mm-ss-ss-ss. The mm’s are the manufacturer’s ID number and the ss’s identify the product’s ID number.
You MAC address is necessary when registering for Lorex DDNS because it identifies your specific product to the DDNS servers.

What is an IP address?

Computing devices connected to a network, such as a LAN or the Internet, are assigned a numerical address. This number is called an IP address (IP stands for Internet Protocol). Each IP address consists of 4 numbers in the range 0-255, and is written as: aaa.bbb.ccc.ddd (e.g. 216.176.57.75).

What is the difference between an internal and external IP address?

Every device that communicates over the Internet must have a unique IP address. These are called external IP addresses (sometimes referred to as public IP addresses). However, there are ranges of IP addresses that are excluded from this address space, so that they can be used internally by devices connected to Local Area Networks (LANs). These are internal IP addresses (sometimes referred to as private IP addresses). If devices that are using internal addresses wish to communicate with devices on the Internet, they must pass their messages through a network gateway, which will map the internal IP Addresses into a valid external IP address. This is called Network Address Translation (NAT), as shown in the following figure.

How can I find my external IP address?

If you wish to find your external IP address, you can use a third-party website such as www.showmyip.com. Your external IP address can also be found within your router settings. Refer to your router’s instruction manual for further details.

What is the difference between static and dynamic IP addresses?

IP addresses are the numbers used by the Internet Protocol (IP) to identify your computer or device. Every computer or device that wants to communicate over the Internet must have an address, unique to that computer or device.
Internet Service Providers (ISPs) can issue IP addresses in two ways:

• Static assignment: The ISP issues a permanent, non-changing address that must be manually entered into the computer or device. This number cannot be used by any other device.
• Dynamic assignment: The ISP uses a protocol called Dynamic Host Configuration Protocol (DHCP) that generates an IP address and leases (i.e. provides) it to your computer or device for a predetermined length of time. After that time expires, your computer or device must request a new IP address. This means that your external IP address will change occasionally. Most residential Internet service packages use dynamic assignment.

Check with your Internet Service Provider (ISP) to determine whether your IP address is static or dynamic.

Read more »

Posted in: Configure Camera

How to Connect & Use a Remote Video Security Camera

Installing a security camera can mean peace of mind.

A network camera lets homeowners monitor areas inside and out of their homes and grounds, transmitting live images of the chosen site that they can watch from any computer that has Internet access. Installing a security camera is simple, as long you pay attention to your user manuals. Your security camera's instructions will guide you in setting up an IP address for your camera feed. According to Home Security Guru, a web resource for home security: "Understanding basic home security best practices could mean the difference between keeping your home safe and becoming the victim of a break-in."

 

• Choose the optimal location for your camera and mount it. Place it close to a power outlet and your wireless Internet router. The camera's cable will need to reach both. Your camera's mounting equipment will include a rod to connect to the camera, which attaches to a base. Screw the base to the wall with the screws that come with the camera mount, and connect the camera to the rod. Some camera models do not mount to a wall at all, but do nestle in a cradle like a phone. Setting up your camera's view after you have it connected to the Internet may take some trial and error.
• Plug the camera's supplied A/C power cord into the outlet. Connect the network cable that comes with the router to the designated port on its back side. Plug its other end into the camera.
• Install the software that came in your camera equipment package onto whatever computer you have connected to your router. This is to establish a connection with the camera. The procedure will vary, depending on your manufacturer and model, but will involve getting the camera's IP address from your manual or the body of the camera and entering it on the computer. Create passwords and user information as the computer prompts you to.
• Go to a computer somewhere outside your home to test your ability to access the camera's live feed remotely. Type your camera's IP address into the browser bar. This should bring up your camera's menu. Enter your user name and your password when prompted. You can now watch your site from any computer.
• Practice using your camera from a remote location. Depending on your camera's capacities, see your user manual to practice watching in real time, recording and storing video of the site, zooming, moving around corners, etc.

Read more »

Posted in: Configure Camera

Configuring an Access Point as a Wireless Bridge

Linksys Wireless-G Access Points can be configured as an Access Point, Access Point Client, Wireless Repeater, and Wireless Bridge. The Wireless Bridge mode will turn the access point into a wireless bridge. Wireless clients will not be able to connect to the access point in this mode.
NOTE: When an access point is configured as a wireless bridge, it will link a wireless network to a wired network allowing you to bridge two networks with different infrastructure.



NOTE: When the WAP54G access point is set to wireless bridge mode, it will only communicate with another Linksys Wireless-G Access Point (WAP54G). 
To configure an access point as a wireless bridge, you need to perform three steps:

1. Checking the Wireless MAC Address of an Access Point
2. Setting-Up Wireless Bridge Mode on the WAP54G
3. Changing the LAN IP Address of the Wireless Bridge 

Checking the Wireless MAC Address of an Access Point
NOTE: The following steps will be performed on the main access point using a wired computer.

Step 1:Connect a computer to the access point.


Step 2:Assign a static IP address on the computer. For instructions, click here.
NOTE: To assign a static IP address on a wired Mac, click here.
Step 3:
Open the access point’s web-based setup page. For instructions, click here.
NOTE: If you are using Mac to access the access point’s web-based setup page, click here.
Step 4:When the access point’s web-based setup page opens, take note of the Wireless MAC Address.


NOTE: The Wireless MAC Address you took note of will be entered on the WAP54G set as wireless repeater.
Step 5:After obtaining the wireless MAC address of the access point, configure the other WAP54G as a wireless bridge. For instructions, follow the steps below.

Setting-Up Wireless Bridge Mode on the WAP54G

Step 1:Connect a computer to the access point you want to configure as a wireless bridge. 


Step 2:Assign a static IP address on the computer. For instructions, click here.
NOTE: To assign a static IP address on a wired Mac, click here.
Step 3:Open the access point’s web-based setup page. For instructions, click here.
NOTE: If you are using Mac to access the access point’s web-based setup page, click here.
Step 4:When the access point’s web-based setup page opens, click AP Mode.


NOTE: The access point’s web-based setup page may differ depending on the access point’s version number.
Step 5:Select Wireless Bridge and type the remote access point’s MAC address that you took note of earlier.  


NOTE: Remove the colons (:) when typing the MAC address on the Remote Access Point’s LAN MAC Address field.
Step 6:
Click .

Changing the LAN IP Address of the Wireless Bridge

After configuring the access point as a wireless bridge, change its LAN IP address to avoid IP address conflict.

Read more »

Posted in: Configure Camera

Wireless Bridges Point-to-Point Link Configuration

Introduction

This document describes how to establish a point-to-point wireless link with the use of Cisco Aironet Wireless Bridges with Cisco LEAP authentication.

Prerequisites

Requirements

Ensure that you have basic knowledge of these topics before you attempt this configuration:

• Configuration of basic parameters on the wireless bridge
  
• Configuration of the Aironet 802.11a/b/g Wireless LAN (WLAN) Client Adapter
  
• Extensible Authentication Protocol (EAP) authentication methods
  

Components Used

The information in this document is based on these software and hardware versions:

• Two Aironet 1300 Series Wireless Bridges that run Cisco IOS^® Software Release 12.3(7)JA firmware
  
• Two Aironet 802.11a/b/g Client Adapters that run firmware version 2.5
  

Note: This document uses a wireless bridge that has an integrated antenna. If you use a bridge which requires an external antenna, ensure that the antennas are connected to the bridge. Otherwise, the bridge is unable to connect to the wireless network. Certain wireless bridge models come with integrated antennas, whereas others need an external antenna for general operation. For information on the bridge models that come with internal or external antennas, refer to the ordering guide/product guide of the appropriate device.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

This document uses this network setup:

This setup uses two Aironet 1300 Series Wireless Bridges. One of the bridges is configured for root bridge mode and the other bridge is configured for non-root bridge mode. Client A associates with the root bridge and Client B associates with the non-root bridge. All the devices use IP addresses in the range 10.0.0.0/24, as the network diagram shows. This configuration establishes a point-to-point wireless connection between the bridges. Before the wireless bridges can communicate, they must authenticate to each other. The bridges use any one of these authentication methods:

• Open authentication
  
• Shared Key authentication
  
• EAP authentication
  

This document uses LEAP for authentication and uses the local RADIUS server on the root bridge in order to validate the credentials.
Note: This document does not explain how to configure the client adapter to associate with the wireless bridges. This document focuses on the configuration of point-to-point connectivity between the root and non-root bridges. For information on how to configure the wireless client adapter to participate in a WLAN, refer to Basic Wireless LAN Connection Configuration Example.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Background Information

A wireless bridge is a Layer 2 device that connects two or more LANs, which are often in different buildings, through the wireless interface. Wireless bridges provide higher data rates and superior throughput for data-intensive and line of sight applications. High-speed links between the wireless bridges deliver throughput that is many times faster than the E1/T1 lines for a fraction of the cost. In this way, wireless bridges eliminate the need for expensive leased lines and fiber-optic cables. You can use the wireless bridges to connect these networks:

• Difficult-to-wire sites
  
• Noncontiguous floors
  
• Temporary networks
  
• Warehouses
  
• Other networks
  

The LANs that the wireless bridge connects can connect to the wireless bridge either through the wired LAN or through the wireless interface. You can configure the wireless bridges for point-to-point and point-to-multipoint applications. This document configures the wireless bridges for point-to-point connectivity.

Configure the Root Bridge

GUI Configuration

This section presents the information to configure the wireless bridge as a root bridge.

1. Access the 1300 wireless bridge through the GUI and go to the Summary Status window.
   Complete these steps:
   
   1. Open a web browser and enter the IP address in the address line.
      This example uses the IP address 10.0.0.1 for the root bridge. For information on how to assign an IP address to the wireless bridge, refer to the Obtaining and Assigning an IP Address section of the document Configuring the Access Point/Bridge for the First Time.
      
   2. Press Tab in order to bypass the Username field and advance to the Password field.
      The Enter Network Password window displays.
      
   3. Enter the case-sensitive password Cisco, and press Enter.
      The Summary Status window displays, as this example shows:
      
      
2. Configure the radio interface.
   
   1. Enable the radio interface and define it as a root bridge.
      This radio interface acts as the wireless interface for the root bridge.
      Note: The radio interface is disabled by default on 1300 wireless bridges that run Cisco IOS Software Release 12.3(7)JA.
      Complete these steps:
      
      1. Choose Network Interfaces > Radio0-802.11G > Settings.
         The Network Interfaces: Radio0-802.11G Settings window displays. You can use this window to configure various parameters that relate to the radio interface. These parameters include:
         
         • Role in the radio network
           
         • Radio data rates
           
         • Radio transmit power
           
         • Radio channel settings
           
         • Antenna settings
           
         • Other parameters
           
      2. Click Enable under Enable Radio in order to activate the radio interface.
         
   2. Enable root mode on the wireless bridge.
      
      1. Under Role in Radio Network, click Root Bridge.
         Note: The Role in Radio Network parameter allows you to configure the wireless bridge in these ways:
         
         • Root bridge
           
         • Non-root bridge
           
         • Root bridge with wireless clients
           
         • Non-root bridge with wireless clients
           
         • Root access point (AP)
           
         • Repeater AP
           
         • Workgroup bridge
           
         • Scanner
           
         • Install mode
           
         If you want to configure the wireless bridge for root bridge/non-root bridge mode and you have wireless clients that are associated to the wireless bridge, you need to choose either Root Bridge with Wireless Clients or Non-Root Bridge with Wireless Clients for the Role in Radio Network parameter. In this way, the wireless bridge functions as a root/non-root bridge and also accepts wireless client associations.
         
         Note: If you use an IEEE 802.11b standard bridge or have 802.11b clients with the 1300 wireless bridge, ensure that you do not choose Require for the Orthogonal Frequency Division Multiplexing (OFDM) data rates. If you choose Require for these data rates, the devices do not associate. The devices do not associate because the 802.11b devices do not support OFDM rates that operate based on the IEEE 802.11g standard. In the Network Interfaces: Radio0-802.11G Settings window example, the OFDM data rates appear with an asterisk (*) beside the rates. The settings in this example also show you how you must configure the data rates for 802.11b devices that operate in a 802.11g environment.
         
      2. Enter 1 for the Distance (Km) parameter, leave all the other parameters at their default values, and click Apply at the bottom of the window.
         
         Note: This document explains the point-to-point configuration with integrated (nonremovable) antennas that are placed close to each other. The bridges are less than 1 kilometer (km) apart. For this reason, all the other radio parameters are left at their default values. A configuration of other parameters can be necessary, however. The necessity of the configuration of other parameters depends on the environment in which these wireless bridges are deployed and the type of antenna that you use. These are other parameters that you may configure:
         
         • Antenna gain
           
         • Radio distance
           Note: This is the distance between the bridges.
           
         • Definition of the transmit and receive antenna
           
         • Power level that is used for communication
           
         • Other parameters
           
         Note: Refer to the Outdoor Bridge Range Calculation Utility in order to calculate these parameters. Always use this utility before you deploy the bridges in order to ensure good throughput and performance. For more information on how to configure the other parameters of the radio interface on the wireless bridge, refer to Configuring Radio Settings.
         
3. Enable LEAP authentication with a local RADIUS server in order to authenticate the wireless bridges.
   Configure LEAP authentication on the root bridge, and then configure the non-root bridge as a LEAP client in order to authenticate to the root bridge. Complete these steps:
   
   1. Choose Security > Server Manager in the menu on the left, define these parameters under Corporate Servers, and click Apply:
      
      • IP address of the RADIUS server
        Note: For the local RADIUS Server, use the IP address of the AP. In the example, the IP address to use is the IP address of the root bridge, which is 10.0.0.1.
        
      • Authentication and accounting ports
        
      • Shared secret of the RADIUS server
        Note: In the example, the shared secret is Cisco.
        
      
      Note: The local RADIUS server listens on ports 1812 and 1813.
      
   2. In the Default Server Priorities area of this window, select the local RADIUS server IP address and click Apply.
      
   3. In order to enable WEP encryption, complete these steps:
      Note: LEAP authentication requires WEP encryption to be enabled.
      
      1. Choose Security > Encryption Manager.
         
      2. In the Encryption Modes area, choose Mandatory for WEP Encryption and choose WEP 128 bit from the drop-down menu beside Cipher.
         
      3. In the Encryption Keys area, choose 128 bit as the Key Size and enter the Encryption Key.
         Note: This encryption key must match the encryption key that you configure on the non-root bridge.
         In this example, the encryption key is 1234567890abcdef1234567890.
         Here is an example:
         
         
   4. Create a new service set identifier (SSID) for the bridges to use in order to communicate.
      Complete these steps:
      
      1. Choose Security > SSID Manager from the menu on the left.
         The SSID Manager window displays.
         
      2. Enter the new SSID in the SSID field.
         This example uses Cisco as the SSID.
         
      3. In the Authentication Settings area, check the Network EAP check box and click Apply.
         This enables LEAP authentication.
         Here is an example:
         
         Note: In Cisco IOS Software Release 12.3(4)JA and later, you configure SSIDs globally and then apply them to a specific radio interface. Refer to the Creating an SSID Globally section of the document Configuring Multiple SSIDs in order to configure SSIDs globally. Also, in Cisco IOS Software Release 12.3(7)JA, there is no default SSID.
         
   5. Scroll down to the Global Radio0-802.11G Properties area and complete these steps:
      
      
      1. From both the Set Guest Mode SSID and the Set Infrastructure SSID drop-down menus, select the SSID that you configured.
         For this example, select Cisco.
         
      2. Check the Force Infrastructure Devices to associate only to this SSID check box.
         This action configures the SSID Cisco as an infrastructure SSID and enables guest mode for this SSID.
         
   6. Configure the local RADIUS server parameters.
      
      1. Choose Security > Local Radius Server, and click the General Set-Up tab.
         
      2. In the Local Radius Server Authentication Settings area, click LEAP.
         
      3. In the Network Access Server (AAA Client) area, define the IP address and shared secret of the RADIUS server and click Apply.
         For the local RADIUS server, use the IP address of the AP.
         Here is an example:
         
         
      4. In the Individual Users area, define the individual users and click Apply.
         The user name and password that you configure must match the user name and password of the LEAP client. In this example, these fields must match the user name and password of the non-root bridge. The example user name is NonRoot, and the password is Cisco123.
         Note: Groups are optional. The group attributes do not pass to the active directory and are only locally relevant. You can add groups later, after you confirm that the base configuration works correctly.
         

Now that you have configured the root bridge, it is ready to associate with clients and non-root bridges. Configure the non-root bridge in order to complete this setup and establish a point-to-point wireless connection.

CLI Configuration

You can use the CLI in order to configure the bridge using telnet.

!--- These commands enable the local radius server on the bridge
!--- and ensure that local radius server is used for authentication:

bridge#aaa new-model
bridge#aaa group server radius rad_eap server 10.0.0.1 auth-port 1812 acct-port 1813
bridge#aaa authentication login eap_methods group rad_eap

bridge(config)#station role root
bridge(config)#distance 1


!--- This commands enters the bridge into the local server config mode:

bridge(config)#radius-server local



!--- By default LEAP, EAPFAST, and MAC authentications are
!--- supported. Using the no form for other 2 types ensures 
!--- that LEAP is used for authentication.
 
bridge(config-radsrv)#no authentication eapfast
bridge(config-radsrv)#no authentication mac

bridge(config)#interface dot11radio 0
bridge(config-if)#ssid bridge

!--- This command enables EAP authentication for the SSID.

bridge(config-if-ssid)#authentication network-eap rad_eap


!--- This step is optional.
!--- This value seeds the initial key for use with broadcast
!--- [255.255.255.255] traffic.  If more than one VLAN is
!--- used, then keys must be set for each VLAN.

bridge(config-if)#encryption vlan 1 key 1 size 128bit 12345678901234567890123456 transmit-key
 

!--- This defines the policy for the use of Wired 
!--- Equivalent Privacy (WEP). If more than one VLAN is used, 
!--- the policy must be set to mandatory for each VLAN.

bridge(config-if)#encryption vlan 1 mode wep mandatory 

bridge(config)#user cisco password cisco123

Configure the Nonroot Bridge

GUI Configuration

This section presents the information to configure the wireless bridge as a non-root bridge. The non-root bridge authenticates as a LEAP client to the local RADIUS server on the root bridge.

1. Access the wireless bridge through the GUI and go to the Summary Status window.
   Complete the instructions in Step 1 of the section Configure the Root Bridge in order to reach the Summary Status window.
   Note: The non-root bridge is configured with IP address 10.0.0.2.
   This window displays:
   
   
2. Configure the SSID for communication.
   
   1. Choose Security > SSID Manager from the menu on the left.
      The SSID Manager window appears.
      
   2. Enter the same SSID that you configured on the root bridge in the SSID field.
      
   3. In the Authentication Settings area, check the Network EAP check box.
      
      
3. Scroll down to the General Settings configuration parameters, define the user name and password for EAP Client, and click Apply.
   This user name and password must exist on the RADIUS server for successful LEAP authentication. In this example, the user name and password must be on the local RADIUS server on the root bridge. Use the user name NonRoot and password Cisco123, which you already configured on the local RADIUS server.
   
   
4. Scroll down to the Global Radio0-802.11G SSID Properties area of this window and complete these steps:
   
   1. From both the Set Guest Mode SSID and the Set Infrastructure SSID drop-down menus, select the SSID that you configured.
      For this example, select Cisco.
      
   2. Check the Force Infrastructure Devices to associate only to this SSID check box.
      This action configures the SSID Cisco as an infrastructure SSID and enables guest mode for this SSID.
      
5. Enable the radio interface and configure the radio interface for non-root mode.
   Complete these steps:
   
   1. Enable the radio interface and define it as a non-root bridge.
      Note: The radio interface is disabled by default.
      Complete these steps:
      
      1. Choose Network Interfaces > Radio0-802.11G > Settings.
         The Network Interfaces: Radio0-802.11G Settings window displays.
         
      2. Click Enable under Enable Radio in order to activate the radio interface.
         
   2. Enable non-root mode on the wireless bridge.
      Complete these steps:
      
      1. For Role in Radio Network, click Non-Root Bridge.
         
         
      2. Enter 1 for the Distance (Km) parameter, leave all the other parameters at their default values, and click Apply at the bottom of the window.
         
         
   3. Configure the non-root bridge as a LEAP client.
      
      1. Choose Security > Encryption Manager.
         
      2. In the Encryption Modes area, choose Mandatory for WEP Encryption and choose WEP 128 bit from the drop-down menu beside Cipher.
         
         
      3. In the Encryption Keys area, choose 128 bit as the Key Size and enter the Encryption Key.
         You must use the same WEP encryption key that you used on the root bridge. In this example, the encryption key is 1234567890abcdef1234567890.
         

Nonroot CLI Configuration

You can use the CLI to configure using telnet.
This example sets a LEAP user name and password for the SSID bridgeman:

bridge#configure terminal
bridge(config)#configure interface dot11radio 0
bridge(config)#station role non-root
bridge(config-if)#ssid bridge

!--- This command configures the user name and password for Leap authentication:

bridge(config-ssid)#authentication client username cisco password cisco123
bridge(config-ssid)#end

Verify

Use this section to confirm that the bridges can associate with each other.
After you configure the wireless bridges for point-to-point connectivity, the local RADIUS server that you configured on the root bridge performs authentication with the use of LEAP.

1. In order to verify successful LEAP authentication, check that the Summary Status report on the root bridge looks like this example:
   
   
2. Check that the Association table looks like this example:
   
   
3. Verify the connectivity on the non-root bridge Association table.
   
   
4. Use the ping test to verify the point-to-point connection.
   Choose Association > Ping/Link Test.
   
   The ping output confirms the establishment of point-to-point connectivity between the wireless bridges.
   
   

Verify Client Connectivity Through the Bridges

Now that you have established the point-to-point connectivity between the wireless bridges, verify the connectivity between the end clients that connect to the wireless bridges.
After you configure the client adapters, the clients associate with the bridges. This example shows the Summary Status window on the root bridge with Client A associated:

The ping test output from the command prompt on Client A confirms reachability to Client B. Here is an example of the ping test on Client A:

Troubleshoot

Verify these items in order to troubleshoot the connectivity between the wireless bridges:

• Ensure that the bridges are configured appropriately in their roles.
  
• Ensure that security settings are identical on both the bridges; wireless settings (such as channel and SSID) should be configured identically on both the bridges.
  
• Ensure that the least congested channel is selected; there should be least interference in the path between the bridges.
  
• Check if appropriate antennas are used for the radios.
  
• Ensure that the antennas of both the bridges are aligned properly to receive maximum signal.
  
• Ensure Layer 3 connectivity. You can use the ping command in order to verify Layer 3 connectivity.
  

Read more »

Posted in: Configure Camera