Solved Configure TL-WR841N router as access point

1025448 Tl-wr841n wireless router - ieee...
April 5, 2016 at 09:48:19
Specs: Windows 7, Intel Core 2 Quad/8GB
Hi,

I am trying to use a TL-WR841N as an access point for my internet access.

I followed the instructions at:
http://www.tp-link.us/faq-417.html

The situation now is:

If connected to my ISP router, I can access:
- The internet
- ISP router admin page
Cannot access:
- TL-WR841N admin page
DHCP works

If connected to the TL-WR841N, I can access:
- ISP router admin page
- TL-WR841N admin page
Cannot access:
- The internet
DHCP does not work, have to manually configure IP to connect.

Can someone provide some guidance on what should be checked or configured?
Thanks!


See More: Configure TL-WR841N router as access point

Report •


✔ Best Answer
April 6, 2016 at 12:47:02
Cable connected to LAN ports on both routers. The only config mentioned that I am not seeing is somewhere to define the Default Gateway on the secondary router outside of the DHCP configuration.

Within in the static LAN settings of your second router there should be a default gateway setting. If not, I'm very much surprised. It's not a huge deal mind you since the router's LAN interface itself does not need to go beyond the boundaries of the subnet.

Two additional things I now noticed:
- The secondary router has logs that states it is not getting a response to DHCP requests

That's odd because the router should not be requesting DHCP information. Likely that's the external (internet/WAN) interface on the router doing DHCP requests. Shut that off if you can. I suspect you'll have to change the external interface to "static" from "DHCP" in order to make that quit.

- I can ping the secondary router from the ping tool on the primary router admin interface but I cannot ping the secondary router from a host connected to the primary router

This is likely because the second router's firewall is set to not respond to ICMP (ping) requests. As long as clients connecting to the second router (wired or wireless) are getting proper TCP/IP settings from the DHCP server on the primary router, and are able to surf the internet, then all is well and you don't need to worry about it.


fingers
Shouldn't the DHCP range include the secondary router? Something like 192.168.254.1 to 192.168.254.200 or at least the secondary router's fixed IP should fall between the above parameters like 192.168.254.101 ?

Nope, you don't want the second router's IP within your DHCP scope. First off, who needs 200 available IP's in a home environment.........LOL

Second, you run the risk of a duplicate IP error if you include statically assigned IP's within the scope of your DHCP. For instance, if the statically assigned device is off, DHCP may give that IP to a DHCP client. Then, when you power up the statically assigned device, you get a dupe error and the statically assigned device can't communicate.

Typically one uses reservations or exclusions within DHCP for statically assigned IP's but it's been my experience, especially in the home or small business environments, that leaving a block of IP's not included in the scope amounts to the same thing and saves a tiny bit of admin time. Since most SOHO routers have a scope of 100 to 199 by default, you have 1-99 to use for static stuff so I always pick IP's for server's, my NAS, my printer, etc from that series of addresses.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***



#1
April 5, 2016 at 13:05:51
Click on my name above in my response and read my "How-To" regarding adding a second router to your home network.

You'll want to pay attention to the scenario wherein you use one subnet only.

Ensure you have the TL router connected properly to your existing ISP provided router and it should all work. I suspect it's not properly configured right now.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
April 5, 2016 at 13:09:32
I just reread my how-to guide and it's a little dated. There is nothing in there about making the second router a wireless access point. It's really quite simple.

Once you have the second (downstream) router configured properly, connected to the first router and working, you would then create a wifi network on it using EXACTLY the same SSID, encryption and encryption key as you have configured on the upstream router (the one connected to the internet).

That should be all you need to do.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#3
April 5, 2016 at 15:40:00
Also this arrangement is best done using a permanent cat-5/ethernet connection between the two routers. This cat-5 connection can either be a direct run of cat-5/ethernet cable; or home plugs can be used to allow the main router to connect to the second router (LAN over the mains system).

Using wifi to wifi connection is not the best; prone to instability; prone to drop out and other irritations. A cat-5/ethernet connection between the two routers is by far the better approach.


Report •

Related Solutions

#4
April 5, 2016 at 19:11:34
I have read the suggested documents and I followed as best as I could using the one subnet configuration.
Also I am keeping a cable between the two routers.

Primary router:
IP:192.168.254.1
Subnet: 255.255.255.0
DHCP enabled: Yes
DHCP range: 192.168.254.100 to 192.168.254.200

Secondary router:
IP:192.168.254.2
Subnet: 255.255.255.0
DHCP enabled: No

