simple accesspoint setup help - Linksys wap4410-N

[Symbiot]

Hi

Apparently I can't seem to find the proper way of setting up my linksys 4410N as an accesspoint.

Here's what I want & Have

I have an asus ac66 router running my wireless network SSID: myWireless
This is placed in one end of the house

I have a linksys 4410N which I've placed in the other end of the house
I have a lan cable running between the 2.. The linksys is plugged in to one of the switch ports of the asus

What I want is for the linksys to just extend my existing wireless from the asus. So I can have proper coverage of my house.

But I am stumped as to the correct setting in the linksys.
I've set it as access point.. but that seems to create some issues.. network becomes unstable for some reason.

Is there some specific settings I need to be aware of on the linksys.. or the asus for that matter?

I'd love it if someone had some specific advice on the above setup..

 

[sinshiva]

hi, what port on the linksys is connected to the asus? i /think/ that you probably cant set the wan/'internet' port to the lan bridge without installing a custom firmware like dd-wrt. this means usng up one of the LAN ports. no big deal if it will just be an AP. also, make sure the lan IP of the linksys is set to the same network as the asus; for example, if the asus is 192.168.0.1, the linksys should be 192.168.0.2 rather than 192.168.1.2

also, you should see about disabling DHCP on the lan side; i've not dealt with that particular model, so i can't say for certain whether it's possible. disabling on the WAN side would likely not be sufficient. if you cant, this can cause conflicts with clients trying to connect, but as long as the lan ip of the router is correctly configured, it shouldn't prevent them from getting a working ip and network access. this is more important when you have static dhcp leases setup on the asus router.

also, the lan configuration should give you options to specify the gateway and dns, both should be set to the lan ip of the asus router. if you can't, then you really will need to install dd-wrt.

really, you should investigate the process by which you would go about installing dd-wrt on that model. it's a safe and easy process, just be sure to do it over a wired connection to be sure.

that should be enough to get you started

 

[Symbiot]

Hi Sin

thanks..
to answer your questions.
linksys is connected via wire to lan switch port on asus router.
it's on same subnet etc. router=192.168.1.1 Linksys=192.168.1.245

There's no dhcp on the linksys.. it's an accesspoint.

dd-wrt doesn't support the linksys 4410N so that's a no go :-|

 

[jlake]

I set up a wap4400 for someone about a year ago. It's pretty much the same as 4410. Here's what I did:

1. Change channel width to 20 MHz
2. Disabled AP isolation since it was enabled by default and this was for a home (not a business)
3. I used inSSIDer to figure out what channels were available.
4. I set their primary router 2.4 ghz width to 20 MHz also
5. I used channel 11 on main router and channel 1 on Wap4400
6. I gave them different SSIDs.

If your using same SSIDs and channel (I don't recommend that) then try making sure their DTIM intervals are the same. Asus uses 3 as default. Linksys uses 1 as default. So either change the linksys to 3 or change asus to 1.

That's basically all I did and didn't have any problems.

Obviously you know the default IP address of asus is 192.168.1.1 and default IP address of 4410 is 192.168.1.245, so you don't need to change anything there.

 

[sinshiva]

haha, ah. guess they make those, too xD

[edit/] what issues were you having? provided jlake's suggestions don't help you clear them up

damn, i totally read the model wrong on that, i should sleep now

 

[Symbiot]

Hi Jlake..

Why would you set a different ssid?
What I'm trying to accomplish is to extend the range of my existing network.
So when I'm in the other end of the house.. the linksys will be stronger, and thus.. I'd want my devices to switch over to the AP.

And thanks for your suggestions.. I'll look into some of them

 

[Symbiot]

haha, ah. guess they make those, too xD

[edit/] what issues were you having? provided jlake's suggestions don't help you clear them up

damn, i totally read the model wrong on that, i should sleep now

Sinshiva.. thanks for your (tired) reply )

issues are.. well the issue is how to set it up to extend my wireless network in the house.. what's the best setup for the AP when it's wired to my router.. and when I want to extend the coverage of my existing network.

 

[sinshiva]

i'm good for those kind

use jlakes tips and see where they get you.

as far as using different SSIDs, wireless clients will generally stick to an AP, even when another known AP has better signal strength. by using different SSIDs, you can more easily choose the nearby AP. there's some other reasons, but that's the gist of it.

With some APs, you can configure them to punt a client when they get below a signal threshold, but it's not the seamless transition nicer/newer APs like Cisco Aironet or Ubiquiti's UAP series can do

Looks like Cisco Aironet needs a controller to do it, whereas the Ubiquiti UAPs 'talk' to eachother

 

[sfx2000]

