TP-link access points disassociating

[warbo]

I believe these access points are pretty popular. Is anyone running 2 in the same location connected to a wireless router?

I've got 2 dreams hooked up to 2 access points and both are freezing /pixellating etc etc. The distance between the access points and the wireless router is minimal.

Yet when I look in the routers logs I see this:

Mar 18 15:53:28 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 18 15:56:07 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 18 16:20:15 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 18 1745 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 17:52:39 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 18 18:00:32 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 18 18:19:30 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 1805 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 18:26:58 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 18:29:14 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 18 18:29:46 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 18:40:26 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 1901 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 19:48:09 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 2046 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 2014 home.gateway:rt61apRxPacketProc:none: 00:1d:0f:e8:47:7c associated
Mar 18 2004 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 20:53:06 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 2147 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 18 21:26:29 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 18 2109 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe

To me this suggests that they are disconnecting and reconnecting.

Any ideas would be greatly appreciated...


EDIT: I am going to upgrade the Billion routers firmware and see what happens, but I can't do that until tommorrow. Please feel free to suggest any thing else in the mean time.

[warbo]

Had a chance to drop out there and upgrade the billion firmware.

It looks like it has resolved the issue

[Fernbay]

Whats the model of the TP links? TP-WA501G's?

Also can you post a link to that firmware too?

I've helped some people out with TP-WA501's and had them running fine without issues, but still currious to know if they are just rebadged billions...

[warbo]

They are TL-WA501G's, although the firmware I was referring to was for the Billion 7401vgpm wireless router that they were talking to.

It seems there were issues with the Billion's factory firmware and wireless.

[warbo]

Hmmmmm.....still happening but not quite as bad.

Can anyone comment if this is normal for 2 wireless clients communicating to a wireless router. If not normal why could this be happening? One of the clients is not more than 5 meters from the wireless router and the other is not more than 10.

Mar 19 19:04:22 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 19 1941 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 19 1959 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 19 19:16:53 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 19 20:37:05 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 19 20:37:22 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 19 20:37:24 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 19 20:44:43 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 20 06:44:06 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 20 06:54:28 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 20 06:59:23 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 20 0711 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 20 07:14:03 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe disassociated
Mar 20 0810 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 20 0821 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 20 10:44:35 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated
Mar 20 10:44:36 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 disassociated
Mar 20 10:53:02 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:fe associated
Mar 20 10:56:38 home.gateway:rt61apRxPacketProc:none: 00:19:e3:03:75:a1 associated

[admin]

What happens when you just run one of them ? Same thing ?

[urban_s0ulja]

i havnt seen this problem....
i was running 4 of these in client mode a few months back without any issues you are speaking of.

Have you tried a different router?


ill look into it for you latter tonight.

[warbo]

Sanity, next time I can give that a try I'll see what happens.

Thanks Urban, I don't have another model of router I can try unfortunately.
That would be great to see if you come up with anything!

I did send a log file off to tp-link usa as it seems it's either that or China.....
Just to see if they can tell me exactly whats happening. Hopefully they'll reply.

[z80]

This thread should be moved out of the dreambox section.

[warbo]

I am going to swap the 2 tp-links with 2 minitars this afternoon and see how it goes.

Mods, please move this thread if you see valid. I only posted here because a lot of people use the Tp-links in client mode with dreams.

[lukebe]

You stated you upgraded the firmware on the billion but not the TP-WA501G?
Probably not required in your case but the new firmware supports WPA-PSK in client mode so was a must for me.

[BCNZ]

I have a system running using one 501 as an access point and one as a client - effectively a long distance LAN link.

It's been working solidly with no issues at all since the middle of last year.