Cable connected to LAN ports on both routers. The only config mentioned that I am not seeing is somewhere to define the Default Gateway on the secondary router outside of the DHCP configuration.

Two additional things I now noticed:
- The secondary router has logs that states it is not getting a response to DHCP requests
- I can ping the secondary router from the ping tool on the primary router admin interface but I cannot ping the secondary router from a host connected to the primary router


Report •

#5
April 5, 2016 at 21:49:00
Trvlr on this:
"Primary router:
IP:192.168.254.1
Subnet: 255.255.255.0
DHCP enabled: Yes
DHCP range: 192.168.254.100 to 192.168.254.200

Secondary router:
IP:192.168.254.2
Subnet: 255.255.255.0
DHCP enabled: No"

Shouldn't the DHCP range include the secondary router? Something like 192.168.254.1 to 192.168.254.200 or at least the secondary router's fixed IP should fall between the above parameters like 192.168.254.101 ?

Waks12:
Is the primary router a hard wired only router (this is the impression I got from the initial question) and this is the only wireless access? This is different from using the second router as a range extender where both are running Wifi to different areas of the same building(s).

You have to be a little bit crazy to keep you from going insane.


Report •

#6
April 6, 2016 at 12:47:02
✔ Best Answer
Cable connected to LAN ports on both routers. The only config mentioned that I am not seeing is somewhere to define the Default Gateway on the secondary router outside of the DHCP configuration.

Within in the static LAN settings of your second router there should be a default gateway setting. If not, I'm very much surprised. It's not a huge deal mind you since the router's LAN interface itself does not need to go beyond the boundaries of the subnet.

Two additional things I now noticed:
- The secondary router has logs that states it is not getting a response to DHCP requests

That's odd because the router should not be requesting DHCP information. Likely that's the external (internet/WAN) interface on the router doing DHCP requests. Shut that off if you can. I suspect you'll have to change the external interface to "static" from "DHCP" in order to make that quit.

- I can ping the secondary router from the ping tool on the primary router admin interface but I cannot ping the secondary router from a host connected to the primary router

This is likely because the second router's firewall is set to not respond to ICMP (ping) requests. As long as clients connecting to the second router (wired or wireless) are getting proper TCP/IP settings from the DHCP server on the primary router, and are able to surf the internet, then all is well and you don't need to worry about it.


fingers
Shouldn't the DHCP range include the secondary router? Something like 192.168.254.1 to 192.168.254.200 or at least the secondary router's fixed IP should fall between the above parameters like 192.168.254.101 ?

Nope, you don't want the second router's IP within your DHCP scope. First off, who needs 200 available IP's in a home environment.........LOL

Second, you run the risk of a duplicate IP error if you include statically assigned IP's within the scope of your DHCP. For instance, if the statically assigned device is off, DHCP may give that IP to a DHCP client. Then, when you power up the statically assigned device, you get a dupe error and the statically assigned device can't communicate.

Typically one uses reservations or exclusions within DHCP for statically assigned IP's but it's been my experience, especially in the home or small business environments, that leaving a block of IP's not included in the scope amounts to the same thing and saves a tiny bit of admin time. Since most SOHO routers have a scope of 100 to 199 by default, you have 1-99 to use for static stuff so I always pick IP's for server's, my NAS, my printer, etc from that series of addresses.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#7
April 6, 2016 at 19:22:52
The DHCP logs were indeed due to WAN interface. Set to static and it stopped.

The issue did seems like a firewall issue, but I could not change anything on the primary router (it's really locked down).

I ended up contacting my ISP and they informed me that LAN ports 3 and 4 on the router have limited connectivity, so i plugged it into port 2 and it worked (Doh!)

Thanks to all who assisted in getting this resolved!


Report •

#8
April 7, 2016 at 03:50:22
The issue did seems like a firewall issue, but I could not change anything on the primary router (it's really locked down)

It would be the secondary router preventing itself from responding to pings. Not the primary.


I ended up contacting my ISP and they informed me that LAN ports 3 and 4 on the router have limited connectivity, so i plugged it into port 2 and it worked (Doh!)

That's just strange. I've never heard of that before! And, I can't imagine why you would build a router that has "limited connectivity" on any port!?!?

It's great you were able to find out, make the change and have everything work properly!

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#9
April 7, 2016 at 21:07:12
Great to hear all is resolved.

Thanks Curt, that makes sense completely.

You have to be a little bit crazy to keep you from going insane.


Report •


Ask Question