I set up a wap4400 for someone about a year ago. It's pretty much the same as 4410. Here's what I did:

1. Change channel width to 20 MHz
2. Disabled AP isolation since it was enabled by default and this was for a home (not a business)
3. I used inSSIDer to figure out what channels were available.
4. I set their primary router 2.4 ghz width to 20 MHz also
5. I used channel 11 on main router and channel 1 on Wap4400
6. I gave them different SSIDs.

If your using same SSIDs and channel (I don't recommend that) then try making sure their DTIM intervals are the same. Asus uses 3 as default. Linksys uses 1 as default. So either change the linksys to 3 or change asus to 1.

That's basically all I did and didn't have any problems.

Obviously you know the default IP address of asus is 192.168.1.1 and default IP address of 4410 is 192.168.1.245, so you don't need to change anything there.

Nice stuff - couple of comments

1) Assign a static IP to the Access Point outside of the DHCP range of the primary router (and make sure you only have one DHCP server on your network) - if 192.168.1.245 is outside of your DCHP range, you're good to go there.

2) I recommend common SSID as it is part of the same LAN/WLAN as the primary AP

3) Ensure that SSID broadcast is enabled on all AP's - and ensure that only one SSID is in use (this AP supports up to 4 SSID's)

4) Disable VLAN's for now if you don't need them - this AP does support VLAN tagging BTW

5) AP Mode - allow it to act as a normal AP, disable "Allow Wireless Signal to be repeated by a repeater" as you have an ethernet connection to the primary AP, so you don't want repeating - this will half your throughput to any clients attached to that AP

6) WPA2-Personal (not mixed, not WPA, not WEP) - use same pass phrase for both the primary and secondary AP's

7) Wireless Mode - leave it in B/G/N mixed mode - and find a clear channel - so for example, if your primary is on Channel 1, try using Channel 6 or Channel 11 for the WAP

8) Make sure that WMM is enabled.

The 4410N is end-of-life from a Cisco perspective, so I would grab a copy of the latest firmware for safe keeping.

Good luck - it's a decent AP

 

[Symbiot]

Hi

Thanks for the reply..

AP is set as follows:

same ssid
same password
channel: auto (same as asus router)

set as AP mode

everything set as you suggested I think

1 place I'm a bit confused on is the advanced settings..

any suggestions here?

I'm running 1Gbit cable..

 

[sfx2000]

Your advanced settings look ok

Try setting channels manually on both the Router/AP and the 4410N as discussed earlier.

Also, might want to run some ping traffic between something both ends of the link just to see if you're getting dropouts. There's a diagnostics page in the WAP and tinker about inside there - try running the ping-test over to the 192.168.1.1 address and see what is going on there.

Also, perhaps to be a bit more helpful - what exactly are you seeing with the "instability" - trying to sort if this is a cabling issue or a radio issue.

Also - try ruling out bad ethernet and perhaps the AC Adapter on the 4410N, it's older gear, and a 2 dollar part at the OEM level can make people pull their hair out

 

[sfx2000]

Something else to consider - try turning off the 4410N for a bit, and check coverage throughout the common places that you use wireless.

Might be surprised - the AC66U has a fairly stout radio - you might not need more AP's.

 

[Symbiot]

here's some ping results from linksys to asus:

PING 192.168.1.1 (192.168.1.1): 32 data bytes
32 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.3 ms
32 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.3 ms
32 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.3 ms
32 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.3 ms
32 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.3 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.3/0.5/1.3 ms

==

PING 192.168.1.1 (192.168.1.1): 4096 data bytes
4096 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=21.9 ms
4096 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.4 ms
4096 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.4 ms
4096 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.4 ms
4096 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.4 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.4/5.5/21.9 ms

==

PING 192.168.1.1 (192.168.1.1): 65500 data bytes
65500 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=44.4 ms
65500 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=14.7 ms
65500 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=14.7 ms
65500 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=14.8 ms
65500 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=14.8 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 14.7/20.6/44.4 ms

==

And from ASUS to linksys:

PING 192.168.1.245 (192.168.1.245): 56 data bytes
64 bytes from 192.168.1.245: seq=0 ttl=64 time=1.679 ms
64 bytes from 192.168.1.245: seq=1 ttl=64 time=0.426 ms
64 bytes from 192.168.1.245: seq=2 ttl=64 time=0.451 ms
64 bytes from 192.168.1.245: seq=3 ttl=64 time=0.391 ms
64 bytes from 192.168.1.245: seq=4 ttl=64 time=0.388 ms

--- 192.168.1.245 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.388/0.667/1.679 ms

==

