[8.160][BUG][FIXED] wireless client does not connect anymore

I have an Epson printer that was connected to the network via the AP30.
Now it cannot connect, fails authentication. So I created a ssid with a lower authentication level, but the printer still fails to keep an association. The laptops and i-phones work fine.

Also the signal strength appears to have dropped after the upgrade. The printer is about 2 metres away from the AP30 and the connection speed is about 500k to 1mb. The speeds to the i-phones and laptops also appears to have been reduced.

Ian M

Parents

0 hschaa over 14 years ago

Or even better. Could you please temporary disable all other SSIDs except the printer SSID? Let the printer associate again and afterwards attach the wireless.log here? Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 14 years ago in reply to hschaa

Hi,
I will be home late tonight and give that try then.

Otherwise it is find an ethernet port for the printer.

Regards

Ian M
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to RFCat_vk_01

Ok, no problem, would have been an easy way to verify my assumption [;)]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 14 years ago in reply to hschaa

Can I force the AP30 to B only?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to RFCat_vk_01

Can I force the AP30 to B only?

Not officially [:)]

But you can add a WEP secured (yeah, let's call it WEP unsecured) SSID as 802.11n is not allowed with WEP and thus will force the AP and the Printer to use 11g rates.

Might be worth a try.

Thanks,
Helmut
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to hschaa

But you can add a WEP secured (yeah, let's call it WEP unsecured) SSID as 802.11n is not allowed with WEP and thus will force the AP and the Printer to use 11g rates.

Might be worth a try.

Of course not as a solution, just to gather some more info about this problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 14 years ago in reply to hschaa

Hi Helmut,
okay created a SSID with WEP 128 (104).

The logfile will show a number of attempts, please ignore them, I forgot to associate the SSID.
Eventually, many key presses later the printer connected at 54mb/s with all the correct details

Log entries to look for start around 2118 10 March ASG time and finish around 2140.

Now to put it back together again.

Ian M

logfiles_20110310214206.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to RFCat_vk_01

Eventually, many key presses later the printer connected at 54mb/s with all the correct details

Ok, so, the printer connected just fine and also got an address via DHCP? Is that correct?

Thanks a lot,
Helmut
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 14 years ago in reply to hschaa

Correct. I also ran a test print just to be sure.

26 hex characters is a pain on a telephone number pad, especially when you get it wrong.

Glad to be of assistance.

Ian M
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to RFCat_vk_01

26 hex characters is a pain on a telephone number pad, especially when you get it wrong.

Indeed!

JFI I've just committed a fix that fixes a problem with some RX STBC capable wifi clients. The epson printer seems to be RX STBC capable. So your problem might be fixed in 8.161 but I'm not sure at all [;)]

Please report back if things improve with 8.161. Otherwise we need to do some more intense debugging ...

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 14 years ago in reply to hschaa

Hi Helmut,
there is good news. The Epson connected first time after some typing errors. Prints well as can be expected.
When printing the wireless security was showing 52mb when printing finished the rate went to 65mb/s which is the highest I saw it previously. The distance between the 2 is line of site, same height, 2 metres apart.

Anyway, thank you it works.

Ian M[[:)]][[:)]]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to RFCat_vk_01

The Epson connected first time after some typing errors. Prints well as can be expected.

Nice. If it breaks again be sure to tell me [:)]

When printing the wireless security was showing 52mb when printing finished the rate went to 65mb/s which is the highest I saw it previously. The distance between the 2 is line of site, same height, 2 metres apart.

Yeah, the rate control algorithm does not necessarily choose the fastest rate, it also takes the transmission probability into account and in some cases a "slower" rate can result in better latency/throughput then a "faster" rate (depending on external circumstances like temporary interference, wall reflections etc.). So, no need to worry about this.

Thanks a lot for the report,
Helmut
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 hschaa over 14 years ago in reply to RFCat_vk_01

The Epson connected first time after some typing errors. Prints well as can be expected.

Nice. If it breaks again be sure to tell me [:)]

When printing the wireless security was showing 52mb when printing finished the rate went to 65mb/s which is the highest I saw it previously. The distance between the 2 is line of site, same height, 2 metres apart.

Yeah, the rate control algorithm does not necessarily choose the fastest rate, it also takes the transmission probability into account and in some cases a "slower" rate can result in better latency/throughput then a "faster" rate (depending on external circumstances like temporary interference, wall reflections etc.). So, no need to worry about this.

Thanks a lot for the report,
Helmut
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data