This started as a temporary that was gona get cut and pasted into my Networking Page -but- it has now
become a permanent fixture. An entity of its own. Actually a compound of what I have found on the net.
I try to remember to credit everyone that deserves it -and- if you see something here that you believe
you need credit for... e-mail me.
I have found comments to the fact that NOT all wireless routers can be used as Access Points,
and even those that can, sometimes aren't very functional in the real world. Two configurations, by another
individual, in the past with AP's (Access Points
from NetGear that never did work even after going through every possible option with the
folks from NetGear.(Hmmmm, not good news.
Well, maybe not. My desire to 'just add' a Wireless point
to my already working ... and secure ... Network seems to NOT work. Disabling DHCP, and changing the Internal IP
in the 'first' WNDR3700 that I had seems to have put it in
Semi-Brick mode. I ended up
returning it and getting another. It was then decided to .. use this Router .. as a Router. It has both Hard Wired and
Wireless connections. So, my Wireless Access Point is not sitting off by itself, it is part of the Router.
Now with baited breath I changed the Internal IP address from
192.168.0.1 and tested it. Things were,
and still are, fine. Don't know if the factory guys will pull their hair out on that last one or not. I tried
the 'Factory Restore' before I returned it and ... it did not restore it. The only two things I had done was
to 'Turn off DHCP' and change the 'Internal IP Address'. Guess you can't turn off DHCP in these and expect
to ever see the Admin section again.
Step 1: Find the IP addresses of your existing gateway/router and clients
You need to find the internal IP address
of your 'existing' modem/gateway/router
that connects your LAN to the internet. Under Windows, the easiest way to do
this is, drop to the command prompt (Start > Run
) and type: ipconfig
in the displayed command window.
IP Address .............. : 192.168.0.2
Subnet Mask .......... : 255.255.255.0
Default Gateway .... : 192.168.0.1
The "IP address
" line in the above figure shows your computer's IP, while the
" is your main existing router that provides your internet
connection. It is usually in the 192.168.x.x range.
More advanced configuration issues must be performed with your favorite Telnet program from the LAN side.
ie; while in this command window enter: telnet 192.168.0.1 and hit Enter.
Also, if you are not a Windows user, you must do all configuration by Telnet. This will be no big deal for
Linux and Unix users, but it may be the first time a MacOS user has had to deal with a terminal emulator and Telnet.
What is all this fuss about the IP Addresses?? Well, all of my original Networking
Equipment is from the 2001 era. At that time, things were still new enough that they hadn't decided on
everything and a lot of these IP addresses got locked in. My Netgear PS110 Printer Server
is one of them.
I could NOT change it's Set IP.
It was/is 192.168.0.150 and that is that.
I'm not gona expound on all that I did to change it ... just suffice it to say that I couldn't.
Well, also in the beginning, my
Netgear RT311 Router was set for
192.168.0.1. So, all these years I have been
using the .0. scheme in my Network.
Well, it seems that the "new" trend is to use .1.
instead. As stated elsewhere, in my attempts to set the "New Router" to the
.0. addressing scheme, plus kill
DHCP so I could use it as an Access Point, I bricked the first one...at least to me. Using the
Factory Restore, and everything else I could find on the Net, would not fix it
and allow me to access the admin section of the New Router again.
I was finally able to change the IP Address of the "Newest" Router over
to the .0. addressing scheme and it is now
192.168.0.1. But I did
not touch DHCP!!
Step 2: Connect to your router administration interface to find the DHCP range
By default, LAN clients are usually set to obtain their IPs automatically. What
that means is, the router acts as a DHCP server, and serves IP addresses dynamically,
as needed to the client computers. You need to find the range of IPs used for DHCP
so you can later set your access point to use an IP address outside that range
(but on the same subnet).
Login to your gateway's admin interface, usually by typing its IP address in your
web browser, and find the DHCP range:
This may, or may not, work on your router. It did not do anything in my Netgear RT311.
Even telneting into the Administrator did not get the DHCP range. However, it did state
that the Starting Address in the Client IP Pool was 192.168.0.1 and that the Size of
that Client Pool was 32. Therefore, I am assuming that the DHCP range for my router is:
192.168.0.1 -to- 192.168.0.33
Step 3: Connect a computer to the wireless router/AP
You need to connect a computer (via a LAN port) to the 'new' Wireless Router to
be used as an Access Point.
We'll refer to it as the "Access Point" from now on. To do this:
- set your client computer to obtain its IP automatically (default behavior in Windows)
- connect it to a LAN port on the Access Point using a Cat5 network cable
- reboot, -or- use the "ipconfig /renew" command in Command prompt to force it to get an IP address from the access point
Log into the admin page of the 'Access Point'. It is usually done by simply typing the IP address of the router
in your browser's address bar. (IF you rebooted above, you can find it's IP address as you did in step
1 for your main router).
Step 4: Configure the wireless router / AP
Now this is where it can get complicated and confusing. Leastwise to me. I may be doing my usual of trying
to make it harder than it is -or- just not properly understanding what I know. So let's dig.
Once logged into the admin interface
of the wireless router
you need to do two things.
you need to change its internal/LAN IP address
to an unused
address in the same
range/subnet as all your other LAN
file on my main 'puter.
# dusty-tr, dusty2 and dusty4m were used on my 9995
# dusty-tr2, dusty3 were created for my new 7480
# Main Linux
192.168.0.2 dusty-tr2.trcomputing dusty-tr2
# Dars Win PC
192.168.0.3 dars-pc.trcomputing dars-pc
# Vista VM macine
192.168.0.5 dusty4.trcomputing dusty4
# Win2k VM machine
192.168.0.4 dusty3.trcomputing dusty3
# shop machine
192.168.0.6 workhorse.trcomputing workhorse
# Printer Server
192.168.0.150 PSD55465.trcomputing PSD55465
, you need to disable
server on your new AP
so there is only one DHCP
server on the network.
In my case, my main gateway/LAN router is set to 192.168.1.1, and it is serving dynamic IPs via DHCP in the
range 192.168.1.10 - 192.168.1.100. I have to use any other address in the 192.168.1.x range for the access point:
- Main Routerís base address is 192.168.1.1, with a DHCP server range of 192.168.1.100 to 192.168.1.150
- Set the Cable/DSL Router to (the one you're using as an Access Point) base address to any IP address
between 192.168.1.151 to 192.168.1.250
Step 5: Connect the AP to the LAN
It is time to connect the reconfigured wireless access point to the network. Use a LAN port on the new
wireless router, and connect it with a Cat5 network cable to one of the LAN ports of the existing gateway.
Make sure not
to use the "Internet/WAN" port on the wireless access point!
Connect your client computer to another LAN port of the gateway/router (if you do not reboot, you will
have to use "ipconfig /renew" in command prompt to obtain an IP address from your router).
Note: Some older devices that do not support Auto-crossover (MDI/MDI-X) may require a crossover network cable
(where the send and receive pairs are switched) between the two routers. This is not common with modern hardware.
For a diagram of non-automatic connections between MDI and MDIX devices, see
Step 6: Test admin page is reachable and secure the AP
Now that the new wireless access point is connected to our network, with a correct IP address in the same
range (and outside the DHCP range), we can test whether it's reachable, and secure the wireless connection.
In the above example, I configured the wireless AP to use 192.168.1.2. Its administration interface should
be reachable by typing this IP address in the browser.
Once connected, it is time to set the wireless security:
Step 7: Test the AP wireless connection
Start a wireless client and make sure it properly connects to the network. It should pull an IP address
automatically from your existing router/gateway (the DHCP server).
Done, you now have a wireless access point.
Copied from:Wireless Forums
courtesy of mysticvirgo67
Wi-Fi teminology can be a little confusing because there are many devices that seem to do the same thing, but in difference in details.
Maybe theses definitions form Wikipedia will help see the differences.
Routers connect two or more logical subnets, which do not necessarily map one-to-one to the physical interfaces of the router. The term "layer 3 switch" often is used interchangeably with router, but switch is a general term without a rigorous technical definition. In marketing usage, it is generally optimized for Ethernet LAN interfaces and may not have other physical interface types. In comparison, a network hub does not do any routing, instead every packet it receives on one network line gets forwarded to all the other network lines.
WIRELESS ACCESS POINTS
In computer networking, a wireless access point (WAP or AP) is a device that allows wireless communication devices to connect to a wireless network using Wi-Fi, Bluetooth or related standards. The WAP usually connects to a wired network, and can relay data between the wireless devices (such as computers or printers) and wired devices on the network.
A wireless router is a network device that performs the functions of a router but also includes the functions of a wireless access point. It is commonly used to allow access to the Internet or a computer network without the need for a cabled connection. It can function in a wired LAN (local area network), a wireless only LAN, or a mixed wired/wireless network. Most current wireless routers have the following characteristics:
LAN ports, which function in the same manner as the ports of a network switch
A WAN port, to connect to a wider area network. The routing functions are filtered using this port. If it is not used, many functions of the router will be bypassed.
Wireless antennae. These allow connections from other wireless devices (NICs (network interface cards), wireless repeaters, wireless access points, and wireless bridges, for example).
Hotspots use AP's connected through ethernet routers that provide the dhcp and IP addy's THROUGHT the WAP's to the client devices. The ap's control interface should allow you to designate a router with internet access as the GATEWAY IP for the AP device.
Basically an AP IS a router, with ONLY wireless connection between it and the client devices.
From Sander on: Wireless Forums
Routing and DHCP are two unrelated functions.
A router doesn't have to run a DHCP service to be a router.
An access point CAN run DHCP and NOT be a router.
Most SOHO routers will usually run a DHCP server but its not related to
the actual routing process so turning off DHCP and assigning static
adresses will not stop the routing process.
If you only connect a "local" port on it and don't use the WAN port that
might not be a problem though.
Wireless Access on Wired