bytes from 192.168.1.245: seq=33 ttl=64 time=1.572 ms
4104 bytes from 192.168.1.245: seq=34 ttl=64 time=1.494 ms
4104 bytes from 192.168.1.245: seq=35 ttl=64 time=1.431 ms
4104 bytes from 192.168.1.245: seq=36 ttl=64 time=1.516 ms
4104 bytes from 192.168.1.245: seq=37 ttl=64 time=1.441 ms
4104 bytes from 192.168.1.245: seq=38 ttl=64 time=1.555 ms
4104 bytes from 192.168.1.245: seq=39 ttl=64 time=1.475 ms
4104 bytes from 192.168.1.245: seq=40 ttl=64 time=1.449 ms
4104 bytes from 192.168.1.245: seq=41 ttl=64 time=1.765 ms

===

PING 192.168.1.245 (192.168.1.245): 65500 data bytes
65508 bytes from 192.168.1.245: seq=0 ttl=64 time=14.899 ms
65508 bytes from 192.168.1.245: seq=1 ttl=64 time=14.793 ms
65508 bytes from 192.168.1.245: seq=2 ttl=64 time=14.992 ms
65508 bytes from 192.168.1.245: seq=3 ttl=64 time=14.657 ms
65508 bytes from 192.168.1.245: seq=4 ttl=64 time=15.616 ms
65508 bytes from 192.168.1.245: seq=5 ttl=64 time=14.968 ms
65508 bytes from 192.168.1.245: seq=6 ttl=64 time=15.012 ms
65508 bytes from 192.168.1.245: seq=7 ttl=64 time=15.099 ms
65508 bytes from 192.168.1.245: seq=8 ttl=64 time=14.892 ms
65508 bytes from 192.168.1.245: seq=9 ttl=64 time=14.724 ms
65508 bytes from 192.168.1.245: seq=10 ttl=64 time=15.112 ms
65508 bytes from 192.168.1.245: seq=11 ttl=64 time=15.448 ms
65508 bytes from 192.168.1.245: seq=12 ttl=64 time=14.765 ms
65508 bytes from 192.168.1.245: seq=13 ttl=64 time=15.068 ms
65508 bytes from 192.168.1.245: seq=14 ttl=64 time=14.828 ms
65508 bytes from 192.168.1.245: seq=15 ttl=64 time=14.685 ms
65508 bytes from 192.168.1.245: seq=16 ttl=64 time=16.016 ms
65508 bytes from 192.168.1.245: seq=17 ttl=64 time=14.760 ms
65508 bytes from 192.168.1.245: seq=18 ttl=64 time=14.662 ms
65508 bytes from 192.168.1.245: seq=19 ttl=64 time=14.962 ms
65508 bytes from 192.168.1.245: seq=20 ttl=64 time=14.796 ms
65508 bytes from 192.168.1.245: seq=21 ttl=64 time=14.662 ms
65508 bytes from 192.168.1.245: seq=22 ttl=64 time=15.163 ms
65508 bytes from 192.168.1.245: seq=23 ttl=64 time=14.763 ms

 

[Symbiot]

oh.. and asus is running Merlin's build

 

[Symbiot]

Your advanced settings look ok

Try setting channels manually on both the Router/AP and the 4410N as discussed earlier.

Also, might want to run some ping traffic between something both ends of the link just to see if you're getting dropouts. There's a diagnostics page in the WAP and tinker about inside there - try running the ping-test over to the 192.168.1.1 address and see what is going on there.

Also, perhaps to be a bit more helpful - what exactly are you seeing with the "instability" - trying to sort if this is a cabling issue or a radio issue.

Also - try ruling out bad ethernet and perhaps the AC Adapter on the 4410N, it's older gear, and a 2 dollar part at the OEM level can make people pull their hair out

The instability was specifically my Ipad connecting then disconnecting again.. then I could manually connect again... then 5 secs later it disconnected..
Like it couldn't keep the connection alive..

The adapter.. well.. it _could_ be that.. but it seems to run ok now..
Cable should be ok as well.. though it's one I made my self.. which is always a joker

 

[Symbiot]

Something else to consider - try turning off the 4410N for a bit, and check coverage throughout the common places that you use wireless.

Might be surprised - the AC66U has a fairly stout radio - you might not need more AP's.

Hi


Yes, I agree the asus radio is quite good.. but as in my 1st post.. it's at one end of the house and it's quite poor in the other end of the house.. so I thought an access point would fix that

 

[sfx2000]

Everything looks ok actually...

If it's only the iPad, then try doing a reset of the network settings (not remove, add network, but reset) - Settings, General, Reset, Reset Network Settings - sometimes the file that stores those values can get corrupted.